Accessing Accessible Accessibility
summary
Team has four months to guarantee all consumer flows are accessible and focuses on concrete steps: a WebAIM audit flags issues, automated Totally script + JSX linter blocks noncompliant builds, and acceptance tests (Python) check alt text, labels and color contrast. Metrics cited: 25% of traffic is 45+ and an estimated 7.5% of global traffic needs accessibility. Workshops force engineers to complete a purchase with screen readers; work is underway via JIRA tickets and modular accessible components, results improving but not finished.
AI-written summary · about
chapters (39)
- 0:00Intro
- 2:39What is accessibility
- 3:52Who needs accessibility
- 7:38Why do accessibility
- 11:21Standards
- 14:24Testing Accessibility
- 15:26Screen Readers
- 16:05Numbers
- 16:34Assistive Technology
- 17:34Other Accessible Devices
- 18:52Web Validators
- 19:53NoCoffee
- 20:26Other Ideas
- 21:07Accessibility
- 23:22Noncolor indicator
- 23:43Tab index
- 24:29Videos animations
- 25:04Aria
- 26:57Roles
- 27:54Aria States
- 28:09Aria Properties
- 28:34Skip Links
- 29:32Skip Main Navigation
- 31:27Skip Narrator
- 31:57Android
- 32:56iOS
- 35:14Web Content
- 41:14Web Aim
- 41:54Crossfunctional Team
- 42:32Documentation
- 43:08Tools
- 44:39Acceptance Tests
- 45:02Project Management
- 45:23Accessibility Dashboard
- 46:03Dont Work Alone
- 46:36Accessibility Workshop
- 47:22Working with Design
- 49:09Accessibility Slack Channel
- 49:31Questions
related talks
54mAccessibility by everyone (and for everyone)
06mAccessibility
14mAccessible Accessibility
41mAccessibility is a Requirement
50mAccessibility by Everyone (and for Everyone)
26mHow (Not) to Fail at Accessibility
01h 02mAccessibility - how to get the job done in a highly collaborative manner
41mArchitecting for Accessibility