Upstream Accessibility: A Contributor's Guide
summary
Shows why >50% of public websites are inaccessible with concrete examples: Yarra Trams has low‑floor trams on only about half its routes and most stops are 50–60% accessible while route 96 approaches 100%; Robles v. Domino’s (filed 2019, courts side with Robles) frames legal risk. Compares raw HTML/CSS gov.uk (works) to frameworks like React where frameworks increase accessibility errors, cites Tailwind UI as a better component option, and prescribes use screen readers and manual testing plus automated checkers and clear upstream PRs.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:14Upstream Accessibility: A Contributor's Guide
- 1:22Upstream Accessibility A Contributor's Guide
- 15:55Robles v Domino's Pizza LLC
- 19:25Raw HTML and CSS
- 21:00Why we use frameworks
- 22:58What makes a framework accessible
- 26:58Just use dark mode, it'll be fine
- 28:46The ethos of accessible development
- 32:51Continuous Accessibility
- 36:40Accessibility and FOSS maintainers
- 37:42Implementing fixes
- 39:08Accessibility testing
- 40:27What maintainers need to know
- 43:18A world of perfect spheres
related talks
14mAccessible Accessibility
01h 01mFull Stack Accessibility, and the Business Case for being Inclusive
01h 07mA web for anyone, anywhere, anytime
53mThe Human Side of Accessibility
53mAccessing Accessible Accessibility
37mAccessibility Matters: Creating a Better Web
25mBeyond Compliance: Testing for a more Accessible Web
26mAccessibility Is a Marathon, not a Sprint