2. 1 Mark Malamud February 23, 2016 Based on the presentation prepared by Bruce Bailey and Katie Haritos-Shea December 15, 2015 Using WCAG 2 for Section 508 Compliance

3. 222 WCAG 2.0 for Section 508 Details & Success Criteria The New Items!

4. 3 WCAG 2 – What IS all this new stuff? Good news… really! Much of it is not new. We have been doing a lot of these things already.

5. 4 WCAG 2.0 Support Documents are Update-Able Deliberative professional and public vetting process WCAG 2.0 is an International Standard W3C Standard in 2008 ISO Standard in 2012: ISO/IEC JTC-1 40500:2012 In Use in Several Countries (Government) Canada, Australia, New Zealand, Japan, elsewhere Soon to be Adopted in EU (Mandate 376)Mandate 376 Formal translations (18 so far) In Use Around the World in Industry Banking, Retail, Education, Business Why Use WCAG 2.0? (Page 1)

6. 5 Includes Cognitive, Language, and Learning (CLL) Technology Neutral Unlike 1194.22, it is not HTML specific Requirements (a.k.a. SC) are all yes/no statements Requirements are Objectively Testable Requirements very discrete and MOSTLY don’t require significant subjective expert judgment to evaluate… Why Use WCAG 2? (Page 2)

7. 6 There are two key concepts that must work together to ensure that information can be presented to the user of AT in an Accessible manner. 1.Authors must rely only on using technologies that are accessibility- supported - and – accessible themselves or work with assistive technology (AT) - and - 2.Authors must use those technologies properly in order for the content to be programmatically determinable - and hence presentable, by AT (and user agents) to users with disabilities Key Concepts to WCAG 2 Accessibility

8. 7 1.4 Show-Stoppers SC (all Level A) If these 4 SC do not pass, then very few PWD will even be able to use the ICT. 1.4.2: Audio Control (must NOT allow automatic playing of sounds – which over-rides screenreader audio track) 2.1.2: No Keyboard Trap (KB only user control) 2.2.2: Pause, Stop, Hide (user control, prevent seizures) 2.3.1: Three Flashes or Below Threshold (prevent seizures) 2.Level A SC (Lowest Level: provides Minimum Access) 3.Level AA SC (2 nd Level: provides Greater Access) Built-in Prioritization Path/Plan (for Remediation/QA) Why Use WCAG 2? Show Stoppers

9. 8 508 vs. WCAG 2 508 Standards508 Refresh 8 Sections – Technological4 Principles -- Conceptual 64 Provisions38 Success Criteria Defined by existing techAdaptable to new tech Evaluation ambiguousYes/No Testable

10. 9 508 vs. WCAG 2 – technological vs. conceptual 508 Standards508 Refresh 8 Sections – Technological 1194.21 Software Applications and Operating Systems (12 provisions) 1194.22 Web-based Internet and Intranet Information and Applications (16 provisions) 1194.23 Telecommunications Products (14) 1194.24 Video and Multi-media Products (5) 1194.25 Self-Contained, Closed Products (4) 1194.26 Desktop and Portable Computers (4) 1194.31 Functional Performance Criteria (6) 1194.41 Information, Documentation and Support (3) 4 Principles – Conceptual Perceivable, 4 Guidelines, 14 SC Operable, 4 Guidelines, 12 SC Understandable, 3 Guidelines, 10 SC Robust, 1 Guideline, 2 SC …And each principle contains guidelines that are also conceptual.

11. 10 WCAG 2 POUR (not poor) for Section 508 Design All of the following SC fall under these 4 A11Y Principles POUR 1.Perceivable 2.Operable 3.Understandable 4.Robust

12. 11 What is it made up of? What is in it? 4 Principles 12 Guidelines 38 Success Criteria (Requirements) 25 SC at Level A 13 SC at Level AA 24 SC at Level AAA (Not Required for Section 508/ADA – not counted) Links to Hundreds of Techniques and Failures (Not Required) WCAG 2.0: How the Standard is Structured

13. 12 Conformance Level: One level of conformance is met in full. 1.Level A (25 SC): (lowest/minimum) Content satisfies all the Level A SC, or a conforming alternate version is provided. Has the highest impact on the broadest array of user populations (highest degree of user impact), and has the lowest impact on the presentation and business logic of the site. Easier for developers. 2.Level AA (13 SC): (higher) Content satisfies all the Level A and Level AA SC, or a Level AA conforming alternate version is provided. Higher Bar. Has a high impact for specific user populations, and may impose more changes to the presentation or business logic of the site. Requires an additional level of effort for developers. 3.Level AAA: (highest) (Not applicable to Section 508/ADA) What Do the Conformance Levels Mean?

14. 13 Perceivable Provide text alternatives for non-text content. (1 Success Criterion) Provide captions and other alternatives for multimedia. (5 SC) Create content that can be presented in different ways, including by assistive technologies, without losing meaning. (3 SC) Make it easier for users to see and hear content. (5 SC) Operable Make all functionality available from a keyboard. (2 SC) Give users enough time to read and use content. (2 SC) Do not use content that causes seizures. (1 SC) Help users navigate and find content. (7 SC) Understandable Make text readable and understandable. (2 SC) Make content appear and operate in predictable ways. (4 SC) Help users avoid and correct mistakes. (4 SC) Robust Maximize compatibility with current and future user tools. (2 SC) WCAG 2.0: 4 Principles, 12 Guidelines

15. 14 WCAG 2.0 – 12 Guidelines & 38 Success Criteria PerceivableOperableUnderstandableRobust TEXT ALTERNATIVES FOR NON-TEXT 1.1.1Non-text Content (A) CAPTIONS OR ALTERNATIVES FOR MULTMEDIA 1.2.1Prerecorded Audio-only and Video-only (A) 1.2.2Captions (Prerecorded) (A) 1.2.3Audio Description or Media Alternative (A) 1.2.4Captions (Live) (AA) 1.2.5Audio Description (Prerecorded) (AA) CONTENT PRESENTED DIFFERENT WAYS 1.3.1Info and Relationships (A) 1.3.2Meaningful Sequence (A) 1.3.3Sensory Characteristics (A) EASIER TO SEE OR HEAR CONTENT 1.4.1Use of Color (A) 1.4.2Audio Control (A) 1.4.3Contrast (Minimum) (AA) 1.4.4Resize Text (AA) 1.4.5Images of Text (AA) ALL FUNCTIONALITY FROM KEYBOARD 2.1.1Keyboard (A) 2.1.2No Keyboard Trap (A) GIVE USERS ENOUGH TIME 2.2.1Timing Adjustable (A) 2.2.2Pause, Stop, Hide (A) NO CONTENT THAT TRIGGERS SEIZURES 2.3.1Three Flashes or Below Threshold (A) HELP USERS NAVIGATE AND FIND CONTENT 2.4.1Bypass Blocks 2.4.2Page Titled (A) 2.4.3Focus Order (A) 2.4.4Link Purpose (In Context) (A) 2.4.5Multiple Ways (AA) 2.4.6Headings and Labels (AA) 2.4.7Focus Visible (AA) MAKE TEXT READABLE AND UNDERSTANDABLE 3.1.1Language of Page (A) 3.1.2Language of Parts (AA) MAKE CONTENT APPEAR AND OPERATE PREDICTABLY 3.2.1On Focus (A) 3.2.2On Input (A) 3.2.3Consistent Navigation (AA) 3.2.4Consistent Identification (AA) AVOID AND CORRECT MISTAKES 3.3.1Error Identification (A) 3.3.2Labels or Instructions (A) 3.3.3Error Suggestion (AA) 3.3.4Error Prevention (Legal, Financial, Data) (AA) MAXIMIZE COMPATABLILITY WITH CURRENT AND FUTURE USER TOOLS 4.1.1Parsing (A) 4.1.2Name, Role, Value (A)

16. 15 WCAG 2.0 – What’s New 8 Guidelines & 16 Success Criteria PerceivableOperableUnderstandableRobust CONTENT PRESENTED DIFFERENT WAYS 1.3.2Meaningful Sequence (A) 1.3.3Sensory Characteristics (A) EASIER TO SEE OR HEAR CONTENT 1.4.2Audio Control (A) 1.4.3Contrast (Minimum) (AA) 1.4.4Resize Text (AA) ALL FUNCTIONALITY FROM KEYBOARD 2.1.2No Keyboard Trap (A) HELP USERS NAVIGATE AND FIND CONTENT 2.4.3Focus Order (A) 2.4.4Link Purpose (In Context) (A) 2.4.5Multiple Ways (AA) 2.4.6Headings and Labels (AA) MAKE TEXT READABLE AND UNDERSTANDABLE 3.1.1Language of Page (A) 3.1.2Language of Parts (AA) MAKE CONTENT APPEAR AND OPERATE PREDICTABLY 3.2.3Consistent Navigation (AA) AVOID AND CORRECT MISTAKES 3.3.3Error Suggestion (AA) 3.3.4Error Prevention (Legal, Financial, Data) (AA) MAXIMIZE COMPATABLILITY WITH CURRENT AND FUTURE USER TOOLS 4.1.1Parsing (A)

17. 16 When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) WCAG 2 Link: 1.3.2 Meaningful Sequence1.3.2 Meaningful Sequence Must Work with AT (Key Concept -- Must be Programmatically Determinable) Reading Order Applicable to: Web, Software and Non-Web Documents. (Developers will adapt SW and NWD for Closed Functionality products). WebAIM Recommends The reading and navigation order (determined by code order) is logical and intuitive. See Designing for Screen Reader Compatibility > Content Linearization.Designing for Screen Reader Compatibility Perceivable 1.3.2 Meaningful Sequence (Reading Order) (Level A)

18. 17 Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A) WCAG 2 Link: 1.3.3 Sensory Characteristics 1.3.3 Sensory Characteristics Note: For requirements related to color, refer to Guideline 1.4. Helps: Blind, Low Vision. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends Instructions do not rely upon shape, size, or visual location e.g., “Click the square icon to continue” or “Instructions are in the right-hand column”. Instructions do not rely upon sound e.g., “A beeping sound indicates you may continue”. Perceivable 1.3.3 Sensory Characteristics (Level A)

19. 18 If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A) Individuals who use screen reading software can find it hard to hear the speech output if there is other audio playing at the same time. WCAG 2 Link: 1.4.2 Audio Control1.4.2 Audio Control Conformance Show-Stopper (# 1 of 4) Helps: Blind, H-o-H, Screen reader Users, Cognitive. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds. Perceivable 1.4.2 Audio Control (Level A)

20. 19 The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA) Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; Incidental: Text or images of text that are part of an inactive UI component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement. WCAG 2 Link: 1.4.3 Contrast (Minimum)1.4.3 Contrast (Minimum) Helps: Low Vision, Color-Blind, Elderly. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends Text and images of text have a contrast ratio of at least 4.5:1.contrast ratio Large text (over 18 point or 14 point bold) has a contrast ratio of at least 3:1. Perceivable 1.4.3 Contrast (Minimum) (Level AA)

21. 20 Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) WCAG 2 Link: 1.4.4 Resize Text1.4.4 Resize Text Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) May be satisfied by Browser, Software and OS Zoom – accept for Mobile where viewport constraints are often used Helps: Low Vision, Partially Sighted, Elderly. Applicable to: Web, Software and Non-Web Documents. (Developers will adapt SW and NWD for Closed Functionality products). WebAIM Recommends The page is readable and functional when the text size is doubled. Perceivable 1.4.4 Resize Text (Level AA)

22. 21 If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface… and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A) Conformance Show-Stopper (# 2 of 4) WCAG 2 Link: 2.1.2 No Keyboard Trap2.1.2 No Keyboard Trap Helps: Blind, Deaf-Blind, Low Vision, Physical Disabilities, Keyboard Users. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends Keyboard focus is never locked or trapped at one particular page element. Keyboard The user can navigate to and from all navigable page elements using only a keyboard. Operable 2.1.2 No Keyboard Trap (Level A)

23. 22 If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A) WCAG 2 Link: 2.4.3 Focus Order2.4.3 Focus Order Helps: Keyboard Users, Mobility Impairment, Low Vision, Elderly, Mobile Device Users. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends The navigation order of links, form elements, etc. is logical and intuitive. Operable 2.4.3 Focus Order (Level A)

24. 23 The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) WCAG 2 Link: 2.4.4 Link Purpose (In Context)2.4.4 Link Purpose (In Context) Helps: Blind, Blind-Deaf, Cognitive, Mobility/Motility Impairments. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context e.g., surrounding paragraph, list item, table cell, or table headers. Links (or form image buttons) with the same text that go to different locations are readily distinguishable. Operable 2.4.4 Link Purpose (In Context) (Level A)

25. 24 More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA) WCAG 2 Link: 2.4.5 Multiple Ways2.4.5 Multiple Ways Helps: Blind, Deaf-Blind, Low Vision, Cognitive, PWD Search. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends Multiple ways are available to find other web pages on the site, at least two of: Multiple ways a list of related pages; table of contents; site map; site search; or list of all available web pages. KHS: Home Page Links to All Pages Operable 2.4.5 Multiple Ways (Level AA)

26. 25 Headings and labels describe topic or purpose. (Level AA) WCAG 2 Link: 2.4.6 Headings and Labels2.4.6 Headings and Labels Helps: Blind, Deaf-Blind, Low Vision, Cognitive (Memory), Elderly, Mobility/Motility Impairments. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., “More Details”) or label text (e.g., “First Name”) unless the structure provides adequate differentiation between them. Operable 2.4.6 Headings and Labels (Level AA)

27. 26 The default human language of each Web page can be programmatically determined. (Level A) WCAG 2 Link: 3.1.1 Language of Page3.1.1 Language of Page Must Work with AT (Key Concept -- Must be Programmatically Determinable) Helps: Screen Reader Users, CCL Text-to-Speech AT Users, Blind, Deaf-Blind, Low Vision, Users who rely on Captions. Applicable to: Web, Software and Non-Web Documents. (Developers will adapt SW and NWD for Closed Functionality products). WebAIM Recommends The language of the page is identified using the HTML lang attribute, for example. Understandable 3.1.1 Language of Page (Level A)

28. 27 The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) WCAG 2 Link: 3.1.2 Language of Parts3.1.2 Language of Parts Must Work with AT (Key Concept -- Must be Programmatically Determinable) Helps: Screen Reader Users, CCL Text-to-Speech AT Users, Blind, Deaf-Blind, Low Vision, Users who rely on Captions. Applicable to: Web, Software and Non-Web Documents. (Developers will adapt SW and NWD for Closed Functionality products). WebAIM Recommends The language of page content that is in a different language is identified using the lang attribute e.g.,. Understandable 3.1.2 Language of Parts (Level AA)

29. 28 Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) WCAG 2 Link: 3.2.3 Consistent Navigation3.2.3 Consistent Navigation Helps: Blind, Deaf-Blind, Low Vision, CLL Disabilities, Elderly. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends Navigation links that are repeated on web pages do not change order when navigating through the site. Understandable 3.2.3 Consistent Navigation (Level AA)

30. 29 If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) WCAG 2 Link: 3.3.1 Error Identification3.3.1 Error Identification Helps: Blind, Deaf-Blind, Color-Blind, CLL Disabilities, Elderly. Applicable to: Web, Software and Non-Web Documents. (Developers will adapt SW and NWD for Closed Functionality products). WebAIM Recommends Required form elements or form elements that require a specific format, value, or length provide this information within the element's label. If utilized, form validation errors are presented in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.form validation Understandable 3.3.1 Error Identification (Level A)

31. 30 If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) WCAG 2 Link: 3.3.3 Error Suggestion3.3.3 Error Suggestion Helps: Blind, Deaf-Blind, Low Vision, CLL Disabilities, Elderly, Mobility/Motility Impairments. Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends If an input error is detected (via client-side or server-side validation), provide suggestions for fixing the input in a timely and accessible manner. Understandable 3.3.3 Error Suggestion (Level AA)

32. 31 For Web pages that cause legal commitments or financial transactions for the user to occur, modify or delete user-controllable data in data storage systems, or submit user test responses, at least one of the following is true: (Level AA) 1.Reversible: Submissions are reversible. 2.Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. 3.Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. WCAG 2 Link: 3.3.4 Error Prevention (Legal, Financial, Data) 3.3.4 Error Prevention (Legal, Financial, Data) Helps: All PWD Applicable to: Web, Software and Non-Web Documents. WebAIM Recommends If the user can change or delete legal, financial, or test data, the changes / deletions can be reversed, verified, or confirmed. Understandable 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

33. 32 In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A) Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete. WCAG 2 Link: 4.1.1 Parsing4.1.1 Parsing Accessibility vs. Usability – This is One Helps: All PWD who Use AT. Applicable to: Web, Software and Non-Web Documents. (Developers will adapt SW and NWD for Closed Functionality products). WebAIM Recommends Significant HTML/XHTML validation/parsing errors are avoided. Check at http://validator.w3.org/ http://validator.w3.org/ Robust 4.1.1 Parsing (Level A)

34. 33 WCAG 2.0 Success Criteria –Questions

35. 34 WCAG 2.0 Success Criteria – Resources Recommended Links Web Content Accessibility Guidelines (WCAG) Overview Includes links to supporting documents Web Content Accessibility Guidelines (WCAG) Overview How to Meet WCAG 2.0 A customizable quick reference to Success Criteria and techniques How to Meet WCAG 2.0 Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) W3C Working Group Note, September 2013 Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) Comparison Table of WCAG 2.0 to Existing 508 Standards Web Content Accessibility Guidelines (WCAG) 2.0

36. 35 WCAG 2.0 Success Criteria – The New 16 Ones The End

37. 36 Current 508 Gaps Example — Language of Page BONUS SLIDE Problems: English encoded as French, Spanish text encoded as English. Correct encoding (English). WCAG 2.0 SC 3.1.1, 3.1.2: The human language of each page, passage, or phrase can be programmatically determined.