Stop to diss ability: the web is designed for all
summary
Proposes treating people as active users who use remaining senses or body parts (see example duck Jimmy) and building an active product with reusable support cards that map abilities (see/hear/touch) to concrete fixes: semantic HTML, coherent IA, speaking hyperlinks, alt text, audio descriptions, plain language. Gives deployment plan for product teams (attach responsibility to roles, add supports to journey maps), cites the European Accessibility Act taking effect 28 June 2025 and its reliance on WCAG standards.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:08Disability meaning
- 2:56Disability history
- 7:28Accessibility challenges
- 8:53Disability definition
- 9:14Jimmy the duck example
- 12:33Disability and digital access
- 13:15Active users concept
- 15:21Disability range in design
- 16:48Content for senses
- 18:34Solutions for abilities
- 19:18Structured HTML importance
- 20:19Accessible navigation
- 21:43Content accessibility aids
- 22:24Support cards guide
- 23:04Team accessibility roles
- 24:30Accessibility in user journeys
- 25:32Overcoming team resistance
- 26:13Situational disabilities
- 27:19SEO and revenue benefits
- 27:59Legal requirements
- 30:28Conclusion
- 32:59Q&A: Legal standards
- 33:43Q&A: Accessibility benefits
- 35:10Q&A: Accessible websites
- 36:36Q&A: AI-driven accessibility
related talks
28mBuilding in accessibility for broader value to all
53mUsability useful for everyone
01h 07mA web for anyone, anywhere, anytime
37mMoving beyond empathy: a11y in documentation
31mHow to Program with Accessibility in Mind
37mAccessibility Matters: Creating a Better Web
49mThese 5 Changes Will Advance Inclusive Design
26mMake the internet a better place - with coding for accessibility