How to set up an accessibility program in an imperfect world
summary
Argues that accessibility can be adopted midstream: set WCAG 2.1 AA as the standard, shrink it to a 14‑item checklist tied to planning/design/dev/test, run one‑off audits of 1.5 years of existing work, and feed issues into the backlog to fix one issue per sprint while preventing new ones via acceptance criteria. Uses Lighthouse, linters and pipeline checks plus short hands‑on training for keyboard and screen‑reader workflows. Outcome: stakeholders accept goals (e.g. 60/80/100% targets) and teams make steady measurable progress.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:10The Reality Check
- 6:29Permanent Disability
- 7:13Creational Disabilities
- 8:35Reality Check
- 9:55Web Content Accessibility Guidelines
- 26:01Hints
- 28:09When Will We Be Done with Accessibility
- 30:06Are There Go to Tools for Making Accessibility Goals Uh More Easy To Adjust
- 32:54What Really Keeps My Spirits High
- 34:26What Are Other Strategies That Work for You and Your Team Um To Spend at Invest More Time Uh in Accessibility When the Stakeholders Say It's Not the Priority
related talks
29mHow to bring accessibility into your teams
42mArchitecting for Accessibility
41mArchitecting for Accessibility
50mShift Left on Accessibility: Beyond the Audit
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
01h 02mAccessibility - how to get the job done in a highly collaborative manner
26mHow (Not) to Fail at Accessibility
49mDigital Accessibility and Knowing When to Flex