May 2017 Newsletter
After looking at hundreds of real-world ARIA uses and abuses, it is clear that some ARIA attributes are typically used in ways that cause more problems than they solve, while other attributes should be used more often to solve specific problems.
Registration is open for the WebAIM training to be held August 29-30 in Logan, Utah.
These days auto-suggest is everywhere, from social media sites like Twitter and Facebook, to shopping sites like eBay and Amazon, and even in occupation validation for credit card applications.
Landmark-based navigation is a great way to signpost to screen reader users areas of content in a page such as main content, the header, navigation, search and so on. The Landmarks extension allows everyone, including keyboard-only users, to discover and navigate landmarks.
Names and descriptions can help your users figure out which elements they are interacting with, and what they are for. In this post Hidde de Vries explains implicit and explicit labelling methods and discusses how to future-proof your labels.
Another excellent installment in the Accessibility Fundamentals video series.
Want to know how many people with disabilities use your site? In this post, we'll explore why that may not be as easy as you might think.
Why website body text should be bigger, and ways to optimize it.
Quick Tip: Using aria-expanded
The aria-expanded attribute can increase accessibility of basic accordions which expand and collapse page content. This attribute is added to the link or button that controls the expanding content. The value (true or false) must be dynamically set to indicate the current state. A screen reader will speak "Expanded" or "Collapsed" when the control is accessed, thus indicating the current state and that activating the control will toggle the state.