A11y-Friendly Documentation
summary
Documentation is often left out of accessibility work yet concrete fixes exist and are demonstrated here: WHO says over one billion people need assistive devices and Stack Overflow shows about 1 in 66 developers are blind or hard of sight, so docs matter. Examples include a screen reader demo, keyboard-accessible Shopify docs, focus rings like gov.uk, skip links (Twilio, MDM), and chart alt text implemented with aria-describedby for charts. Tools shown include VoiceOver and NVDA, axe and WAVE, Color Oracle and WebAIM; trailing spaces and improper markup actually break screen reader output.
AI-written summary · about
chapters (20)
- 0:00Start
- 3:09assistive technology
- 6:17there's a business case for ally
- 7:05documentation is for developers
- 10:19structure and hierarchy
- 11:04html - hypertext markup language
- 12:28aria - accessible rich internet applications
- 19:46charts and infographics
- 24:26code snippets
- 25:54use meaningful variable names
- 26:55plain language
- 28:13testing for accessibility
- 31:00free extensions and validators
- 32:23make accessibility a priority
- 32:44create an accessibility policy
- 33:46update your development checklists
- 34:05browse the web from a different perspective
- 34:36host an ally hackathon
- 34:59contribute to open source docs
- 36:26documentation is for everyone
related talks
37mMoving beyond empathy: a11y in documentation
31mBringing the Web Back to the Blind
01h 07mA web for anyone, anywhere, anytime
37mAccessibility Matters: Creating a Better Web
33mAccessibility Done Right
41mAccessibility is a Requirement
41mTales of Accessibility Failures
36mThe Human Side of Accessibility