Web Accessibility Strategies for Non-Accessible Projects
summary
Presents a four‑pillar plan: commit and KPI, audit and recruit people with disabilities, embed accessibility in processes, and add observability and tests. Cites WebAIM data on 1 million sites with ~85% failing color contrast and lists six persistent failures: missing html lang, empty buttons and links, no form labels, missing alt text, poor contrast. Recommends concrete fixes like lang attributes, aria-labels, visible labels, and running axe, Pa11y and aXe linter in CI/GitHub Actions plus unit and end‑to‑end checks.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 1:00Identifying accessibility issues
- 3:59Planning and transparency
- 6:16Cultural change and teamwork
- 8:48Technical excellence and learning
- 10:31Common accessibility failures
- 14:20Observability and automation
- 18:10Conclusion and human impact
related talks
50mMaking a Strong Case for Accessibility
26mHow (Not) to Fail at Accessibility
37mMaking A Strong Case For Accessibility
41mAccessibility is a Requirement
01h 03mAccessibility: Making your websites more inclusive
15mRapid Introduction to Web Accessibility
25mBeyond Compliance: Testing for a more Accessible Web
52mDesigning inclusive and accessible experiences