Lessons learnt from building accessible complex web apps
summary
Two case studies detail concrete outcomes: an Angular e-commerce with JAWS 17 & VoiceOver iPad where accessibility is built in, three rounds of usability testing find and fix navigation and tabs, and a Polymer financial app repaired to WCAG A with NVDA+Firefox under a tight MVP timeline. Key specifics: evaluate framework accessibility up front, embed an accessibility SME, test multiple screen reader/browser combos early, choose a prioritized platform when ARIA behaves inconsistently, and document decisions and vendor bug reports.
AI-written summary · about
chapters (27)
- 0:00Intro
- 2:20About Sarah
- 4:03Lessons learnt
- 7:17Research and planning
- 7:43Accessibility considerations
- 10:51Roles and responsibilities
- 14:14Best practice
- 15:57Dont focus on accessibility
- 17:39Tip 1 A complex web app
- 18:17Tip 2 User experience
- 19:53Tip 3 Intent
- 21:48Tip 3 Support Multiple Screen Readers
- 23:00Tip 1 Native HTML Elements
- 24:46Tip 2 ParentChild Relationships
- 25:36Tip 3 Test Early
- 26:35Tip 4 Code Samples
- 28:33Tip 5 Decision Tree
- 30:27Hacks
- 32:35Get usability testing into your project
- 34:38Selecting the right mix of users
- 36:52Testing with users
- 37:21Listening to users
- 39:24Documenting decisions
- 40:21Raising bugs
- 41:26Tapping into the accessibility community
- 42:01Summary
- 44:07Accessibility Avenger
related talks
23mPractical A11Y for Web Apps
42mArchitecting for Accessibility
37mAccessibility Matters: Creating a Better Web
23mBuilding Accessible Components: Best Practices and Business Buy-In
53mDoing Responsive Right: Accessibility Lessons from the Field
35mAccelerating accessibility in web
43mWalking Down the A11Y Road - Lessons Learnt From...
31mHow to Program with Accessibility in Mind