Slide 11
Slide 11 text
Okay you got me, what then ?
1. Include alternative text for non-text based
content - Images | Audio | Video
A visually impaired person cannot view a picture or
video content. Providing a plain text alternative for
all functional and informative non-text contents
makes it possible for such persons to access the
content.
2. Specify the Language of a Page
Use the lang attribute to specify the language of a page on
the HTML element.
Also if the language of an element differs from the rest of
the page use the lang attribute to specify the language of
that element
3. Use semantic elements
Use the right element tag for paragraphs, headings, lists,
and tables.
Also use semantic elements such as , ,
to structure the layout of your website.
4. Structure elements in a logical reading order
Assistive technologies read web contents in the order they
appear in the source code. So elements should always be
placed in the order it should be read.
CSS can always be used to place elements anywhere, but the
order in which it appears in the source code should be in the
logical reading order.
5. Ensure interactive elements are keyboard accessible
Interactive elements such as buttons, links, and form controls are by
default keyboard accessible.
However other custom built interactive widgets are not accessible
via the keyboard.
To add keyboard accessibility, use the tabindex="0" attribute on the
target element.
6. Avoid using CAPTCHAs for authentication
CAPTCHAs can be problematic to some kinds of users. You can opt for
alternative methods such as automatic detection or interface
interactions to verify that all inputs are generated by a human.
7. Use Linters
Linters are tools/plugins that help report bottlenecks and recommend
fixes in our codes. Some of them identify accessibility bottlenecks and
recommends fixes for developers. Example: eslint-plugin-jsx-a11y