In this webinar, you will learn about important updates coming in WCAG 2.2 and what they mean. This webinar will be presented by A360's Michele Landis, CRO, and Co-Founder.

1. Implementing WCAG 2.2
into Your Digital Strategy

2. HELLO!
Michele Landis
Co-Founder Accessible360
Aaron Cannon, CPWA
Co-Founder Accessible360 CPACC | WAS

3. Intro
Still not published
Augments, does not replace, 2.0 and 2.1
Backwards compatible (conforming to 2.2 means you also
conform to 2.1 & 2.0)
10 new and 1 updated success criteria
3 level A
5 level AA
2 level AAA
1 promoted from AA to A
WCAG 2.2

4. Why the New Version?
Continues the work started in WCAG 2.1
Improving accessibility guidance for three major groups
users with cognitive or learning disabilities
users with low vision
All disabled Mobile device users
WCAG 2.2

5. 2.4.7 Focus Visible
Level A (used to be AA)
Any keyboard operable user interface has a mode of operation
where the keyboard focus indicator is visible.
WCAG 2.2

6. 2.4.11 Focus Appearance (Minimum)
Level AA
When user interface components receive keyboard focus, an
area of the focus indicator meets the following:
Minimum area: The area is either:
at least as large as the area of a 1 CSS pixel thick perimeter of
the unfocused component, or
at least as large as the area of a 4 CSS pixel thick line along the
shortest side of a minimum bounding box of the unfocused
component, and no part of the area is thinner than 2 CSS pixels.
WCAG 2.2

7. 2.4.11 Focus Appearance (Minimum) Cont.
Contrast: The area has a contrast ratio of at least 3:1 between
the colors when the component is focused and it is not focused.
Adjacent contrast: Where the area is adjacent to the
component, it has a contrast ratio of at least 3:1 against the
component or a thickness of at least 2 CSS pixels.
Additionally, the item with focus is not entirely hidden by
author-created content.
WCAG 2.2

8. 2.4.13 Page Break Navigation
Level A
For web content with page break locators, a mechanism is
available to navigate to each locator.
WCAG 2.2

9. WCAG 2.2
2.5.7 Dragging Movements
Level AA
All functionality that uses a dragging movement for operation
can be operated by a single pointer without dragging, unless
dragging is essential.
NOTE
This requirement applies to web content that interprets pointer
actions (i.e. this does not apply to actions that are required to
operate the user agent or assistive technology).
Reasoning
Some people cannot perform dragging motions in a precise
manner. Others use a specialized or adapted input device such as
a head pointer, eye-gaze system, or speech-controlled mouse
emulator, which makes dragging cumbersome, error-prone, or
outright impossible.

10. WCAG 2.2
2.5.8 Pointer Target Spacing
Level AA
The size of the target for pointer inputs is at least 24 by 24 pixels,
except where:
Spacing: The target offset is at least 24 CSS pixels to every
adjacent target;
Inline: The target is in a sentence or block of text;
Necessary: A particular presentation of the target is essential or
is legally required for the information being conveyed.
Legal: A particular presentation of the target is legally required.

11. WCAG 2.2
3.2.6 Consistent Help
Level A
For each web page within a set of web pages that provides one
or more of the following ways of finding help, access to at least
one form of help is included in the same relative order on each
page:
Human contact details;
Human contact mechanism;
Self-help option;
A fully automated contact mechanism.
NOTE
Access to help mechanisms may be provided directly on the page,
or may be provided via a direct link to a different page containing
the information

12. WCAG 2.2
3.2.7 Visible Controls
Level AA
Where receiving pointer hover or keyboard focus triggers user
interface components to be visible, information needed to identify
that user interface components are available is visible, except
when:
The information needed to identify the user interface components
is available through an equivalent component that is visible on the
same page or on a different step in a multi-step process without
requiring pointer hover or keyboard focus;
The component is provided specifically to enhance the
experience for keyboard navigation;
A mechanism is available to make the information persistently
visible;
Hiding the information needed to identify the component is
essential.

13. 3.3.7 Accessible Authentication
Level AA [New]
For each step in an authentication process that relies on a cognitive
function test, at least one other authentication methos is available that
does not rely on a cognitive function test, or a mechanism is available to
assist the use in completing the cognitive function test.
Exception:
When the cognitive function test is to recognize common objects or
content the user provided to the website.
NOTES
Common objects and content for the exception may be represented by
images, text, video or audio.
Examples of mechanisms include: 1) support for password entry by
password managers to address the memorization cognitive function test,
and 2) copy and paste to help address transcription cognitive function test.
WCAG 2.2

14. 3.3.9 Redundant Entry
Level A
Information previously entered by or provided to the user that is
required to be entered again in the same process is either:
auto-populated, or available for the user to select.
Exception:
When re-entering the information is essential, the information is
required to ensure the security of the content, or when
previously entered information is no longer valid.
WCAG 2.2

15. WCAG 3.0

16. Intro
See Draft
Not just new success criteria
A new approach to web accessibility
Expressly includes guidelines for web, mobile, and desktop
applications
Not necessarily compatible with 2.X
Specifies how to test against the standards and how to score those
tests
Anticipates substantial conformance in addition to full conformance
WCAG 3.0

17. Problems With Previous Versions
True/false accessibility does not match the real world
Accessibility is a spectrum
WCAG is all but useless for people new to accessibility
A 10 year (or even 2 year) refresh cycle fails to keep up with
tech
WCAG 3.0

18. WCAG 3.0
The New Structure
Made up of a list of guidelines
Guidelines are broad categories of issues
Written to be understood by non-technical folks
Think of these as similar to the various guidelines (not success
criteria) within WCAG 2
Each guideline has a list of outcomes, critical errors,
and information on how to score each outcome
outcomes are intended for technical folks
Most similar to the individual success criteria in WCAG 2
Critical Errors are descriptions of things, which if they happen
mean an instant failure of the outcome

19. The New Structure Cont.
Each outcome has a list of methods, critical errors, tests, and
categories
Methods are similar to the current technique documents
Critical Errors are descriptions of things, which if they happen
mean an instant failure of the outcome
WCAG 3.0

20. Guideline examples
Provide text alternative for non-text content.
Use common clear words.
Provide captions and associated metadata for audio content.
WCAG 3.0

21. Outcome Examples
Text alternative available
Uses common and clear words in all content.
Translates speech and non-speech audio
WCAG 3.0

22. Critical Error Examples
Any image of text without an appropriate text alternative
needed to complete a process.
Any video without captioning that is needed to complete a
process.
None (Not all guidelines have critical errors)
WCAG 3.0

23. Method Examples
Text alternative for Image of text (HTML)
Functional Images (HTML, PDF, ePub)
Decorative images (HTML, PDF, ePub)
Informative images (HTML)
Author control of text alternatives (ATAG)
Use Clear Words (All)
Provides text equivalents of speech and key sound effect (XR)
WCAG 3.0

24. The Future …..

25. WCAG 3.0
Example rating for Text Alternative
Rating 0: Less than 60% of all images have appropriate text
alternatives OR there is a critical error in the process
Rating 1: 60% - 69% of all images have appropriate text
alternatives AND no critical errors in the process
Rating 2: 70% - 79% of all images have appropriate text
alternatives AND no critical errors in the process
Rating 3: 80% - 95% of all images have appropriate text
alternatives AND no critical errors in the process
Rating 4: 95% to 100% of all images have appropriate text
alternatives AND no critical errors in the process

26. Automated Scanning & Human Testing
Use an automated tool to decide how many images lack
alternative text
A human reviews the missing alts to decide if any constitute a
critical error
Poor alternative text that passes an automated tool does not
seem to have been addressed in this early draft
WCAG 3.0

27. How Sites/Apps/Documents Etc. Are Scored
Treats content required to complete a process more strictly
than other content
Recognizes that bugs happen and does not penalize them
excessively unless they are blockers
Offers conformance levels of Bronze, Silver, and Gold
While you can claim a conformance level for the entire site,
encourages claiming conformance for processes or individual
views
WCAG 3.0