Accessible Accessibility
summary
Surveyed organisations report 90% say accessibility matters while audits show only ~50% have accessible sites and 55% of frontend developers consider accessibility, a clear gap. The practical fixes shown are tool-led: add automated integration tests, use checkers like axe, pa11y and IBM Equal Access, and adopt frameworks that enforce patterns — Svelte issues a terminal warning for missing alt attributes. Hardware and assistive software can work but cost (eye tracker > A$300, some software needs donations) limits uptake.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:30Awareness versus action
- 3:46Why accessibility tools fail
- 5:40Barriers to implementation
- 8:18Tooling for responsibility
- 9:24Svelte’s accessibility warnings
- 10:34Accessibility as enhanceability
- 12:52Key takeaways and closing thoughts
related talks
41mAccessibility is a Requirement
53mAccessing Accessible Accessibility
54mAccessibility by everyone (and for everyone)
56mAccessibility Testing 101
09m"How to bring accessibility into your teams."
29mHow to bring accessibility into your teams
45mTips from the Trenches: Accessibility Testing
44mTesting Web Accessibility