Coding for accessibility can be challenging: Which assistive technologies should I consider? What is their support for specific coding patterns? Developers often add supplementary code to their projects to control the behaviour of assistive technologies like screen readers.
Eric Eggert shows how graceful degradation and progressive enhancement allow people to use their tools in a way they are comfortable with, while at the same time keeping your project’s code simple and easier to maintain.
This article examines the rationale for organizations to address accessibility. It includes tangible and intangible benefits and the risks of not addressing accessibility adequately. It explores how accessibility can:
In February 2019, WebAIM conducted an accessibility evaluation of the home pages for the top 1,000,000 web sites using the WAVE stand-alone API (with additional tools to collect site technology parameters). While this research focuses only on automatically detectable issues, the results paint a rather dismal picture of the current state of web accessibility for individuals with disabilities.
In September of 2017 Gerard K. Cohen of Unfettered Thoughts posted an article on the how VoiceOver and Safari (Webkit) (macOS and iOS) remove list element semantics when list-style: none is used. And it’s not just the use of list-style: none, but any CSS that would remove the bullet or number indicators of a list’s items will also remove the semantics.
Introduced as part of HTML5, the figure and figcaption elements are meant to create a meaningful markup structure that:
To get more specific, let’s look at these elements individually.
The latest and greatest Dragon Naturally Speaking (version 13) finally catches up, at least partially, with a critical web standard: WAI-ARIA.
Accessibility is more than just making things work in a screen reader. This talk discusses Windows High Contrast Mode’s capabilities and limitations, and how to best design and develop for it.