Full Stack Accessibility, and the Business Case for being Inclusive
summary
Recent court precedent Domino's US Supreme Court win forces websites to be accessible even when a physical store exists, and automated scans (WAVE/WebAIM) flag 97.8% of the top million home pages with WCAG 2 failures. Practical fixes shown include semantic labels, aria-labelledby or wrapping inputs with label, NVDA/VoiceOver testing, alt text and captions, skip links and visible focus outlines. Data points: 1 billion people with disabilities worldwide, Forrester/Microsoft estimate €2.3M extra annual revenue per 1M daily visits from fixing accessibility.
AI-written summary · about
chapters (22)
- 0:00Start
- 4:06What Is an Inclusion Engineer
- 6:27Web Accessibility
- 6:53Web Content Accessibility Guidelines
- 9:06Screen Reader
- 13:35The Aria Labeled by Attribute
- 17:32Motor Impairment
- 20:17Designing for Users with Anxiety
- 35:29What Is Full Stack Accessibility
- 37:19The Squint Test
- 40:33Content and Marketing
- 41:33Social Media
- 42:20Javascript Developer
- 44:27Back-End Developer Devops
- 46:15Inclusive Leadership
- 47:46The Business Case for Inclusion
- 48:14Innovation
- 48:49Curb Cuts in the Footpath
- 50:50Inclusion Is Good for Brand Enhancement
- 53:01Sydney Olympics
- 54:32Customer and Employee Satisfaction
- 58:34Example of an Accessibility Action Plan
related talks
53mThe Human Side of Accessibility
37mAccessibility Matters: Creating a Better Web
22mIn the age of AI: if it's not Accessible, it's not Acceptable
21mWhy Accessibility Benefits Us All
51mIts Spelled Accessibility not Disability
33mThe Digital Accessibility Legal Landscape – why it matters for developers
29mAccessibility Matters: Creating a Better Web
54mAccessibility by everyone (and for everyone)