Real accessibility: an imperfect, honest journey
summary
A five‑year accessibility guild grows into a concrete practice: an external + internal audit after the EU Accessibility Act, published Ubuntu and web guides, and onboarding docs tied into the Vanilla design system so buttons, focus rings and labels ship correctly. Engineers learn Orca and run manual assistive‑tech checks because Orca screen reader testing finds issues automated tools miss. Native app toolkit Jaru needs work; upstream fixes land in GNOME. Guides live at ubu.link/bererlin and community testing continues.
AI-written summary · about
chapters (13)
- 0:00Introduction and audience check
- 1:13Why accessibility matters today
- 5:33Starting the accessibility guild
- 7:17Conducting the accessibility audit
- 9:44Creating accessibility guides
- 13:17Building a diverse team
- 14:21Fixing toolkits and design systems
- 16:49Integrating accessibility into processes
- 18:56Engaging with the community
- 19:37Imperfect journey and next steps
- 21:48Q&A: Accessibility for power users
- 24:20Q&A: AI and accessibility impact
- 27:49Q&A: Overcoming resource overwhelm
related talks
50mShift Left on Accessibility: Beyond the Audit
23mAccessibility matters. Let’s do something about it
24mAccessibility needs better marketing
21mBuilding an Accessibility Culture
22mFrom a Workshop to a Wake-Up Call: My Journey into Accessibility
47mLessons learnt from building accessible complex web apps
01h 05mAccessibility Testing 101
01h 02mAccessibility - how to get the job done in a highly collaborative manner