¿What can happen if you create screen readers only content?
It can actually create a worse user experience for some users. Besides which, it can create a maintenance headache when it comes to things like internationalization.
¿Which are the three common patterns that can cause the screen reader to miss links in the page?
- One is using a span, with some link styling, or an anchor tag without an href attribute.
- Something which is implemented using a link but is really more like a button; for this case, we’ll just replace that anchor tag with a button tag and style it appropriately.
- Where we have an image used as link content; for an assistive technology this makes the link unusable.
¿What should any link text do?
In general, link text should give any user enough information to decide whether they want to click it.
¿What should I use an anchor with the href attribute for?
For anything which behaves like a link, including within a single page application.
No exceptions.
¿Why to always use anchor with href?
Not only will this make the link show up in the links list, but it automatically works with the keyboard.
¿What does using semantic elements do?
Using semantic elements, provides a more terse way to express the same information while also potentially providing more information for screening ready users.
WHAT ARE ARIA LANDMARKS?
ARIA landmarks are attributes you add to elements to create semantically defined sections of a page that allow users of assistive technologies to navigate the page more easily. Think of ARIA landmarks as building a set of “skip to” links like “skip to main content”.
