Tag: WAI-ARIA
Accessibility for User Experience Designers
In this post, JavaScript Developer Matt Isner details the ins and outs of accessible design for user experience designers. Matt covers everything from the initial design stage to the technical specifics, with several tips and practical "Deque How To" hacks to help you ensure that your website is accessible by design. Remember, solving accessibility problems means improving usability for everyone!
Read ArticleBuilding Accessible Buttons with ARIA: A11y Support Series
Previously Paul J. Adam explained how to build ARIA role="alert" Modal Dialogs in his A11y support series. In his latest post in the series, Paul details how to build another ARIA widget: a simple role="button" UI control. He also explains what screen reader and browser combinations are supported when using other ARIA attributes allowed on role="button."
Read ArticleHow to Build WAI-ARIA Modal Alert Dialogs: A11y Support Series
In the second part of his accessibility support series, Paul Adam explains how to build an accessible widget with ARIA Modal Alert Dialogs. Learn new tricks on building accessible widgets that go above and beyond the recommendations outlined in the WAI-ARIA Authoring Practices.
Read ArticleAccessible HTML Heading Markup
Do headings introduced to meet SC 2.4.10 (AAA) need to be marked up With an h<n> tag too? On this page, HTML heading markup h<n>…
Read ArticleHow Accessibility Impacts Responsive Design
This illustrates why accessibility support in terms of differences in navigation techniques and HTML / ARIA behavior on a mobile device needs to be taken into account during design.
Read ArticleUsing Aria-invalid for Error Indication
Aria-invalid=true Setting aria-invalid to “true” is a quick and easy method for indicating that a field has failed validation. Yet, its usefulness from an accessibility…
Read Article