Learn about the latest mobile accessibility requirements in WCAG 2.1, mobile developer resources, and future standards from W3C/WAI.

1. Mobile Accessibility in
WCAG 2.1 and Beyond
KATHLEEN WAHLBIN AND SHADI ABOU-ZAHRA
13/21/2018

2. Mobile
Landscape
Changed the way people are
consuming information
2
All ages are using mobile
Using one handed
Using touch screens
Situations where we have
busy eyes and hands
Out in bright light
In noisy, public spaces
3/21/2018

3. W3C Mobile Accessibility Task Force
Task Force of the W3C AG Working Group
Exploring improvements for mobile space
◦ Analysis of user needs and existing resources
◦ Proposed new Success Criteria for WCAG 2.1
◦ Input for future work on WCAG 2.2(?), Silver, …
3/21/2018 3

4. Mobile Accessibility Policies
US Section 508: WCAG 2.0
Europe: EN 301 549 v2.1 (in development,
currently WCAG 2.1 CR without “At Risk”)
Other local developments with risk of standards
fragmentation
3/21/2018 4

5. Mobile Accessibility in WCAG 2.1 CR
Candidate Recommendation
Draft from 30 January 2018:
◦ w3.org/TR/WCAG21
Comments until 30 March
Session on WCAG 2.1 tomorrow
at 8:00am in this same room
3/21/2018 5

6. WCAG 2.1
All of WCAG 2.0
5 New SCs at Level A
7 New SCs at Level AA
5 New SCs at Level AAA
3/6/2015 6

7. New Mobile Requirements in WCAG 2.1
Speech Input
◦ Character Key Shortcuts
◦ Label in Name
Pointer
◦ Pointer Gestures
◦ Pointer Cancellation
◦ Target Size
Input Methods
◦ Concurrent Input
Mechanisms
◦ Motion Actuation
Device Settings
◦ Orientation
Status Changes
3/21/2018 7

8. New in WCAG 2.1: Conformance Note
5.2.2 Full Pages:
Note 3
A full page includes each variation of the page that
is automatically generated by the page for various
screen sizes. Each of these variations needs to
conform (or needs to have a conforming alternate
version) in order for the entire page to conform.
3/21/2018 8

9. New in WCAG 2.1: Pointer Gestures
2.5.1 Pointer Gestures
All functionality that uses multipoint or path-
based gestures for operation can be operated
with a single pointer without a path-based
gesture, unless a multipoint or path-based
gesture is essential.
3/21/2018 9

10. New in WCAG 2.1: Pointer Cancellation
2.5.2 Pointer Cancellation
For functionality that can be operated using a single
pointer, at least one of the following is true:
◦No Down Event: […]
◦Abort or Undo: […]
◦Up Reversal: […]
◦Essential: […]
3/21/2018 10

11. New in WCAG 2.1: Target Size
2.5.3 Target Size
The size of the target for pointer inputs is at least 44 by 44 CSS
pixels except when:
◦ Equivalent - The target is available through an equivalent link or
control on the same page that is at least 44 by 44 CSS pixels;
◦ Inline - The target is in a sentence or block of text;
◦ User Agent Control - The size of the target is determined by the
user agent and is not modified by the author.
◦ Essential - A particular presentation of the target is essential to the
information being conveyed
3/21/2018 11

12. New in WCAG 2.1: Non-Text Contrast
1.4.11 Non-Text Contrast
The visual presentation of the following have a
contrast ratio of at least 3:1 against adjacent
color(s):
◦User Interface Components: […]
◦Graphical Objects: […]
3/21/2018 12

13. Next Steps for
Us
Input Input to discussion on future guidelines
Support Support the completion of WCAG 2.1
Complete Complete Understanding and Techniques
Document Document implementations of new SCs
3/21/2018 13

14. Next Steps for
You
Engage in Engage in future developments on “Mobile”
Provide
Provide comments on WCAG 2.1 CR Draft
• GitHub: github.com/w3c/wcag21/issues/new
• Email: public-agwg-comments@w3.org
Implement Implement new WCAG 2.1 Success Criteria
3/21/2018 14

15. Questions?
153/21/2018