January 2019 Newsletter
This new resource can help you through the process of evaluating Office documents and presentations for accessibility.
Registration is open for a WebAIM web accessibility training to be held March 5-6 in Logan, Utah.
A landmark ruling that clarifies that the ADA covers websites and mobile applications.
Some of the quickest accessibility wins can be simple fixes. But if you don't know what to look for, they can be hard to spot.
Scott O'Hara provides an in-depth examination of accessibility of the figure and figcaption elements.
Several examples are provided of improper ARIA usage, with the corrections shown.
A sighted user puts himself in the shoes of a non-sighted user. Chris Ashton experiences first-hand difficulties that visually impaired users face and describes what we can do as web developers to help.
Old technology finds a surprising new application.
Quick Tip: Text Spacing
Some users may adjust text as viewed in their browser to support their optimal reading. They may increase the text size, change font faces, or adjust paragraph, line, letter, and/or word spacing. WCAG 2.1 requires that your page has no loss of content or functionality if the end user modifies certain text spacing properties. The guidelines prescribe the exact values, but the principle is sound - if users adjust text properties, ensure that your page still works. Using pixel heights for elements that contain text is the most common cause of failure - when the text is modified, it may no longer fit within the defined element's dimensions.