WCAG 2.1: What is Next for Accessibility Guidelines WCAG Next WCAG 2.1: What is Next for Accessibility Guidelines WCAG 2.1 – The next “minor” version of WCAG became a full W3C Recommendation on June 5, 2018! The W3C has been researching user needs and writing proposed WCAG 2.1 success criteria to fill known gaps. Silver – A parallel effort is also in motion to create a major revision of digital accessibility guidelines. The code name for this major revision is Silver. Come to this session and learn how WCAG 2.0, 2.1, Silver, ATAG and UAAG relate to each other. Discover three areas of known gaps in WCAG 2.0. Dive in and look at the 12 proposed WCAG 2.1 Success Criteria that have been approved at A and AA. Last, but not least, we will look ahead and predict when WCAG 2.1 will be required and when Silver may become a reality. A glimpse into the future of WCAG 2.1 and Silver will help you be a better accessibility expert today!

Glenda Sims @goodwitch deque.com #a11y

WCAG Flight Path (Agenda) History of WCAG WCAG 2.1 & Silver Requirements Timeline WCAG 2.1 A/AA How to Get Involved

History of WCAG WCAG 1.0 – May 5, 1999 WCAG 2.0 – December 11, 2008 Focused on html WCAG 2.0 – December 11, 2008 Perceivable Operable Understandable Robust WCAG What Is Next?

WCAG Next – Parallel Efforts fill known gaps focused release (before Silver) Silver Accessibility Guidelines (AG) Broader than just web Likely to encompass UAAG and ATAG

Web Content ATAG + WCAG + UAAG illustration with labeled graphics of boxes, content, and people. at the top center is a pie chart, an image, a form, and text, labeled 'content'. coming up from the bottom left, a line connects 'developers' through 'authoring tools' and 'evaluation tools' to 'content' at the top. coming up from the bottom right, an arrow connects 'users' to 'browsers, media players' and 'assistive technologies' to 'content' at the top. below these are 'accessibility guidelines' which include 'ATAG' with an arrow pointing to 'authoring tools' and 'evaluation tools', 'WCAG' pointing to 'content', and 'UAAG' pointing to 'browsers, media players' and 'assistive technologies'. at the very bottom, 'technical specifications (HTML, XML, CSS, SVG, SMIL, etc.)' forms a base with an arrow pointing up to the accessibility guidelines. User Agent (Examples: Browser, Assistive Technology Authoring Tool (Example: Content Management System) illustration showing the accessibility guidelines for the different components ATAG, WCAG and UAAG, detailed description at http://www.w3.org/WAI/intro/components-desc.html#guide

WCAG 2.1 Requirements Backwards compatible with WCAG 2.0 WCAG 2.1 Success Criterion must be Very clear, distinct and testable Continue WCAG 2.0 A/AA/AAA model WCAG 2.0 will remain a valid standard / http://w3c.github.io/wcag/wcag21/requirements

WCAG 2.1 Areas of Focus Cognitive (COGA) Low Vision Mobile

Requirements for Good Success Criteria Testable - testable thru auto or manual process Condition - describe condition to meet criteria, not method Applies to all content - exceptions explicitly identified Apply across technologies - HTML, mobile, PDF, etc Implementable - Be implementable today (through Techniques) using readily-available formats, user agents, and assistive technologies

WCAG Success Criteria Level A & AA Accessible Reasonable Technically Possible Now WCAG 2.0 SC A & AA Inspired by David MacDonald https://docs.google.com/spreadsheets/d/1XShLFX8fxHYYLn8A6avDwu37w9JfnZCGWvAKBpK9Xo4/edit#gid=793462493 Inspired by David MacDonald

WCAG 2.1 Timeline Jan 2017 – Accessibility Guidelines Charter Feb 2017 – 1st Public Working Draft Apr 2017 – 2nd Public Working Draft Jun 2017 – 3rd Public Working Draft Jul 2017 – 4th Public Working Draft Aug 2017 – 5th Public Working Draft Aug 22, 2017 – Stop accepting new WCAG 2.1 SC Sep 2017 – 6th Public Working Draft Dec 2017 – 7th Public Working Draft Jan 2018 – WCAG 2.1 Candidate Recommendation Jun 2018 – WCAG 2.1 Recommendation <<<< DONE ! Source: https://www.w3.org/WAI/GL/wiki/WCAG_2.1_timeline

WCAG 2.1 – Keep Calm and Breathe Deeply

How do you feel about WCAG 2.1 Right now?

When will YOU implement WCAG 2.1 ? © 2016 - All Rights Reserved

Ready for a Glimpse of YOUR A11Y Future?

W3C WCAG 2.1 Recommendation 5 SC at Level A 7 SC at Level AA 5 SC at Level AAA _______________________ 17 New (SC) Success Criteria https://www.w3.org/TR/WCAG21/#new-features-in-wcag-2-1

WCAG 2.1 (A/AA) New Success Criteria at A or AA level 1.3.4 Orientation (AA) 1.3.5 Identify Input Purpose (AA) 1.4.10 Reflow (AA) 1.4.11 Non-Text Contrast (AA) 1.4.12 Text Spacing (AA) 1.4.13 Content on Hover or Focus (AA) 2.1.4 Character Key Shortcuts (A) 2.5.1 Pointer Gestures (A) 2.5.2 Pointer Cancellation (A) 2.5.3 Label in Name (A) 2.5.4 Motion Actuation (A) 4.1.2 Status Changes (AA) https://www.w3.org/TR/WCAG21/#new-features-in-wcag-2-1

WCAG 2.1 (AAA) New Success Criteria at AAA level 1.3.6 Identify Purpose (AAA) 2.2.6 Timeouts (AAA) 2.3.3 Animation from Interaction (AAA) 2.5.5 Target Size (AAA) 2.5.6 Concurrent Input Mechanisms (AAA) https://www.w3.org/TR/WCAG21/#new-features-in-wcag-2-1

Let’s look closer at the 12 proposed SC at A and AA

Source: Mobile Task Force 1. 1.3.4 Orientation (AA) Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. "Don't force me to rotate my mobile device." - Goodwitch Persona Quote “I can't rotate my tablet — it's attached to my wheelchair.” - Comic with cerebral palsy who uses a wheelchair Source: Mobile Task Force https://www.w3.org/TR/WCAG21/#orientation SC Manager: Marc Johlic Origin: Mobile Accessibility Task Force (MATF)

2. 1.3.5 Identify Input Purpose (AA) The purpose of each input field collecting information about the user can be programmatically determined when: The input field serves a purpose identified in the Input Purposes for User Interface Components section; and The content is implemented using technologies with support for identifying the expected meaning for form input data. “Personalization Overlay: Help me fill out forms by letting me use labels that make sense to me!” - Goodwitch Persona Quote “I love websites that can automatically fill it all in (personal info) for me. Then I don't have to work so hard to get the numbers and spelling right.” Note: This works because the fields use autocomplete. - Supermarket assistant with dyslexia and dyscalculia Source: Cognitive Task Force https://www.w3.org/TR/WCAG21/#identify-input-purpose SC Manager: Lisa Seeman and John Foliot Origin: Cognitive Task Force (COGA)

Source: Low Vision Task Force 3. 1.4.10 Reflow (AA) Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning. “Horizontal scrolling is evil” - Goodwitch Persona Quote “It's nearly impossible to read text if I have to scroll right and left to read each line. It's disorienting and I lose my place. It makes it hard to understand what I'm reading.” - Parent with low vision Source: Low Vision Task Force https://www.w3.org/TR/WCAG21/#reflow SC Manager: Alastair Campbell Origin: Low Vision Task Force (LVTF)

4. 1.4.11 Non-Text Contrast (AA) The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components: Visual information required to identify user interface componentsand states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. “Did you actually want me to see that important graphic and/or control?” - Goodwitch Persona Quote “I couldn't use the "Order Form" — there were no text boxes. After a long call with customer service, I learned there were text box borders that were too light for me to see.” - Retiree with low contrast sensitivity Source: Low Vision Task Force https://www.w3.org/TR/WCAG21/#non-text-contrast SC Manager: Alastair Campbell Origin: Low Vision Task Force (LVTF)

5. 1.4.12 Text Spacing (AA) In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least 2 times the font size; Letter spacing (tracking) to at least 0.12 times the font size; Word spacing to at least 0.16 times the font size. Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script “This text is so hard to read! I need to be able  to adjust the spacing.” - Goodwitch Persona Quote “Most text is hard to read. It's so cluttered I can't keep my focus. Just increasing the space between lines makes all the difference. When I'm really tired, I also increase the space between words. - Student with dyslexia Low Vision Task Force https://www.w3.org/TR/WCAG21/#text-spacing SC Manager: Laura Carlson Origin: Low Vision Task Force (LVTF)

6. 1.4.13 Content on Hover or Focus (AA) Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author “ #@$% popup! I can’t control it and I can’t see what I need to see! Arrrrrgh! ” - Goodwitch Persona Quote “I was moving my mouse around to track what I was looking at on a web page. It helps me keep focused. Then -boom- this little box popped up. It covered what I was trying to read and I couldn't get it to go away.” - Teacher with low vision who uses screen magnification software Source: Low Vision Task Force https://www.w3.org/TR/WCAG21/#content-on-hover-or-focus SC Manager: Steve Repsher Origin: Low Vision Task Force (LVTF)

7. 2.1.4 Character Key Shortcuts (A) If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: Turn off: A mechanism is available to turn the shortcut off; Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc); Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus. “On NO! Computer! Stop! I did NOT mean that!” - Goodwitch Persona Quote “When I was using my mail app with voice commands, it kept deleting the messages instead of opening them.” Note: There was a shortcut key for delete that was triggered by something he was saying and no way to turn off the shortcut keys. - Reporter with repetitive stress injury who uses voice recognition software Source: Mobile Task Force https://www.w3.org/TR/WCAG21/#character-key-shortcuts SC Manager: David MacDonald Origin: Mobile Accessibility Task Force (MATF)

Source: Mobile Task Force 8. 2.5.1 Pointer Gestures (A) 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. “You expect me to do that complex hand gesture? Are you kidding me? What is this? The finger Olympics???” - Goodwitch Persona Quote “I can't move my fingers like that. I need another way to zoom in the map.” - Comic with cerebral palsy who has limited movement in fingers Source: Mobile Task Force https://www.w3.org/TR/WCAG21/#pointer-gestures SC Manager: Detlev Fischer Origin: Mobile Accessibility Task Force (MATF)

9. 2.5.2 Pointer Cancellation (A) For functionality that can be operated using a single pointer, at least one of the following is true: No Down-Event: The down-event of the pointer is not used to execute any part of the function; Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; Up Reversal: The up-event reverses any outcome of the preceding down-event; Essential: Completing the function on the down-event is essential. “Holy curse word! I did not mean to just _____!” - Goodwitch Persona Quote “I went to hit the "Mute" button and accidentally touched the "End Call" button instead. It hung up immediately.” - Politician with motor disabilities and low vision Source: Mobile Task Force https://www.w3.org/TR/WCAG21/#pointer-cancellation SC Manager: David MacDonald Origin: Mobile Accessibility Task Force (MATF)

Source: Mobile Task Force 10. 2.5.3 Label in Name (A) For user interface components with labels that include text or images of text, the name contains the text presented visually. “Computer! ‘Submit’ the form! Computer! Curses! Why aren’t you doing what I said?!?!” - Goodwitch Persona Quote “It understood most of my voice commands until I got to the Send button. I kept saying 'Send' and it didn't work.” Note:  It was visually labelled 'send' but the 'name' in the code was 'submit'. It would have worked if the 'name' started with 'send’. - Reporter with repetitive stress injury who uses voice recognition software Source: Mobile Task Force https://www.w3.org/TR/WCAG21/#label-in-name SC Manager: Jon Avila Origin: Mobile Accessibility Task Force (MATF)

Source: Mobile Task Force 11. 2.5.4 Motion Actuation (A) Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: Supported Interface: The motion is used to operate functionality through an accessibility supported interface; Essential: The motion is essential for the function and doing so would invalidate the activity. “Don’t make me tilt or shake.” - Goodwitch Persona Quote “I have tremors, so I need to turn off motion activation — and then be able to do stuff without motion actuation.” - Comic with cerebral palsy who uses a wheelchair Source: Mobile Task Force https://www.w3.org/TR/WCAG21/#motion-actuation SC Manager: David MacDonald Origin: Mobile Accessibility Task Force (MATF)

“I can’t tell if anything has happened.“ - Goodwitch Persona Quote 12. 4.1.3 Status Messages (AA) In content implemented using markup languages,  status messages can be programmatically determined  through role or properties such that they can be presented to the user by assistive technologies without receiving focus. “I can’t tell if anything has happened.“ - Goodwitch Persona Quote “I selected a class for the conference, but I can't tell if it got added to my schedule.” Accountant who is blind and uses a screen reader Source: Cognitive Task Force https://www.w3.org/TR/WCAG21/#status-messages SC Manager: Wayne Dick Origin: Mobile Accessibility Task Force (MATF) & Cognitive Task Force (COGA)

Do these 12 Proposed SC for WCAG 2.1 fix all known accessibility gaps? © 2016 - All Rights Reserved

WCAG 2.1 is a step in the right direction. © 2016 - All Rights Reserved

Will there be a WCAG 2.2? 2.2? 2.3?? 2.???

Silver Silver

Goals for Silver include as many perspectives as possible broadly communicate silver efforts easy and open communication channels use evidence and data to make decisions attend to the lifecycle of Silver (reasonable release cycle for new versions) broaden scope of applicability (beyond just “web content” also include “web apps”, “native mobile”, “digital documents”, perhaps even “TV on the Web”. define and engage stakeholders establish clear milestones source: https://www.w3.org/WAI/GL/wiki/Goals_for_Designing_the_Silver_Process

Silver is planned to be a major revision of Silver’s Progress July 12, 2016 - Silver Sub Group Created to explore a path forward Oct 27, 2016 - Agreement on Silver Process https://www.w3.org/WAI/GL/wiki/Process_of_Designing_Silver Nov 4, 2016 - Agreement on Silver Work Statement Dec 2016 – Publish Stakeholder Map (draft) Dec 2017 - Requirements gathering & research stage 2018 Report on research findings Create and refine prototypes; choose option Write requirements document Write editors draft for First Public Working Draft Silver is planned to be a major revision of WCAG, UAAG and ATAG Source: https://www.w3.org/WAI/GL/task-forces/silver/work-statement source: https://www.w3.org/WAI/GL/wiki/Goals_for_Designing_the_Silver_Process

5 Phases to Develop Silver Discovery Discovery Interpretation Ideation Experimentation New AG Standard 2020 Interpretation Ideation Experimentation Source: https://www.w3.org/WAI/GL/wiki/Process_of_Designing_Silver New AG Standard 2020

What is Silver Researching? How might we make accessibility guidelines easier to use? How might accessibility guidelines address more types of disabilities? How might we make conforming with guidelines more straightforward? How might we make the process of keeping accessibility guidelines current, achievable, and timely? How do we scope it? (Web content, native, platforms, hardware, where do you stop?) And much more…

Guess how many stakeholders for digital Accessibility Guidelines (AG / Silver) have been defined ? © 2016 - All Rights Reserved

Accessibility Guideline Stakeholders Defined by Silver (so far) 31!

Silver Stakeholders Accessibility consultant/advisor Accessibility designer Accessibility developer Accessibility influencer Accessibility specialist/helper AT developer Authoring tool developer Call center representative Chief Accessibility Officer Content provider/producer Designer Developer Disability organization Evaluation tool developer Government Policy Influencer in disabilities Instructor/Trainer IT manager Lawyer Organizational policy People with disabilities Platform developer (hardware, os, browser) Product manager Professional/Industry Org/Association Project manager QA Specialist Researcher Standards developer Training resource developer Technology innovator WCAG WG Source: https://docs.google.com/spreadsheets/u/1/d/128vPnCweXN9t4JBG7-AOeBhT-KquaWXcCsi3H-f8u94/preview

Silver Stakeholder Roles Consult Make Policy Use Policy Make Content Teach Research Make Standards Make Decisions Help People With Disabilities Beneficiary of Standards Communicate Measure / Test Source: https://docs.google.com/spreadsheets/u/1/d/128vPnCweXN9t4JBG7-AOeBhT-KquaWXcCsi3H-f8u94/preview

How will you make a difference?

Get Involved! WCAG 2.1 Silver Volunteer with the W3C We invite you (yes, you!) to get involved https://www.w3.org/WAI/about-links Help write techniques Silver Join community group: w3.org/community/silver

WCAG Next Questions & Feedback Slide owner: Glenda © 2016 - All Rights Reserved