WCAG 2.2 What’s coming
presentation by Carolyn Shannon at DrupalCamp Colorado 2020
A presentation at DrupalCamp Colorado in August 2020 in Denver, CO, USA by Carolyn Shannon
presentation by Carolyn Shannon at DrupalCamp Colorado 2020
Grew up in the Midwestern US Have siblings image: two young girls in early-American-style bonnets
Carolyn Shannon Manager of Technical Documentation @ Pantheon 12+yr Drupalista @chicagomom She/her pronouns image: profile image of presenterCarolyn Shannon
We make assumptions about the features of those who use our sites and content image: two young girls in early-American-style bonnets
Building, migrating, upgrading a site or UI - Care about accessibility - Want to expand your user base - Compliance needs
cognitive and learning, low vision, disabilities using mobile applications People with learning and cognitive disabilities have accessibility challenges using certain types of website/application controls and interfaces. image: chart with people figures illustrating disability types speak, hear, see, touch, and categories permanent, temporary, situational
Make one thing better, every day. image: knitting on a knitting needle, with increases that shape the fabric
World Wide Web Consortium Web Content Accessibility Group Accessibility Guidelines Working Group (AG WG)
Current version: 2.1 Conformance levels A, AA, AAA Perceivable Operable Understandable Robust
Working Draft Wide Review Working Draft - Aug 2020 Candidate Recommendation Proposed Recommendation W3C Recommendation - mid-2021
WCAG 2.2 Guidelines (working draft, for wide review 11 Aug 2020) Overview blog post | w3.org Making Content Usable for People with Cognitive and Learning Disabilities | Working Draft Note 17 Jul 2020 COGA TF Gap Analysis Submit comments through 18 Sep 2020 - via GitHub issue - https://github.com/w3c/wcag/issues - via email - public-agwg-comments@w3.org
Nine new success criteria, one criteria promoted
Purpose: Make it easier to know where you are when using keyboard navigation WCAG 2.2 Draft Level A [promoted] Success Criterion 2.4.7
Purpose: Make it easier to see which component has focus WCAG 2.2 Draft Level AA [new] Success Criterion 2.4.11
Purpose: Make component that has focus highly visible WCAG 2.2 Draft Level AAA [new] Success Criterion 2.4.12
Purpose: On e-pubs, page links exist and the table of contents links always point to the same locator.
Purpose: moving, re-ordering, sliders Alternatives: click-to-move WCAG 2.2 Draft Level AA [new] Success Criterion 2.5.7
Purpose: increase the hit/tap area of targets WCAG 2.2 Draft Level AA [new] Success Criterion 2.5.8
Purpose: Consistent placement! WCAG 2.2 Draft Level A [new] Success Criterion 3.2.6
Purpose: Don’t hide things I need to complete the current task. Examples: auto-hiding multimedia controls, inline edit icons WCAG 2.2 Draft Level AA [new] Success Criterion 3.2.7 image: multimedia video controls
Alternatives: Honeypot, Antibot (JS), 2FA, tokens, keygen, biometric WCAG 2.2 Draft Level A [new] Success Criterion 3.3.7 image: captcha image
Purpose: Help users avoid and correct mistakes. Examples: re-entering the same information on a multi-part form WCAG 2.2 Draft Level A [new] Success Criterion 3.3.8 image: admin interface for Drupal webform module
The cheapest, easiest time to do accessibility work is during design and site building.
Incorporate WCAG 2.2 principles into your site design and testing now; you’ll be prepared for success.
It doesn’t have to be perfect. It just has to be a little bit better than yesterday. — Léonie Watson
Thank you! — Carolyn Shannon
