Be a Better Developer:
Build for Accessibility
India Amos | india@indiamos.com | @indiamos
Grace Hopper Academy 1706 Cohort
Adults with hearing trouble | 37.2 million | 15.3% |
Adults with vision trouble | 22.9 million | 9.4% |
Adults with any physical functioning difficulty | 39.6 million | 16.3% |
Adults with dyslexia: 5–20%, depending on whom you ask
1. Learn the standards.
2. Build for differing abilities.
3. Build for differing devices.
The Web Accessibility Initiative (WAI) of the
World Wide Web Consortium (W3C) has issued a set of
Web Content Accessibility Guidelines (WCAG)
https://www.w3.org/WAI/intro/wcag.php
WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities.
Using semantic HTML for structure while controlling presentation using CSS, will get you a long way toward accessibility, especially on forms.
Know your elements.
Image? Describe it.
Audio? Transcribe it.
Video? Caption it.
DOM change? Notify assistive tech using ARIA, and place it downstream.
Personas for Accessible UX, by Whitney Quesenbery:
http://rosenfeldmedia.com/a-web-for-everyone/personas-for-accessible-ux/
Can you get to important elements quickly?
Can you get out of everything?