Creating Accessibility Culture
summary
European Accessibility Act requires compliance as of June 2025 and the recommended target is WCAG 2.2 AA baseline. Practical fixes shown: use Chrome DevTools Accessibility → Show Accessibility to inspect the accessibility tree, prefer aria-label for SVG icons, hide decorative SVGs with aria-hidden or use empty alt="" for decorative images, and avoid redundant alt plus aria-label. Workflow changes include upskilling leads, adding accessibility to acceptance criteria, and offering training; examples mention Onclick Co-op projects, compose.co, and a bookings app called Butter Software.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:13Speaker background and co-op model
- 6:09What is web accessibility
- 8:13Creating accessibility culture
- 10:44Accessibility in code examples
- 17:27Fixing accessibility issues with ARIA
- 21:45Alt text and decorative images
- 23:10Practical accessibility mindset
- 24:11Legal standards and compliance
- 26:39Screen reader testing techniques
- 28:25Resources and closing
related talks
38mAccessibility 101-102: What every tester should know about digital accessibility
06mWeb Accessibility by 2025
15mAccess-what? why and how. A11Y for all
41mArchitecting for Accessibility
32mTHE GREAT OPPORTUNITY - Part 1: Back to the Future
01h 03mAccessibility: Making your websites more inclusive
42mArchitecting for Accessibility
43mWhat is accessibility, and why I should care?