Accessibility and Performance
summary
Claims that accessibility boosts perceived responsiveness and concrete techniques to prove it get covered: measure seconds until a screen reader reads content instead of only load time, count keystroke level performance (tabs enter escape) to see how many actions a keyboard user needs, inspect skeleton loaders and ARIA states like aria-roledescription and aria-busy in the Khan Academy chat table example, use Axe Core and the Axe browser extension plus Cypress for automated keyboard contracts, track Lighthouse accessibility score and EN301549 compliance for EU obligations, avoid overlay widgets as a permanent fix.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:26Talk introduction
- 3:38Defining accessibility
- 5:00Accessibility and performance
- 9:59Skeleton loaders and accessibility
- 16:22Mobile web and responsive design
- 20:17Keyboard navigation performance
- 27:37Accessibility metrics and tools
- 34:23Prioritize accessibility
- 39:40Inclusive design tips
- 42:25Resources and call to action
- 43:28Q&A
related talks
26mAccessibility Is a Marathon, not a Sprint
41mAccessibility is a Requirement
34mAccessibility: the land that time to interactive forgot
32mDemystifying Accessibility
33mAccessibility needs to be the future of better technology
37mAccessibility Testing Techniques, Issues and Tricks
08m"Accessibility! Why should I care?"
22mAccessibility in Practice