Architecting for Accessibility
summary
Claims a practical roadmap: adopt WCAG 2.1 Level AA, baseline the app, publish an accessibility statement, then fix high-impact components (navigation, headers, repeated widgets) before critical flows. Uses tooling like Lighthouse and Accessibility Insights plus linters and CI gating, manual keyboard and screen-reader checks, and user testing. Notes assistive tech share (approx JAWS 21% / NVDA 20%), Chrome/Safari ~82% market, and recommends component-first fixes and CI gating to make and keep an app accessible.
AI-written summary · about
chapters (5)
related talks
41mArchitecting for Accessibility
33mAccessibility needs to be the future of better technology
01h 05mAccessibility Testing 101
38mHow to set up an accessibility program in an imperfect world
26mHow (Not) to Fail at Accessibility
29mAccessibility first is the new Mobile first
28mBuilding in accessibility for broader value to all
12mAccessibility-First Development: Making Applications Inclusive from Day One