Architecting for Accessibility

on YouTube ↗41m

" summary

Claims concrete steps: baseline against WCAG 2.1 AA, pick target browsers (Chrome+Safari ~82% market) and assistive tech to test with, and phase work into 0–4 so fixes land and stay fixed. Tooling mixes linters, validators and Lighthouse and Accessibility Insights plus manual and screen‑reader checks; surveys note JAWS 21% NVDA 20% for screen reader usage. Expect to fix global components first, automate regressions, and keep an evolving accessibility statement.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 9:58Diversity of Abilities
3. 12:56Determining Scope
4. 14:58Baselining the Application
5. 16:38Browser Support
6. 20:18Breakpoints
7. 30:11Team Roles

" related talks

• 42mArchitecting for AccessibilityMartine Dowden · JavaScript and Friends Conference 2020
• 56mAccessibility Testing 101Erissa Duvall · Conf42 Kube Native 2023
• 01h 05mAccessibility Testing 101Erissa Duvall · NDC London 2024
• 26mHow (Not) to Fail at AccessibilityTrish Ang · JSConf Hawai 2019
• 45mTips from the Trenches: Accessibility TestingManoj Kumar · Agile India 2021
• 33mWeb Accessibility: Why, How and What?Arathy Kumar · DevConf.CZ 2023
• 41mAccessibility is a RequirementRyan Boone · RailsConf 2021
• 50mShift Left on Accessibility: Beyond the AuditRamona Domen · Jfokus 2026