January 2018 Newsletter
NCDAE (a WebAIM partner) has created four new accessibility cheatsheets. These single-page resources outline accessibility techniques for Word and PowerPoint 2016 for Windows and Mac.
Registration for the April 10-11 WebAIM web accessibility training in Utah is now open.
One question we get asked regularly relates to seemingly odd behavior, where you use a different browser on the same system, or your usual browser on another machine, and the site doesn’t behave as you expect.
Designing an accessible interface is not only working on contrasts and colours for users with visual impairment. An accessible interface is built to be used by all kinds of users, including dyslexic people.
To understand why automating tests for assistive technology is difficult, it helps to know a bit about the process your page goes through when it finally gets announced by a screen reader.
Ryan Jones provides a great analogy to help others more accurately understand what it is like for someone using screen reading software to navigate through a web page.
Andy Bell gives an excellent list of tips on small things that can make a big difference, while hopefully not affecting your development process too much.
Quick Tip: Responsive Design Support Accessibility
Zooming a web page can trigger tablet and phone responsive breakpoints, if they are defined. WCAG 2.1 (which is still in draft form) has a new success criterion for supporting reflow of web content when zoomed. This behavior can provide content that is optimized for low vision users - it will be enlarged on their screen while minimizing horizontal scrolling. Do, however, keep in mind that users may experience a tablet or phone view of your page while on a desktop or laptop computer. This necessitates that these responsive presentations of the page work with a keyboard and support other aspects of accessibility.