Skip to main content
User Experience

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    Aren't you overthinking this? If you already use sementic elements the right way and have the document and content build up logically, everything should be accessible by keyboard and read by screen readers just fine. Why should only screen reader users benefit from the extra explanations/descriptions? Here's is a challenge: Try to make the document so that you need as few aria and tabindex attributes as possible, that will give you an idea how much complexity it takes away when you think about accessibility right from the start. Commented Jun 14, 2023 at 14:15
  • I'm not really using any semantic elements for the descriptive text at the top of the page. They're not accessible via keyboard because they're not really focusable. Voiceover just skips right past them and goes directly to the filters on the sidebar. Commented Jun 14, 2023 at 14:20