Don't sleep on WCAG 2.2:
it helps real people
David Cox (he / him)
Slides and resources
Hi, I’m David 👋
I was working in London
Now I’m back
in Toronto
I work on
design systems,
I work on
design systems,
web accessibility
I work on
design systems,
web accessibility
and product design.
My goal is to
massively improve things that matter.
Massively improve:
For things that matter:
Past design systems:
Current design system:
Note: opinions expressed are my own.
This talk does not represent the opinions or policies of any organization.
Vibe check
Making websites more accessible can be tricky.
What’s the point of WCAG?
What’s the point of WCAG 2.1?
What’s the point of WCAG 2.2?
WCAG 2.1:
“defines how to make Web content more accessible to people with disabilities.”
WCAG 2.2:
“defines how to make Web content more accessible to people with disabilities.”
They’re the ‘same picture’
(well, their purpose is the same)
But WCAG 2.2 isn’t some ‘special edition’
version.
It’s more like a firmware update.
WCAG 2.2
“I’m you, but stronger.”
WCAG 2.1
“Who are you?”
2.2 adds 9 criteria to address 7 specific accessibility needs.
2.2 removes 1 criterion that is no longer relevant.
2.2 expands the glossary with 6 new terms.
What’s the point?
What’s the point?
A more complete set of guidelines, to better meet the intended goal.
The intended goal:
Make web content more accessible to people with disabilities.
But is aiming for WCAG 2.1
good enough?
… Is relying on an outdated instruction manual good enough?
Hot take: WCAG 2.1 was never
‘good enough’.
So what do we do?
Start from:
real lived experiences.
Refer back to:
real lived experiences.
Make it easier to:
Interact within services.
Target size
The intent: target size
To prevent selecting the wrong item on small or crowded screens.
Clue: target size
Elements are:
Examples: target size
Sometimes applies to:
Dragging
movements
The intent: dragging movements
To make sure interactions which allow for selecting elements and dragging them also work without dragging.
Clue: dragging movements
An element:
Examples: dragging movements
Sometimes applies to:
Make it easier to:
Navigate through services.
Easier for people who are:
Navigating with a keyboard.
For example, to help ease
Focus
appearance
The intent: focus appearance
To provide a clearer and more noticeable visual change when indicating which element of a website is currently focused.
Clue: focus appearance
An element’s focus indicator:
Examples: focus appearance
Applies to anything with a focus indicator:
Focus not obscured
The intent: focus not obscured
To make sure that whichever element is currently focused isn’t covered up by other elements.
Clue: focus not obscured
An element either:
Examples: focus not obscured
Applies to anything blocking focusable elements:
Make it easier to:
Find help within services.
Easier for people who are:
Navigating based on
reading order.
For example, when using a screen reader.
Easier for people who are:
Dealing with high stress
or anxiety.
For example, from a panic disorder.
Consistent help
The intent: consistent help
To place help and support tools that exist across multiple pages in a consistent spot.
Clue: consistent help
A series of pages across a service include:
Examples: consistent help
Sometimes applies to:
Make it easier to:
Enter the right information.
Easier for people experiencing:
Fatigue from manually
entering information.
For example, due to arthritis.
Redundant entry
The intent: consistent help
To avoid asking for the same information multiple times in a single journey, and enable previously entered information to be re-used.
Clue: redundant entry
A single online journey requires a user to:
Examples: redundant entry
Sometimes applies when asking for:
Make it easier to:
Log in to
services.
Easier for people experiencing:
Difficulties with problem-solving.
For example, due to a cognitive disability that affects visual comprehension.
Easier for people experiencing:
Difficulties with
math or numbers.
For example, due to dyscalculia.
Accessible authentication
The intent: consistent help
To avoid cognitive function tests, puzzles and memorization exercises during login processes.
Clue: accessible authentication
A login process contains any of the following:
Examples: accessible auth
Applies when:
That’s a lot of info.
But what’s the main point?
Let’s review.
Looking just at the 9 new criteria…
WCAG 2.2 helps people using:
mobile devices | screen readers | voice command software |
mouth sticks | keyboards |
switches | other pointer inputs
WCAG 2.2 helps people to:
login | navigate | enter information | find help info | interact with services
WCAG 2.2 helps people with:
dementia | dyslexia | arthritis | RSI | Parkinson’s disease | cataracts | cognitive disabilities | dyscalculia | panic disorders | cerebral palsy
WCAG 2.2 helps people who are experiencing:
anxiety | stress | tremors | fatigue
WCAG 2.2 helps people who are having difficulty:
problem-solving | reading |
writing | remembering | calculating
So, WCAG 2.2 can do a lot.
And most importantly…
WCAG 2.2 helps lots of real people.
Let’s
help people.
Questions
and thank you!
WCAG 2.2
helps people.