<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (fjordaan)</title>
    <link>https://pinboard.in/u:fjordaan/public/</link>
    <description>recent bookmarks from fjordaan</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://dev.to/mfairchild365/ai-generated-accessibility-an-update-frontier-models-still-fail-but-skills-change-the-game-5629"/>
	<rdf:li rdf:resource="https://www.jeana.dev/thoughts/2026/05/fieldsets-legends/"/>
	<rdf:li rdf:resource="https://veroniiiica.com/using-kagi-search-with-low-vision/"/>
	<rdf:li rdf:resource="https://webaim.org/techniques/headings/"/>
	<rdf:li rdf:resource="https://webaim.org/techniques/headings/#missingh1"/>
	<rdf:li rdf:resource="https://annaecook.com/writing/2026/ai-doesnt-fix-accessible-systems-it-depends-on-them"/>
	<rdf:li rdf:resource="https://www.deque.com/blog/unique-id-attributes-matter/"/>
	<rdf:li rdf:resource="https://tarnoff.info/2026/03/10/quick-tip-dialog-focus/"/>
	<rdf:li rdf:resource="https://social.tupo.space/@joshua/116057389741775295"/>
	<rdf:li rdf:resource="https://css-tricks.com/accessible-svgs/#aa-complex-images-an-accessible-graph"/>
	<rdf:li rdf:resource="https://haltersweb.github.io/Accessibility/autocomplete.html"/>
	<rdf:li rdf:resource="https://www.dennisdeacon.com/web/accessibility/baby-steps-accessibility-pdfs/"/>
	<rdf:li rdf:resource="https://www.visionaid.co.uk/handheld-video-magnifiers/handyreader-hd"/>
	<rdf:li rdf:resource="https://www.sarasoueidan.com/blog/alt-text-for-css-generated-content/"/>
	<rdf:li rdf:resource="https://pac.pdf-accessibility.org/en/download"/>
	<rdf:li rdf:resource="https://www.tpgi.com/tables-beyond-rows-and-columns/"/>
	<rdf:li rdf:resource="https://www.dennisdeacon.com/web/accessibility/testing-methods-reflow/"/>
	<rdf:li rdf:resource="https://intopia.digital/articles/user-testing-with-people-with-disabilities/"/>
	<rdf:li rdf:resource="https://www.a11y-collective.com/blog/visually-hidden/"/>
	<rdf:li rdf:resource="https://afixt.com/ada-title-ii-and-pdfs-fix-archive-or-delete/"/>
	<rdf:li rdf:resource="https://a11yalt.ai/"/>
	<rdf:li rdf:resource="https://alttext.ai/"/>
	<rdf:li rdf:resource="https://gptforwork.com/blog/bulk-write-alt-text-chatgpt-excel-google-sheets"/>
	<rdf:li rdf:resource="https://ui.shadcn.com/"/>
	<rdf:li rdf:resource="https://draft-ui.com/"/>
	<rdf:li rdf:resource="https://lion-web.netlify.app/"/>
	<rdf:li rdf:resource="https://adrianroselli.com/2023/06/under-engineered-comboboxen.html"/>
	<rdf:li rdf:resource="https://ariakit.org/"/>
	<rdf:li rdf:resource="https://blog.usablenet.com/2025-midyear-accessibility-lawsuit-report-key-legal-trends"/>
	<rdf:li rdf:resource="https://www.tpgi.com/client-side-routing-accessibility/"/>
	<rdf:li rdf:resource="https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Inflation/td-p/2614730#main"/>
	<rdf:li rdf:resource="https://scribe.rip/14-logic-driven-ui-design-tips-145ee08ea5a5"/>
	<rdf:li rdf:resource="https://datasavvy.me/"/>
	<rdf:li rdf:resource="https://medium.com/san-francisco-digital-services/a-template-for-accessible-data-visualizations-ca2ed52f945b"/>
	<rdf:li rdf:resource="https://datasavvy.me/2018/06/06/power-bi-report-accessibility-checklist/"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=VAvkyGGX8IE"/>
	<rdf:li rdf:resource="https://rklein324.github.io/PowerBIAccessibility/"/>
	<rdf:li rdf:resource="https://accessibleweb.com/ramp-web-accessibility-tools/discover-accessibility-issues/"/>
	<rdf:li rdf:resource="https://thepaciellogroup.github.io/cupper/"/>
	<rdf:li rdf:resource="https://adrianroselli.com/2025/01/aria-description-does-not-translate.html"/>
	<rdf:li rdf:resource="https://www.elevenways.be/en/articles/screenreaders-special-characters"/>
	<rdf:li rdf:resource="https://adrianroselli.com/2019/05/uniquely-labeling-fields-in-a-table.html#Update01"/>
	<rdf:li rdf:resource="https://buttondown.com/access-ability/archive/pseudomotion-motion-sensitivity-and-accessibility/"/>
	<rdf:li rdf:resource="https://wagtail.org/blog/htmx-accessibility-gaps-data-and-recommendations/"/>
	<rdf:li rdf:resource="https://www.evinced.com/blog/why-u-s-companies-need-to-pay-attention-to-the-eaa"/>
	<rdf:li rdf:resource="https://dev.to/steady5063/ios-accessibility-inspector-beyond-automation-2cl2"/>
	<rdf:li rdf:resource="https://afixt.com/how-to-write-alt-text-for-complex-images-a-guide-to-clarity-and-accessibility/"/>
	<rdf:li rdf:resource="https://accessdefense.com/?p=6567"/>
	<rdf:li rdf:resource="https://karlgroves.com/digital-accessibility-is-a-civil-right/"/>
	<rdf:li rdf:resource="https://karlgroves.com/ai-is-the-future-of-accessibility/"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=LRJ_DBKPAyQ"/>
	<rdf:li rdf:resource="https://adrianroselli.com/2025/06/where-to-put-focus-when-opening-a-modal-dialog.html"/>
	<rdf:li rdf:resource="https://www.fromdev.com/2023/06/improving-accessibility-with-javascriptvoid0-for-javascript-links.html"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=Uaqo4FOI_DY"/>
	<rdf:li rdf:resource="https://londonwebstandards.org/talks/shift-left-on-accessibility/"/>
	<rdf:li rdf:resource="https://karlgroves.com/a-deep-dive-into-the-websites-and-software-applications-accessibility-act-of-2025/"/>
	<rdf:li rdf:resource="https://mayank.co/notes/popover-vs-dialog/"/>
	<rdf:li rdf:resource="https://karlgroves.com/the-european-accessibility-act-and-b2b-software-what-internal-platforms-must-comply-with/"/>
	<rdf:li rdf:resource="https://www.nira11y.com/post/the-4-motivations-for-accessibility-the-big-why"/>
	<rdf:li rdf:resource="https://www.nira11y.com/post/the-challenge-of-measuring-accessibility-impact"/>
	<rdf:li rdf:resource="https://www.parliament.uk/about/living-heritage/building/cultural-collections/historic-furniture/the-collection/chairs-chairs-chairs/"/>
	<rdf:li rdf:resource="https://a11y-audits.com/"/>
	<rdf:li rdf:resource="https://www.w3.org/WAI/demos/bad/"/>
	<rdf:li rdf:resource="https://emailmarkup.org/en/reports/accessibility/2025/"/>
	<rdf:li rdf:resource="https://equalizedigital.com/accessibility-checker/improper-use-of-link/"/>
	<rdf:li rdf:resource="https://overlays.dnikub.dev/#conclusion"/>
	<rdf:li rdf:resource="https://www.linkedin.com/feed/update/activity:7329407855357272065/?commentUrn=urn%3Ali%3Acomment%3A%28urn%3Ali%3Aactivity%3A7329407855357272065%2C7329516523000127488%29&amp;dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287329407855357272065%2C7329516523000127488%29%2C7329407855357272065%29&amp;origin=COMMENTS_BY_YOUR_NETWORK&amp;midToken=AQGfCjslg0iVRw&amp;midSig=3lQRgBFMh1trM1&amp;trk=eml-email_notification_digest_01-hero_notification_cta-0-COMMENTS_BY_YOUR_NETWORK&amp;trkEmail=eml-email_notification_digest_01-hero_notification_cta-0-COMMENTS_BY_YOUR_NETWORK-null-ndsj~mavfltko~dr-null-null&amp;eid=ndsj-mavfltko-dr&amp;otpToken=MTMwNTE3ZTAxYjI4Y2FjZWI1MjkwMWVkNDAxNmU3YjU4ZWNhZDA0ODlmYTQ4YTZjNzFjMjA5Njg0NjVhNWVmM2ZjYWZiMzliMTNjMmU1ZjA2NjU3OWNkZmFhYzQyN2ZiODg4YTg3Y2FmNDhhOGM5NWFjLDEsMQ%3D%3D"/>
	<rdf:li rdf:resource="https://blog.pope.tech/2025/04/30/remediate-a-pdf-for-accessibility-using-adobes-accessibility-checker/"/>
	<rdf:li rdf:resource="https://github.blog/engineering/user-experience/considerations-for-making-a-tree-view-component-accessible/"/>
	<rdf:li rdf:resource="https://ux.stackexchange.com/questions/145088/hiding-duplicate-links-with-aria-hidden/145099#145099"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://dev.to/mfairchild365/ai-generated-accessibility-an-update-frontier-models-still-fail-but-skills-change-the-game-5629">
    <title>AI-generated accessibility, an update — frontier models still fail, but skills change the game - DEV Community</title>
    <dc:date>2026-06-25T09:49:43+00:00</dc:date>
    <link>https://dev.to/mfairchild365/ai-generated-accessibility-an-update-frontier-models-still-fail-but-skills-change-the-game-5629</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[A few months ago I shared early results from the A11y LLM Eval project, a benchmark that measures how accessibly LLMs generate UI code. The previous post showed that LLMs default to inaccessible code, explicit accessibility instructions can dramatically change that, and manual testing is still essential.

The latest report is out, with new models, a redesigned test scope, and a brand new mechanic: skills. Two things stand out:

    The newest frontier models (GPT‑5.5, Claude Opus 4.7, Gemini 3.1 Pro Preview, Claude Haiku 4.5, and others) still fail accessibility checks by default.
    A well-written skill can produce the highest pass rates we've measured. Skills can even let a weak-baseline model outperform the leaders, though they can cost more tokens to run.]]></description>
<dc:subject>a11y accessibility LLM GenAI Claude GPT code HTML skill instructions microsoft</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:0dc043c5c19b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:LLM"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:GenAI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:Claude"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:GPT"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:HTML"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:skill"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:instructions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:microsoft"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.jeana.dev/thoughts/2026/05/fieldsets-legends/">
    <title>Thoughts - Jeana Clark Portfolio</title>
    <dc:date>2026-06-02T16:20:41+00:00</dc:date>
    <link>https://www.jeana.dev/thoughts/2026/05/fieldsets-legends/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[The goal is to use fieldsets where they add meaning and skip them where they don't — which requires understanding what they're for. A <fieldset> and <legend> are not an accessibility checkbox. They're a mechanism for giving grouped controls a shared name that the individual labels can't provide. Used correctly, they make forms significantly easier to navigate for assistive technology users. Used incorrectly, they add noise that makes forms harder to navigate.]]></description>
<dc:subject>fieldset legend accessibility a11y</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:d3f3066e065c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:fieldset"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:legend"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://veroniiiica.com/using-kagi-search-with-low-vision/">
    <title>Using Kagi Search With Low Vision | Veronica With Four Eyes</title>
    <dc:date>2026-05-22T10:24:20+00:00</dc:date>
    <link>https://veroniiiica.com/using-kagi-search-with-low-vision/</link>
    <dc:creator>fjordaan</dc:creator><dc:subject>search accessibility kagi engine customisation keyboard shortcuts</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:43a4b3fe273b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:kagi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:engine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:customisation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:keyboard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:shortcuts"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://webaim.org/techniques/headings/">
    <title>WebAIM: Headings</title>
    <dc:date>2026-05-14T09:57:50+00:00</dc:date>
    <link>https://webaim.org/techniques/headings/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[When a user encounters a webpage, they want to confirm that the page includes relevant information and find that information quickly. Headings create an outline for the page, similar to a term paper outline or table of contents.

While sighted users typically determine a page's content and structure by scanning for large text that look likes headings, screen reader users rely on the page's underlying semantic structure for navigation. Users with motor or other disabilities might also navigate or explore a page by headings. Headings are also used by search engines to determine page content.]]></description>
<dc:subject>accessibility headings hierarchy a11y</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:d20dad8209a3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:headings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:hierarchy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://webaim.org/techniques/headings/#missingh1">
    <title>WebAIM: Headings</title>
    <dc:date>2026-05-14T09:57:41+00:00</dc:date>
    <link>https://webaim.org/techniques/headings/#missingh1</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[When a user encounters a webpage, they want to confirm that the page includes relevant information and find that information quickly. Headings create an outline for the page, similar to a term paper outline or table of contents.

While sighted users typically determine a page's content and structure by scanning for large text that look likes headings, screen reader users rely on the page's underlying semantic structure for navigation. Users with motor or other disabilities might also navigate or explore a page by headings. Headings are also used by search engines to determine page content.]]></description>
<dc:subject>accessibility headings hierarchy a11y</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:26219d3e4b6c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:headings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:hierarchy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://annaecook.com/writing/2026/ai-doesnt-fix-accessible-systems-it-depends-on-them">
    <title>AI Doesn't Fix Accessible Systems. It Depends on Them. — Anna E. Cook</title>
    <dc:date>2026-05-12T09:08:10+00:00</dc:date>
    <link>https://annaecook.com/writing/2026/ai-doesnt-fix-accessible-systems-it-depends-on-them</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[LLMs and Gen AI have been trained on a highly inaccessible and deeply flawed dataset — publicly available “free” data on the good ol’ World Wide Web.  
LLMs learned from a web that was already broken. That is the structural debt AI is now inheriting and reproducing at scale. The next generation will learn from one that's gotten worse.]]></description>
<dc:subject>a11y ai accessibility flaws llm training</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:f93324294333/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:flaws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:llm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:training"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.deque.com/blog/unique-id-attributes-matter/">
    <title>Why Unique ID Attributes Matter</title>
    <dc:date>2026-04-22T09:09:26+00:00</dc:date>
    <link>https://www.deque.com/blog/unique-id-attributes-matter/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Duplicate IDs of the most common WCAG 4.1.1 violations reported by automated accessibility testing tools such as axe, and it can cause a fair share of problems for your users. It happens when more than one element on the webpage have the same ID attribute. People often ask me how these seemingly innocuous ambiguous IDs can cause so many problems.]]></description>
<dc:subject>accessibility a11y form field label id ids deque</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:e79aa8fec2ee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:form"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:field"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:label"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:id"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ids"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:deque"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tarnoff.info/2026/03/10/quick-tip-dialog-focus/">
    <title>Quick Tip: Dialog Focus – Nat Tarnoff</title>
    <dc:date>2026-04-14T08:16:34+00:00</dc:date>
    <link>https://tarnoff.info/2026/03/10/quick-tip-dialog-focus/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[I recommend placing the focus on the heading of the dialog. We do this by providing a proper ID and tabindex="-1". Now when the user opens the cart dialog they would hear something like “Dialog, Shopping Cart.” This tells me my focus has shifted due to my actions, where the focus went by identifying, and I’m not hit with the confusing close button. ]]></description>
<dc:subject>accessibility dialog focus a11y</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:dc611e4a7e00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:dialog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:focus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://social.tupo.space/@joshua/116057389741775295">
    <title>Joshua Jung: &quot;@stroughtonsmith I am slowly l…&quot; - Tupo Space Mastodon</title>
    <dc:date>2026-02-16T09:44:10+00:00</dc:date>
    <link>https://social.tupo.space/@joshua/116057389741775295</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[I am slowly losing dexterity in my hands due to a neurological condition. Being able to code via prose or even voice is a huge game changer for me. This may not destroy, but save my career in thong run. I feel like we don’t talk  enough about the accessibility angle of agentic coding.]]></description>
<dc:subject>accessibility genAI LLM</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:be36333d4a6e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:genAI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:LLM"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://css-tricks.com/accessible-svgs/#aa-complex-images-an-accessible-graph">
    <title>Complex images – An Accessible Graph ¬ Accessible SVGs | CSS-Tricks</title>
    <dc:date>2025-12-12T15:44:37+00:00</dc:date>
    <link>https://css-tricks.com/accessible-svgs/#aa-complex-images-an-accessible-graph</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[It’s great that we can use SVGs instead of PNGs and JPGs, especially when it comes to complex web content like a graph. It would be excessive to provide all of this info in the alt attribute, so providing alternative text for this image (as a png/jpg) would be tricky. Instead, we can use an SVG and make all of that text directly accessible! ]]></description>
<dc:subject>accessibility charts graphs svg</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:29022aeade17/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:charts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:graphs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:svg"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://haltersweb.github.io/Accessibility/autocomplete.html">
    <title>Accessible Autocomplete</title>
    <dc:date>2025-12-09T16:47:50+00:00</dc:date>
    <link>https://haltersweb.github.io/Accessibility/autocomplete.html</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[This is an accessible autocomplete which works with keyboard, screen readers, switch devices, and touch screens.]]></description>
<dc:subject>autocomplete accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:b5569a492c8a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:autocomplete"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.dennisdeacon.com/web/accessibility/baby-steps-accessibility-pdfs/">
    <title>Baby Steps Accessibility - PDFs - Dennis Deacon</title>
    <dc:date>2025-11-05T14:41:44+00:00</dc:date>
    <link>https://www.dennisdeacon.com/web/accessibility/baby-steps-accessibility-pdfs/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Before we begin, let me set expectations. This isn’t a step-by-step tutorial on how to remediate a PDF. Instead, my goal is to provide a strategic framework, one that helps organizations prepare, prioritize, and take meaningful action on PDF accessibility. And here’s a reality check: unless you’ve been creating accessible PDFs for years, chances are most of your files are not accessible. ]]></description>
<dc:subject>PDF accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:3ec8083872fe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PDF"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.visionaid.co.uk/handheld-video-magnifiers/handyreader-hd">
    <title>HandyReader HD | VisionAid</title>
    <dc:date>2025-11-04T11:09:41+00:00</dc:date>
    <link>https://www.visionaid.co.uk/handheld-video-magnifiers/handyreader-hd</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[The HandyReader HD is a great value handheld video magnifier system. 

It has tactile controls which ensure that it is easy to operate for all users and the high contrast 3.5" screen with up to 24x magnification allow for easy viewing of all objects and text. The television out feature (cable included) also lets you connect it to any television set to make reading of longer documents more comfortable. This device is small and compact so it is ideal for use while on the go. You can put the device in your pocket or handbag and use it while in the supermarket to magnify and read information on food packets. It is also a useful tool to read medicine bottles so it is perfect for use in the home too. ]]></description>
<dc:subject>accessibility magnifier magnifying lens zoom</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:943c6e5c23ab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:magnifier"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:magnifying"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:lens"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:zoom"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.sarasoueidan.com/blog/alt-text-for-css-generated-content/">
    <title>CSS to speech: alternative text for CSS-generated content</title>
    <dc:date>2025-10-28T09:44:38+00:00</dc:date>
    <link>https://www.sarasoueidan.com/blog/alt-text-for-css-generated-content/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[This is a 101 post on when and how to use the slash content property syntax in CSS to provide alt text for CSS-generated content, and why it is important.]]></description>
<dc:subject>CSS generated content accessibility sara soueidan sarasoueidan</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:e8477d142245/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:CSS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:generated"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:content"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:sara"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:soueidan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:sarasoueidan"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pac.pdf-accessibility.org/en/download">
    <title>Download - PAC PDF accessibility checker</title>
    <dc:date>2025-10-23T08:51:52+00:00</dc:date>
    <link>https://pac.pdf-accessibility.org/en/download</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[PAC 2026 beta with AI-assisted checks is here!
PAC 2026 takes PDF accessibility testing to a new level.
For years, PAC has been a globally recognized standard product for machine-based testing according to the Matterhorn Protocol.
In the new 2026 version, PAC now also supports you with the human evaluation tasks through integrated AI.]]></description>
<dc:subject>pdf windows accessibility checker</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:071e1006bbc2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:windows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:checker"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.tpgi.com/tables-beyond-rows-and-columns/">
    <title>Tables: Beyond Rows and Columns - TPGi — a Vispero company</title>
    <dc:date>2025-10-20T13:48:53+00:00</dc:date>
    <link>https://www.tpgi.com/tables-beyond-rows-and-columns/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[There are many semantic HTML tags covered under WCAG SC 1.3.1: Info and Relationships, but in this article, we’ll zoom in on one of the most misunderstood, the table.]]></description>
<dc:subject>accessibility tables</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:fe2db6de2bf3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:tables"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.dennisdeacon.com/web/accessibility/testing-methods-reflow/">
    <title>Testing Methods: Reflow - Dennis Deacon</title>
    <dc:date>2025-10-20T13:32:20+00:00</dc:date>
    <link>https://www.dennisdeacon.com/web/accessibility/testing-methods-reflow/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[WCAG 1.4.10 Reflow is a Level AA conformance level Success Criterion. It requires that content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions, when viewed at a width equivalent to 320 CSS pixels (typically a small mobile screen). This ensures that users can zoom in or use devices with smaller screens without encountering horizontal scrolling or content cut off the screen. ]]></description>
<dc:subject>accessibility reflow testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:9f090d16db0b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:reflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:testing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://intopia.digital/articles/user-testing-with-people-with-disabilities/">
    <title>How to conduct user testing with people with disabilities - Intopia</title>
    <dc:date>2025-10-20T13:30:26+00:00</dc:date>
    <link>https://intopia.digital/articles/user-testing-with-people-with-disabilities/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Here’s how to approach user testing with people with disabilities so you get the most valuable feedback, for both your team and your participants.]]></description>
<dc:subject>usertesting user testing disabilities inclusive accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:ca3a039d99d1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:usertesting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:user"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:disabilities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:inclusive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.a11y-collective.com/blog/visually-hidden/">
    <title>Essential Visually Hidden CSS Techniques for Web Accessibility</title>
    <dc:date>2025-10-20T13:28:49+00:00</dc:date>
    <link>https://www.a11y-collective.com/blog/visually-hidden/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Fix vanishing focus indicators & conflicting sr-only classes. Learn the 3-state visibility model that transforms CSS hacks into logical accessibility decisions.]]></description>
<dc:subject>visually hidden accessibility sr-only</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:3df3201da1b1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:visually"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:hidden"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:sr-only"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://afixt.com/ada-title-ii-and-pdfs-fix-archive-or-delete/">
    <title>ADA Title II and PDFs: Fix, Archive, or Delete? - AFixt AFixt, Inc. offers a full array of services for regulations and standards such as ADA, WCAG, EAA, AODA, and EN 301 549</title>
    <dc:date>2025-10-20T13:27:23+00:00</dc:date>
    <link>https://afixt.com/ada-title-ii-and-pdfs-fix-archive-or-delete/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Imagine you work for a state government agency. Over the years, your department has diligently published reports, meeting minutes, forms, budget documents, and countless other materials as PDFs. A quick inventory shows thousands of them – some from last week, others dating back more than a decade. At the time they were created, nobody thought much about accessibility. The priority was getting information online quickly. Fast forward to today, with a looming deadline to comply to new requirements around Title II of the Americans with Disabilities Act, and suddenly those PDFs feel less like a public service and more like a compliance headache. The natural question is: what now? Do you fix all those PDFs, even the dusty ones from 2009? Do you shove them into an archive and hope for the best? Or do you quietly start deleting? ]]></description>
<dc:subject>PDF accessibility remediation government ADA karlgroves</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:fd676d136a11/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PDF"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:remediation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:government"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ADA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:karlgroves"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://a11yalt.ai/">
    <title>[untitled]</title>
    <dc:date>2025-10-20T09:32:23+00:00</dc:date>
    <link>https://a11yalt.ai/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Image Alt Text at Scale: AI-Powered Inclusive Content
At Zenyth, we provide advanced alt text solutions that make vast image catalogs accessible and inclusive. Our AI-driven capabilities deliver accurate, context-rich text alternatives, scaling effortlessly from hundreds to tens of thousands of images. ]]></description>
<dc:subject>alt text generator accessibility a11y image description ai shopify wordpress magento</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:1564cc275443/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:alt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:generator"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:image"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:shopify"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:wordpress"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:magento"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://alttext.ai/">
    <title>Free Alt Text Image Generator 130+ Languages</title>
    <dc:date>2025-10-20T09:31:44+00:00</dc:date>
    <link>https://alttext.ai/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Automatically generate alt text for images in over 130 languages. ]]></description>
<dc:subject>alt tool generator ai images accessibility a11y description</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:36d9aeab8d8c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:alt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:tool"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:generator"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:images"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:description"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gptforwork.com/blog/bulk-write-alt-text-chatgpt-excel-google-sheets">
    <title>Use AI to Bulk Write Alt Text in Excel and Google Sheets</title>
    <dc:date>2025-09-01T13:04:57+00:00</dc:date>
    <link>https://gptforwork.com/blog/bulk-write-alt-text-chatgpt-excel-google-sheets</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Use GPT for Sheets’ GPT_VISION function in Google Sheets to automatically generate alt text for e-commerce applications. Alt text will improve your website’s accessibility, which benefits users and improves your SEO ranking.]]></description>
<dc:subject>alt text accessibility ChatGPT automation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:1b41e09725c3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:alt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ChatGPT"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:automation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ui.shadcn.com/">
    <title>The Foundation for your Design System - shadcn/ui</title>
    <dc:date>2025-07-30T13:11:27+00:00</dc:date>
    <link>https://ui.shadcn.com/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[A set of beautifully designed components that you can customize, extend, and build on. Start here then make it your own. Open Source. Open Code.]]></description>
<dc:subject>components framework ui library radix accessible accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:ab3ddbc4f6d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:radix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessible"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://draft-ui.com/">
    <title>Draft UI</title>
    <dc:date>2025-07-30T13:07:32+00:00</dc:date>
    <link>https://draft-ui.com/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Draft UI is a collection of simply designed React components focused on making web accessibility as easy as copy & paste.]]></description>
<dc:subject>libraries components library html framework React accessible accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:683922005cc7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:React"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessible"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lion-web.netlify.app/">
    <title>Lion - Fundamental white label web components for building your design system</title>
    <dc:date>2025-07-30T13:04:41+00:00</dc:date>
    <link>https://lion-web.netlify.app/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[ All of our components align to platform standards, WAI ARIA patterns, and are always tested on accessibility, both through aXe automated tests but also manually with screen readers. ]]></description>
<dc:subject>components javascript accessibility ui html library framework accessible</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:b2cd26fa5246/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessible"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://adrianroselli.com/2023/06/under-engineered-comboboxen.html">
    <title>Under-Engineered Comboboxen? — Adrian Roselli</title>
    <dc:date>2025-07-30T10:02:16+00:00</dc:date>
    <link>https://adrianroselli.com/2023/06/under-engineered-comboboxen.html</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[ Unlike all my other Under-Engineered posts, this one is not a “how-to”. This is a “what’s-up”, so you can make a decision about whether or not you want to give <datalist> a shot. ]]></description>
<dc:subject>components forms accessibility combobox listbox select autocomplete input</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:9bd6ee10eff3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:forms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:combobox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:listbox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:select"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:autocomplete"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:input"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ariakit.org/">
    <title>Ariakit - Toolkit for building accessible UIs</title>
    <dc:date>2025-07-30T09:54:51+00:00</dc:date>
    <link>https://ariakit.org/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Open-source library with unstyled, primitive components, with a collection of styled examples that you can copy and paste into your apps.]]></description>
<dc:subject>sass components aria system a11y ui library javascript accessibility react</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:8a41ef3b7605/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:aria"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:system"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:library"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:react"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.usablenet.com/2025-midyear-accessibility-lawsuit-report-key-legal-trends">
    <title>2025 Midyear Accessibility Lawsuit Report: Key Legal Trends | UsableNet, Inc.</title>
    <dc:date>2025-07-29T15:16:25+00:00</dc:date>
    <link>https://blog.usablenet.com/2025-midyear-accessibility-lawsuit-report-key-legal-trends</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[The numbers are in: digital accessibility lawsuits are on track to surge nearly 20% in 2025, with over 2,000 cases already filed in the first half of the year. UsableNet’s Midyear ADA Lawsuit Report offers the most detailed view into this growing legal risk. Now in its sixth year, the report is built from the ground up by manually reviewing digital accessibility lawsuits in the U.S. to identify those involving websites, mobile apps, digital video, or physical spaces.]]></description>
<dc:subject>accessibility lawsuits legal overlays widgets ecommerce ecom</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:31052b850b20/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:lawsuits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:overlays"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:widgets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ecommerce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ecom"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.tpgi.com/client-side-routing-accessibility/">
    <title>Improving Client-side Page Routing for Better Accessibility - TPGi</title>
    <dc:date>2025-07-29T15:09:56+00:00</dc:date>
    <link>https://www.tpgi.com/client-side-routing-accessibility/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[For those that may not be familiar, client-side routing is where navigating between pages happens dynamically instead of your browser making separate requests to the web server. For example, your page-specific markup might be wrapped in a particular <div> element. When moving between pages, the JavaScript framework would swap out that <div> with another that contains the markup for a different page. All of this happens inside your browser because it has already downloaded the markup for each page in your app. Traditional page loading on the other hand would have your browser reach out to the web server to grab new markup each time you load a new page.]]></description>
<dc:subject>SPA accessibility React reload dynamic</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:e96a5d16830e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:SPA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:React"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:reload"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:dynamic"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Inflation/td-p/2614730#main">
    <title>Inflation - Microsoft Fabric Community</title>
    <dc:date>2025-07-17T11:47:54+00:00</dc:date>
    <link>https://community.fabric.microsoft.com/t5/Data-Stories-Gallery/Inflation/td-p/2614730#main</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[In this work, an analysis was carried out, where a data set was selected, including information on socio-economic indicators in the countries of our world. You will be presented with one screen where you can see basic information about the situation in each state. At the top of our screen, the main indicators are shown for a successful analysis, and at the bottom, for a more convenient presentation, all our data is summarized in one common table.
This dashboard is based on real data and created as part of a curriculum.]]></description>
<dc:subject>PowerBI accessibility dashboard report example</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:4544ec919aef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PowerBI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:dashboard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:report"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:example"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://scribe.rip/14-logic-driven-ui-design-tips-145ee08ea5a5">
    <title>14 logic-driven UI design tips to improve any interface</title>
    <dc:date>2025-07-11T08:24:48+00:00</dc:date>
    <link>https://scribe.rip/14-logic-driven-ui-design-tips-145ee08ea5a5</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Designing user interfaces is no easy task. With countless choices around layout, spacing, typography, and colour, it’s easy to feel overwhelmed. And when you layer in considerations like usability, accessibility, and human psychology, the challenge only grows.
Even if you don’t have much experience with UI design, you can probably tell that the original design just doesn’t feel “right”. That’s because it contains a bunch of design flaws that can negatively impact usability. You might already have spotted some of them.]]></description>
<dc:subject>usability accessibility design UI UX tips redesign mobile gestalt letter spacing letterspacing buttons</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:e8b637ab27c2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:UI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:UX"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:tips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:redesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:gestalt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:letter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:spacing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:letterspacing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:buttons"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://datasavvy.me/">
    <title>Data Savvy - My experiences and education in data modeling, integration, transformation, analysis, and visualization</title>
    <dc:date>2025-07-08T09:48:09+00:00</dc:date>
    <link>https://datasavvy.me/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[ My experiences and education in data modeling, integration, transformation, analysis, and visualization 
I’m Meagan Longoria, an analytics and data engineering consultant with Denny Cherry & Associates Consulting and a Microsoft MVP who helps people understand their data and use it to learn and make better decisions. I focus on the Microsoft data platform, doing data modeling, data lakehouse, and data warehouse design, as well as semantic models, and data visualization. I spend a lot of time thinking about how to use data integration and data visualization techniques to make data useful for people. I enjoy sharing my knowledge and experiences at conferences and user group meetings as well as through this blog. This blog is my place to share interesting links, knowledge, and experiences with BI and data tools and concepts. See the Presentations pages for more information on my presentations and past events.]]></description>
<dc:subject>accessibility dataviz PowerBI Microsoft data visualisation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:cc9523ba2d6c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:dataviz"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PowerBI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:Microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:visualisation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/san-francisco-digital-services/a-template-for-accessible-data-visualizations-ca2ed52f945b">
    <title>A template for accessible data visualizations | by Lauren Jong | San Francisco Digital &amp; Data Services | Medium</title>
    <dc:date>2025-07-08T09:47:01+00:00</dc:date>
    <link>https://medium.com/san-francisco-digital-services/a-template-for-accessible-data-visualizations-ca2ed52f945b</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Here are some of the key improvements that made our data and reports more accessible and easy to use:
    1. Consistent dashboard layouts
    2. Focused, simple data visualizations
    3. Accessible text to support the data
    4. Mobile responsive dashboards
    5. Special care to accessibility for screen readers
    6. Templates and guidance to streamline adoption
We published everything we learned in the Public Data Visualization Guide to make it easy for analysts and dashboard creators to replicate. Details about our best practices, PowerBI tips, and specific recommendations are in the guide.]]></description>
<dc:subject>dataviz a11y accessibility SanFrancisco SF public data visualisation PowerBI Covid dashboard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:241157180654/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:dataviz"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:SanFrancisco"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:SF"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:public"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:visualisation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PowerBI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:Covid"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:dashboard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://datasavvy.me/2018/06/06/power-bi-report-accessibility-checklist/">
    <title>Power BI Report Accessibility Checklist - Data Savvy</title>
    <dc:date>2025-07-08T09:42:43+00:00</dc:date>
    <link>https://datasavvy.me/2018/06/06/power-bi-report-accessibility-checklist/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[In many cases, some small changes can go a long way in making your Power BI reports more accessible for users with different abilities. The checklist below lists considerations you should make in your report design to create more inclusive reports. I’ll update this post as new features are released.]]></description>
<dc:subject>PowerBI accessibility a11y charts</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:b00690f015cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PowerBI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:charts"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=VAvkyGGX8IE">
    <title>Creating Accessible Power BI Reports with Meagan Longoria - YouTube</title>
    <dc:date>2025-07-08T09:36:28+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=VAvkyGGX8IE</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Accessibility is catering for your whole audience, including those with disabilities. According to the US Census Bureau, 19 percent of the of the population had a disability in 2010. Do you know if your reports are designed in an inclusive way such that everyone in your intended audience can use them? While this question is relevant for every organization, this can be especially important if you are making reports for government entities, educational institutions, or the general public. In this session, we'll discuss accessibility features available in Power BI today and how to design your Power BI reports with inclusiveness in mind.]]></description>
<dc:subject>PowerBI accessibility a11y video webinar microsoft</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:ff089a33d654/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PowerBI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:webinar"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:microsoft"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://rklein324.github.io/PowerBIAccessibility/">
    <title>Power BI Accessibility Best Practices | PowerBIAccessibility</title>
    <dc:date>2025-07-08T09:31:11+00:00</dc:date>
    <link>https://rklein324.github.io/PowerBIAccessibility/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[This document is a guide to the best practices for creating accessible data visualizations and data reporting, specifically for Microsoft Power BI. This includes WCAG requirements and suggestions for how to best create a report to be accessible, as well as steps on how to fix these issues within Power BI. There are two sections directly related to our chrome extension - PowBility:]]></description>
<dc:subject>PowerBI accessibility a11y charts</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:e9abadd53ff8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PowerBI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:charts"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://accessibleweb.com/ramp-web-accessibility-tools/discover-accessibility-issues/">
    <title>Discover Web Accessibility Issues | Accessible Web RAMP</title>
    <dc:date>2025-07-04T14:16:37+00:00</dc:date>
    <link>https://accessibleweb.com/ramp-web-accessibility-tools/discover-accessibility-issues/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Start your accessibility work by discovering issues with our digital accessibility tools. Automated scanning detects violations, Recommended Action Items prioritizes the findings, & the Accessible Web Helper browser extension highlights the failures with a push of a button.]]></description>
<dc:subject>accessibility checker documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:b8abe1afc1d7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:checker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://thepaciellogroup.github.io/cupper/">
    <title>Cupper</title>
    <dc:date>2025-07-04T14:09:01+00:00</dc:date>
    <link>https://thepaciellogroup.github.io/cupper/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Welcome to Cupper: a documentation builder for inclusive designers and those trying to be inclusive designers. These are Cupper’s docs, but they are also an example of a site built with Cupper. Here are some of its features:]]></description>
<dc:subject>documentation docs builder pdf generator a11y accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:842220158a9d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:docs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:builder"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:generator"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://adrianroselli.com/2025/01/aria-description-does-not-translate.html">
    <title>aria-description Does Not Translate — Adrian Roselli</title>
    <dc:date>2025-07-02T16:14:58+00:00</dc:date>
    <link>https://adrianroselli.com/2025/01/aria-description-does-not-translate.html</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[ Content buried in aria-label, aria-placeholder, aria-roledescription, or aria-valuetext can end up being presented to users in a language different than their own. The very thing we add to help users can exclude them instead. ]]></description>
<dc:subject>aria accessibility internationalisation localisation translation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:05c4734ed5c8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:aria"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:internationalisation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:localisation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:translation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.elevenways.be/en/articles/screenreaders-special-characters">
    <title>How screen readers read special characters: an update | Eleven Ways</title>
    <dc:date>2025-07-02T15:51:37+00:00</dc:date>
    <link>https://www.elevenways.be/en/articles/screenreaders-special-characters</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Screen readers interpret what is on the screen. They can read most text easily and accurately, but how do they handle special punctuation and characters? Let's find out!]]></description>
<dc:subject>accessibility a11y entities special characters screenreaders theme agency experts</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:613b60ca9da4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:entities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:special"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:characters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:screenreaders"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:theme"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:agency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:experts"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://adrianroselli.com/2019/05/uniquely-labeling-fields-in-a-table.html#Update01">
    <title>Uniquely Labeling Fields in a Table — Adrian Roselli</title>
    <dc:date>2025-07-01T11:12:16+00:00</dc:date>
    <link>https://adrianroselli.com/2019/05/uniquely-labeling-fields-in-a-table.html#Update01</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[ The good news here is that if you are creating tables correctly, there isn’t much extra work you need to do. Your column and row headers, paired with some ARIA, can do the job for you. I made a demo to show it in action, embedded below or directly at Codepen. ]]></description>
<dc:subject>accessibility aria table form inputs fields</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:8cb839bb9c3f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:aria"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:table"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:form"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:inputs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:fields"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://buttondown.com/access-ability/archive/pseudomotion-motion-sensitivity-and-accessibility/">
    <title>Pseudomotion, Motion Sensitivity, and Accessibility • Buttondown</title>
    <dc:date>2025-06-30T13:10:29+00:00</dc:date>
    <link>https://buttondown.com/access-ability/archive/pseudomotion-motion-sensitivity-and-accessibility/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Motion sensitivity is a condition that affects a significant number of people, including those with vestibular disorders, migraines, epilepsy, and other neurological conditions. For these individuals, both real and simulated motion can trigger symptoms such as nausea, dizziness, vertigo, migraines, or even seizures.
Pseudomotion is the illusion of movement created by design elements. It can be every bit as harmful as actual motion. While pseudomotion is not a widely recognized term, these examples of pseudomotion are well-known. They include:
Parallax Scrolling
Sharp Color Changes
Dynamically Updating Content
Zoom Effects or Transitions]]></description>
<dc:subject>motion accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:e109fb4e97cb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:motion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://wagtail.org/blog/htmx-accessibility-gaps-data-and-recommendations/">
    <title>htmx accessibility gaps: data and recommendations | Wagtail CMS</title>
    <dc:date>2025-06-27T11:20:49+00:00</dc:date>
    <link>https://wagtail.org/blog/htmx-accessibility-gaps-data-and-recommendations/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Every few months I’m asked about possible accessibility issues with a UI built with htmx. It’s super popular in the Django world, so felt worthwhile to take the time to dig deeper! Time to spell out where htmx shines, and where it falls short.]]></description>
<dc:subject>HTMX accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:9d8ae4cf0ccc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:HTMX"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.evinced.com/blog/why-u-s-companies-need-to-pay-attention-to-the-eaa">
    <title>Why U.S. companies need to pay attention to the EAA – Evinced</title>
    <dc:date>2025-06-27T11:19:40+00:00</dc:date>
    <link>https://www.evinced.com/blog/why-u-s-companies-need-to-pay-attention-to-the-eaa</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[If you’re a U.S.-based business, it’s easy to assume that the European Accessibility Act (“EAA”) doesn’t apply to you. 

But if your digital products or services reach consumers in any of the 27 EU member states, that assumption could cost you. The EAA, like the General Data Protection Regulation  (GDPR) before it, has extraterritorial reach. It protects EU residents no matter where a product originates, so any company doing business in the EU, directly or through partners, falls within its scope. ]]></description>
<dc:subject>EAA accessibility legislation USA US</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:7cebc8eeedae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:EAA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:legislation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:USA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:US"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://dev.to/steady5063/ios-accessibility-inspector-beyond-automation-2cl2">
    <title>iOS Accessibility Inspector: Beyond Automation - DEV Community</title>
    <dc:date>2025-06-24T09:09:12+00:00</dc:date>
    <link>https://dev.to/steady5063/ios-accessibility-inspector-beyond-automation-2cl2</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Xcodes accessibility inspector has long been thought of as only an 'automated' issue tool. This thought has led to its full potential never being fully met by developers and testers. So if it's more than just automated issues, then what should users be doing with it to catch more accessibility bugs? Let's dive right in. ]]></description>
<dc:subject>iOS accessibility testing macos tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:5b8be7e686c3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:iOS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:macos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://afixt.com/how-to-write-alt-text-for-complex-images-a-guide-to-clarity-and-accessibility/">
    <title>How to Write Alt Text for Complex Images: A Guide to Clarity and Accessibility - AFixt AFixt, Inc. offers a full array of services for regulations and standards such as ADA, WCAG, EAA, AODA, and EN 301 549</title>
    <dc:date>2025-06-20T16:26:15+00:00</dc:date>
    <link>https://afixt.com/how-to-write-alt-text-for-complex-images-a-guide-to-clarity-and-accessibility/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[When it comes to simple images—like icons, buttons, or decorative visuals—writing alt text is straightforward. But what about complex images like charts, infographics, maps, and diagrams? These images often carry dense information, and writing effective alt text requires more thought and strategy.

In this post, we’ll break down the best practices for writing clear, concise, and useful alt text for complex images, ensuring that your content is accessible to everyone.]]></description>
<dc:subject>accessibility complex images charts diagrams infographics flowcharts</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:fe36234276b2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:complex"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:images"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:charts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:diagrams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:infographics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:flowcharts"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://accessdefense.com/?p=6567">
    <title>Kiosks and the ADA – evaluating the risk after Davis v Lab Corp – ADA and FHA Defense</title>
    <dc:date>2025-06-16T13:32:33+00:00</dc:date>
    <link>https://accessdefense.com/?p=6567</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Circuit court decisions on ADA cases are sparse when compared to the number of suits filed, and cases involving self-service kiosks are rare, so it isn’t surprising the Ninth Circuit’s decision in Davis et al v. Laboratory Corp. of America Holdings, Case No. 22-55873 (Ninth Circuit, February 8, 2024) has gotten a good deal of attention. Others have looked at the holding itself, but I thought it would be a good opportunity to look at the issue of accessible kiosks generally to see how this case fits with earlier decisions and ask whether it marks a significant change in the law.¹]]></description>
<dc:subject>accessibility kiosks ADA legal law lawsuits</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:c98035b5e479/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:kiosks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ADA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:lawsuits"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://karlgroves.com/digital-accessibility-is-a-civil-right/">
    <title>Digital Accessibility is a Civil Right - Karl Groves</title>
    <dc:date>2025-06-16T13:29:22+00:00</dc:date>
    <link>https://karlgroves.com/digital-accessibility-is-a-civil-right/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Weaponizing Anecdotes Doesn’t Solve Systemic Problems
The article leans heavily on the idea of “serial plaintiffs” and “cash settlements,” implying that most lawsuits are frivolous. I agree that there are a large number of lawyers who are behind a lot of the legal activity around the ADA. Some of those lawyers are involved in doing so for less than noble reasons. But those lawsuits are an indictment of something far worse: a widespread, systemic failure to build accessible digital experiences.]]></description>
<dc:subject>accessibility ADA USA US argument law legal lawsuits</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:c1595c53523a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ADA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:USA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:US"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:argument"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:lawsuits"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://karlgroves.com/ai-is-the-future-of-accessibility/">
    <title>AI is the future of accessibility - Karl Groves</title>
    <dc:date>2025-06-16T13:26:49+00:00</dc:date>
    <link>https://karlgroves.com/ai-is-the-future-of-accessibility/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Imagine a world where screen readers no longer struggle with poorly labeled websites, because AI fills in the blanks with semantic and contextual understanding. Imagine a world where an autistic person’s communication app learns their speech patterns and preferences over time, getting better the more they use it. Where augmented reality glasses provide Deaf users with live captioning layered over the real world. Where a wheelchair user’s smart assistant can understand their preferences, navigate their home, and even advocate on their behalf.

These aren’t far-fetched sci-fi dreams. They’re coming—and in many cases, they’re already here.

So let’s be bold. Let’s be curious. Let’s treat AI not as a threat to accessibility, but as a tool we must shape—because the future belongs to those who build it. Stop being afraid of change and, instead, work to make sure change is for the better.]]></description>
<dc:subject>karl groves karlgroves ai accessibility future</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:84e09c2ce94f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:karl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:groves"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:karlgroves"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:future"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=LRJ_DBKPAyQ">
    <title>Seeing Beyond: Diablo IV's Screen Reader &amp; Navigation Innovation - YouTube</title>
    <dc:date>2025-06-09T15:42:14+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=LRJ_DBKPAyQ</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[This is how Diablo IV designers and engineers worked alongside #accessibility #a11y experts to perfect the advanced screen reader and to develop new tools for navigation assistance, like the addition of the compass and audio enhancements, to ensure players of every capability can save Sanctuary.]]></description>
<dc:subject>videogame game accessibility</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:087b68142502/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:videogame"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:game"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://adrianroselli.com/2025/06/where-to-put-focus-when-opening-a-modal-dialog.html">
    <title>Where to Put Focus When Opening a Modal Dialog — Adrian Roselli</title>
    <dc:date>2025-06-09T15:05:02+00:00</dc:date>
    <link>https://adrianroselli.com/2025/06/where-to-put-focus-when-opening-a-modal-dialog.html</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[TL;DR: blanket statements about where to put focus when opening a modal dialog are wrong, including this one. This post is meant to help you, an intelligent and thoughtful and empathetic reader, figure out where you should set focus. The scenarios are non-exhaustive. ]]></description>
<dc:subject>modal dialog focus html ux accessibility adrian roselli francois</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:a57d95042752/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:modal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:dialog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:focus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:adrian"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:roselli"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:francois"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.fromdev.com/2023/06/improving-accessibility-with-javascriptvoid0-for-javascript-links.html">
    <title>Improving Accessibility with javascript:void(0) for JavaScript Links - FROMDEV</title>
    <dc:date>2025-06-06T16:41:36+00:00</dc:date>
    <link>https://www.fromdev.com/2023/06/improving-accessibility-with-javascriptvoid0-for-javascript-links.html</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Both # and javascript:void(0) can be used as the href value for JavaScript links, but it’s generally better to use javascript:void(0) because it is more semantically correct and is considered more accessible for users with disabilities.]]></description>
<dc:subject>javascript link accessibility void</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:ba6be957d8fc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:link"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:void"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=Uaqo4FOI_DY">
    <title>Screen readers and cookie consents - Léonie Watson - YouTube</title>
    <dc:date>2025-06-05T08:45:10+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=Uaqo4FOI_DY</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[On 12th May 2020 at Screen readers and cookie consents as part of LWP May: Regulation and compliance
When screen reader users are browsing your website, are they hearing your cookie consent banner or popup? What is this experience typically like, does it comply with GDPR and how can we optimise our privacy settings and compliance popups for accessibility? In some cases, users glide past consent prompts without even being aware of them, much less needing to explicitly accept anything. At the other extreme, the prompt can be impossible to accept, resulting in an inability to use the site at all.]]></description>
<dc:subject>a11y video accessibility cookie consent banner leoniewatson</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:08e2c43eebba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:cookie"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:consent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:banner"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:leoniewatson"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://londonwebstandards.org/talks/shift-left-on-accessibility/">
    <title>Shift left on accessibility - Geri Read | London Web Standards</title>
    <dc:date>2025-06-04T13:15:49+00:00</dc:date>
    <link>https://londonwebstandards.org/talks/shift-left-on-accessibility/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Accessibility is often treated as a final checkbox at the end of a sprint, if there’s time. But by then, it’s usually too late. This talk shares practical tips for integrating accessibility into each stage of an agile process for design, engineering, and product. Shift left to make accessibility part of your workflow, avoid last-minute surprises and build more inclusive products.]]></description>
<dc:subject>accessibility build design workflow talk GeriRead JustEat</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:fcc249e24139/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:build"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:talk"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:GeriRead"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:JustEat"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://karlgroves.com/a-deep-dive-into-the-websites-and-software-applications-accessibility-act-of-2025/">
    <title>A Deep Dive into the Websites and Software Applications Accessibility Act of 2025 - Karl Groves</title>
    <dc:date>2025-06-03T11:05:36+00:00</dc:date>
    <link>https://karlgroves.com/a-deep-dive-into-the-websites-and-software-applications-accessibility-act-of-2025/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[In May 2025, a landmark piece of legislation was introduced in the U.S. House of Representatives: H.R. 3417. Listed as “To establish uniform accessibility standards for websites and applications of employers, employment agencies, labor organizations, joint labor-management committees, public entities, public accommodations, testing entities, and commercial providers, and for other purposes.”, this is basically also to be known as “Websites and Software Applications Accessibility Act of 2025”. I’ve been given an advanced look at the eventual long-form content of this bill. Let’s take a detailed look into what the bill proposes, why it matters, and what potential challenges and opportunities it presents.]]></description>
<dc:subject>accessibility legal law legislation USA US website ADA karlgroves</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:247bd9b180b9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:legislation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:USA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:US"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:website"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ADA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:karlgroves"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mayank.co/notes/popover-vs-dialog/">
    <title>Dialog is for modals, popover is for everything else</title>
    <dc:date>2025-06-03T11:02:37+00:00</dc:date>
    <link>https://mayank.co/notes/popover-vs-dialog/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[<dialog> and popover are currently the only two ways to access the browser’s top layer. So what’s the difference between them and which one should you use when?]]></description>
<dc:subject>accessibility dialog modal popover tooltip</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:721ed42a6f5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:dialog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:modal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:popover"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:tooltip"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://karlgroves.com/the-european-accessibility-act-and-b2b-software-what-internal-platforms-must-comply-with/">
    <title>The European Accessibility Act and B2B Software: What Internal Platforms Must Comply With - Karl Groves</title>
    <dc:date>2025-06-03T11:00:49+00:00</dc:date>
    <link>https://karlgroves.com/the-european-accessibility-act-and-b2b-software-what-internal-platforms-must-comply-with/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[The assumption that the European Accessibility Act applies only to public-facing systems is inaccurate and insufficient. National laws in France, Italy, Spain, and other EU countries clearly demonstrate that internal B2B systems—particularly those used by employees or public clients—are within scope for accessibility obligations. Vendors and enterprise buyers alike must adopt a proactive, standards-driven approach to accessibility, not only to comply with current laws but to meet the growing demand for inclusive and equitable digital tools.]]></description>
<dc:subject>accessibility legal karlgroves b2b internal EAA</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:c723fac93050/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:karlgroves"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:b2b"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:internal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:EAA"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.nira11y.com/post/the-4-motivations-for-accessibility-the-big-why">
    <title>The 4 Motivations for Accessibility - The Big WHY?</title>
    <dc:date>2025-05-30T09:47:45+00:00</dc:date>
    <link>https://www.nira11y.com/post/the-4-motivations-for-accessibility-the-big-why</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[1. The Business Case - Market Size Matters
2. The Curb Cut Effect - Better Products for Everyone
3. The Legal Imperative - Avoiding Costly Consequences
4. Inclusion - A Matter of Human Dignity]]></description>
<dc:subject>accessibility why reasons motivations justification</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:780b29b8f83a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:why"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:reasons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:motivations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:justification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.nira11y.com/post/the-challenge-of-measuring-accessibility-impact">
    <title>The Challenge of Measuring Accessibility Impact</title>
    <dc:date>2025-05-30T09:46:05+00:00</dc:date>
    <link>https://www.nira11y.com/post/the-challenge-of-measuring-accessibility-impact</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[As accessibility professionals, we constantly face a fundamental question from business stakeholders: "What's the ROI of our accessibility investments?" It's a fair question. Companies typically evaluate investments by measuring clear returns - put X money in, get Y return out. This process requires measuring the impact of every product or feature against conversion rates, engagement metrics, revenue improvements, or other key performance indicators.]]></description>
<dc:subject>accessibility ROI value measurement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:0eee131fc4d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ROI"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:value"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:measurement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.parliament.uk/about/living-heritage/building/cultural-collections/historic-furniture/the-collection/chairs-chairs-chairs/">
    <title>Chairs, Chairs, Chairs - UK Parliament</title>
    <dc:date>2025-05-28T08:46:58+00:00</dc:date>
    <link>https://www.parliament.uk/about/living-heritage/building/cultural-collections/historic-furniture/the-collection/chairs-chairs-chairs/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[There are almost 6,000 historic chairs in the Palace of Westminster ranging from quite plain items to ornate, gilded thrones. All but one of these chairs are in use, some of them every day. Many of the chairs were designed by A.W.N Pugin in the 1840s in the gothic revival style. Sir Giles Gilbert Scott also designed chairs for the House of Commons in the late 1940s to replace the furniture which was destroyed in the Second World War bombings.]]></description>
<dc:subject>parliament design IA accessibility breadcrumbs cards menu megamenu focus state</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:ed1db5c19be5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:parliament"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:IA"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:breadcrumbs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:cards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:menu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:megamenu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:focus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:state"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://a11y-audits.com/">
    <title>Love &amp; Minter</title>
    <dc:date>2025-05-27T12:47:35+00:00</dc:date>
    <link>https://a11y-audits.com/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[This is a TEST SITE to demonstrate common WCAG accessibility failures that a retail website might have.]]></description>
<dc:subject>wcag demo a11y accessibility teaching bad mistakes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:3f5d6534b184/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:wcag"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:demo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:teaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:bad"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:mistakes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/WAI/demos/bad/">
    <title>Before and After Demonstration: Overview</title>
    <dc:date>2025-05-27T12:47:14+00:00</dc:date>
    <link>https://www.w3.org/WAI/demos/bad/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[The Before and After Demonstration is a multi-page resource that shows an inaccessible website and a retrofitted version of this same website. Each web page includes inline annotations that can be activated to highlight some of the key accessibility barriers or repairs. Each web page is also accompanied by an evaluation report to inform the developers on the level of conformance to the Web Content Accessibility Guidelines (WCAG).]]></description>
<dc:subject>wcag demo a11y accessibility teaching w3c bad mistakes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:d8f3afe18412/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:wcag"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:demo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:a11y"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:teaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:bad"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:mistakes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://emailmarkup.org/en/reports/accessibility/2025/">
    <title>Accessibility Report 2025 | Email Markup Consortium</title>
    <dc:date>2025-05-27T08:16:17+00:00</dc:date>
    <link>https://emailmarkup.org/en/reports/accessibility/2025/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[This year’s report expands beyond just the code sent in HTML messages by senders. This time, we also evaluate the state of accessibility inside email clients, based on our Email Client Feature Support Rankings. Shockingly, only one email client supports all HTML and CSS accessibility features.]]></description>
<dc:subject>email html accessibility markup</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:21eadca620ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:markup"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://equalizedigital.com/accessibility-checker/improper-use-of-link/">
    <title>How to Fix Improper Use of Link Accessibility Errors in WordPress</title>
    <dc:date>2025-05-23T16:11:55+00:00</dc:date>
    <link>https://equalizedigital.com/accessibility-checker/improper-use-of-link/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Relevant WCAG 2.1 Success Criteria
1.3.1 Info and Relationships – Level A

This guideline requires that information and the structure of elements can be programmatically determined, which includes the use of proper semantic HTML.
3.2.4 – Consistent Identification – Level AA

This guideline requires that components of a web page that have the same functionality be identified consistently.
4.1.2 – Name, Role, Value – Level A

This guideline requires all user interface components, including buttons, must have a name and role that can be programmatically determined through the code.]]></description>
<dc:subject>button link accessibility WCAG</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:577e50c4d137/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:button"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:link"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:WCAG"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://overlays.dnikub.dev/#conclusion">
    <title>The Impact of Web Accessibility Overlays | Master's Thesis by Daniela Kubesch</title>
    <dc:date>2025-05-21T14:39:06+00:00</dc:date>
    <link>https://overlays.dnikub.dev/#conclusion</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[ In conclusion, in their current state, accessibility overlays do not benefit every individual with a permanent visual impairment. A website's usability and a user's UX are impacted by them. While accessibility overlays are currently not increasing usability and UX to an acceptable level, both usability and UX are slightly better in the case of individuals who are unaware of the accessibility overlays' existence on a website. This contradicts the idea of accessibility overlays that aim at improving usability, accessibility, and UX for individuals with impairments (Egger, Zimmermann, and Strobbe 2022; AudioEye 2022b; Groves 2021). Additionally, the results of this thesis show that users generally experience a worse UX and reduced usability when they realise a website has an accessibility overlay. This negative impact is further compounded when users interact with or activate the overlay. This decrease can be attributed to issues with activating and interacting with the accessibility overlay and its user interface due to several reasons such as inconsistent structure, misleading wording (Sharif, McCall, and Bolante 2022; Thoo et al. 2023; Mack et al. 2021; Brulé et al. 2020) and cognitive load (Theofanos and Redish 2003), navigation issues on the website while using the overlay, previously negative experiences with overlays and the feeling that "nothing had changed" (Kohler 2023), which led participants to deactivate the accessibility overlay. ]]></description>
<dc:subject>accessibility overlays thesis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:88bf3fcb2af1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:overlays"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:thesis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/feed/update/activity:7329407855357272065/?commentUrn=urn%3Ali%3Acomment%3A%28urn%3Ali%3Aactivity%3A7329407855357272065%2C7329516523000127488%29&amp;dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287329407855357272065%2C7329516523000127488%29%2C7329407855357272065%29&amp;origin=COMMENTS_BY_YOUR_NETWORK&amp;midToken=AQGfCjslg0iVRw&amp;midSig=3lQRgBFMh1trM1&amp;trk=eml-email_notification_digest_01-hero_notification_cta-0-COMMENTS_BY_YOUR_NETWORK&amp;trkEmail=eml-email_notification_digest_01-hero_notification_cta-0-COMMENTS_BY_YOUR_NETWORK-null-ndsj~mavfltko~dr-null-null&amp;eid=ndsj-mavfltko-dr&amp;otpToken=MTMwNTE3ZTAxYjI4Y2FjZWI1MjkwMWVkNDAxNmU3YjU4ZWNhZDA0ODlmYTQ4YTZjNzFjMjA5Njg0NjVhNWVmM2ZjYWZiMzliMTNjMmU1ZjA2NjU3OWNkZmFhYzQyN2ZiODg4YTg3Y2FmNDhhOGM5NWFjLDEsMQ%3D%3D">
    <title>Do we really need to describe ourselves in meetings with blind participants? | LinkedIn</title>
    <dc:date>2025-05-20T08:42:48+00:00</dc:date>
    <link>https://www.linkedin.com/feed/update/activity:7329407855357272065/?commentUrn=urn%3Ali%3Acomment%3A%28urn%3Ali%3Aactivity%3A7329407855357272065%2C7329516523000127488%29&amp;dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287329407855357272065%2C7329516523000127488%29%2C7329407855357272065%29&amp;origin=COMMENTS_BY_YOUR_NETWORK&amp;midToken=AQGfCjslg0iVRw&amp;midSig=3lQRgBFMh1trM1&amp;trk=eml-email_notification_digest_01-hero_notification_cta-0-COMMENTS_BY_YOUR_NETWORK&amp;trkEmail=eml-email_notification_digest_01-hero_notification_cta-0-COMMENTS_BY_YOUR_NETWORK-null-ndsj~mavfltko~dr-null-null&amp;eid=ndsj-mavfltko-dr&amp;otpToken=MTMwNTE3ZTAxYjI4Y2FjZWI1MjkwMWVkNDAxNmU3YjU4ZWNhZDA0ODlmYTQ4YTZjNzFjMjA5Njg0NjVhNWVmM2ZjYWZiMzliMTNjMmU1ZjA2NjU3OWNkZmFhYzQyN2ZiODg4YTg3Y2FmNDhhOGM5NWFjLDEsMQ%3D%3D</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Barry Hill: Weekend thought: Do we really need to describe ourselves in meetings with blind participants?]]></description>
<dc:subject>barry Sky accessibility blind descriptions speakers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:5afd853770d8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:barry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:Sky"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:blind"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:descriptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:speakers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.pope.tech/2025/04/30/remediate-a-pdf-for-accessibility-using-adobes-accessibility-checker/">
    <title>Remediate a PDF for accessibility using Adobe’s Accessibility Checker - Pope Tech Blog</title>
    <dc:date>2025-05-20T08:15:05+00:00</dc:date>
    <link>https://blog.pope.tech/2025/04/30/remediate-a-pdf-for-accessibility-using-adobes-accessibility-checker/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Adobe Acrobat Pro’s Accessibility Checker is a great way to review and fix PDF accessibility issues.
In this video, we go over:
    The overall remediation steps
    How to use the accessibility checker]]></description>
<dc:subject>PDF accessibility checker</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:3ee1fe21bd08/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:PDF"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:checker"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.blog/engineering/user-experience/considerations-for-making-a-tree-view-component-accessible/">
    <title>Considerations for making a tree view component accessible - The GitHub Blog</title>
    <dc:date>2025-05-09T14:10:16+00:00</dc:date>
    <link>https://github.blog/engineering/user-experience/considerations-for-making-a-tree-view-component-accessible/</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[Tree views are notoriously difficult to implement in an accessible way. This post is a deep dive into some of the major considerations that went into how we made GitHub’s tree view component accessible. We hope that it can be used as a reference and help others.]]></description>
<dc:subject>components aria tree ui accessibility GitHub</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:13c9e016949d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:components"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:aria"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:tree"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:GitHub"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ux.stackexchange.com/questions/145088/hiding-duplicate-links-with-aria-hidden/145099#145099">
    <title>accessibility - Hiding duplicate links with aria-hidden - User Experience Stack Exchange</title>
    <dc:date>2025-05-09T13:49:42+00:00</dc:date>
    <link>https://ux.stackexchange.com/questions/145088/hiding-duplicate-links-with-aria-hidden/145099#145099</link>
    <dc:creator>fjordaan</dc:creator><description><![CDATA[aria-hidden will indeed hide the element from screen readers and will prevent the user from navigating to it with the screen reader (such as using the down arrow) but does not prevent the user from navigating to it with the TAB key (since links are inherently keyboard focusable). This means a screen reader user could TAB to the hidden link but nothing will be announced because the element was removed from the accessibility tree.

That's bad.

To prevent TAB, you'd need tabindex="-1". However, that will prevent sighted keyboard users from navigating to it. That might be a good thing as you'll have fewer tab stops, but if something looks like a link, then I'd expect to be able to TAB to it.]]></description>
<dc:subject>aria-hidden read more learn link list accessibility tabindex</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:fjordaan/b:e19abcbede51/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:aria-hidden"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:read"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:more"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:learn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:link"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:list"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:fjordaan/t:tabindex"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>