Peter Krautzberger, krautzource
Slides at https://krautzource.github.io/talks-2025-weba11y-intro/
To move through the Slides, scroll left/right.
Source: webaim
Inspiration:
Technically-oriented: Selfish Accessibility (Adrian Roselli) (note: audio gets better ~3:30min)
Content-oriented: Accessibility is usability (Sarah Richards), A11y Camp 2020
👁 Seeing
👂 Hearing
🖐 Touching
🧠 Thinking
🗣 Speaking
👁 Seeing
👂 Hearing
🖐 Touching
🧠 Thinking
🗣 Speaking
Disability ≠ Personal Health Condition
Disability = Mismatched Human Interactions
Accessibility: Literally, gaining access
Inclusion: Not wishing you hadn’t
Good to know: Universal Design (wikipedia).
“Universal design is design that’s usable by all people, to the greatest extent possible, without the need for adaptation or specialized design.”–Ron Mace
The web platform is a collection of technologies.
The web is accessible by default.
If accessibility is missing, we broke it ourselves.
More at W3C Web Accessibility Laws & Policies
At the core: W3C Web Content Accessibility Guidelines (WCAG)
The core is always WCAG, currently WCAG 2.2.
Introductory: W3C Accessibility Principles, WebAIM articles…
expert blogs: a11y-collective, smashing magazine, Stéphanie Walter…
WCAG foundation: All content has to be
for all users.
Automated
Manual testing
User testing: critical for anything complex
Avoid: Accessibility Overlays
Output: custom display, screen magnifier, audio, braille, vibration…
Input: adaptive keyboards, mouse, joystick, trackball, switch access, braille, speech, head pointer, eye tracking, sip&puff…
The point is not to create a better experience, or even a good experience.
It’s to ensure a comparable experience between different people.
Interfaces should not be challenging to some and not to others, but some interfaces are necessarily complex and some content is inherently esoteric. […]
These are shortcomings of inclusivity, not accessibility.
Accessibility is a process for helping people.