Accessible Javascript with and without WAI ARIA
15 likes5,816 views
The document discusses making JavaScript accessible. It states that JavaScript content should be at least as accessible without JavaScript, nothing should be withheld from non-JavaScript users, and assistive technologies should be able to use the page. It emphasizes that websites must work without JavaScript first, and that CSS should not be used for interaction or hiding content. The document then introduces WAI-ARIA as a way to add semantics and meaning to elements for screen readers through roles, properties, and live regions. It encourages using WAI-ARIA but also not relying on it exclusively.
Editor's Notes
- #31: over 90 different roles to map existing OS concepts onto your Markup
- #33: article Content that makes sense in its own right, such as a complete blog post, a comment on a blog, a post in a forum, and so on. banner Site-orientated content, such as the title of the page and the logo. complementary Supporting content for the main content, but meaningful in its own right when separated from the main content. For example, the weather listed on a portal. contentinfo Child content, such as footnotes, copyrights, links to privacy statement, links to preferences, and so on. main Content that is directly related to or expands on the central content of the document. navigation Content that contains the links to navigate this document and/or related documents. search This section contains a search form to search the site.
- #35: aria-valuemin Stores the lowest value a range may have. aria-valuemax Stores the highest value a range may have. aria-valuenow Stores the current value in a range. aria-valuetext Stores readable text to help the user understand the context. For example, \"30 dollars\" . aria-labelledby Stores the id attribute of a text label containing an appropriate prompt for this widget.