Accessibility Matters: Creating a Better Web
summary
Web accessibility follows WCAG 2.0 (POUR) and affects roughly 10–20% of users; EU directives from 2016 push public sites to comply. A simple manual test — cover eyes, put on headphones, enable a screen reader — exposes real failures: videos that can be played but not paused, modals that trap focus. Practical fixes shown include ARIA alerts, meaningful alt text, keyboard navigation checks, and using tools like JAWS screen reader and browser extensions. Accessibility also improves SEO, code quality, and reduces future dev work.
AI-written summary · about
chapters (13)
- 0:00Introduction to accessibility
- 3:24What is web accessibility
- 5:10Who needs accessibility
- 10:32Stress cases over edge cases
- 11:36Common accessibility issues
- 15:32Elevator analogy for design
- 18:01Improving accessibility
- 21:58Universal design principles
- 23:21Bare minimum accessibility
- 24:25Importance of wording
- 26:11Testing with keyboard navigation
- 27:14Benefits beyond users
- 28:18Conclusion and resources
related talks
37mAccessibility Matters: Creating a Better Web
43mWhat is accessibility, and why I should care?
22mWeb Accessibility?
54mAccessibility by everyone (and for everyone)
22mAccessibility in Practice
01h 03mAccessibility: Making your websites more inclusive
38mAccessibility 101-102: What every tester should know about digital accessibility
41mAccessibility is a Requirement