1. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. How to Explain WCAG 2.0 to Your Web Team Andrew Kirkpatrick | Adobe Accessibility 1

2. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Focus on why conforming to WCAG is important 2 People

3. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Developers are people too 3 Help authors understand the value of their efforts Help authors understand that the standard is to make their work easier

4. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Provide the 10,000 foot view WCAG 2.0 can be a jumble of words to new readers 4

5. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Provide the 10,000 foot view  Standards (Normative)  WCAG 2.0  Related Documentation (Informative)  Techniques for WCAG 2.0  Understanding WCAG 2.0  How To Meet WCAG 2.0 5

6. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Provide the 10,000 foot view 6

7. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Provide the 10,000 foot view 7 WCAG 2.0 is not Section 508 is not the ADA (but your web team probably doesn’t care about policy)

8. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Developers are people too 8 New + Unfamiliar = Feels difficult and uncertain Provide a safety net.

9. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Simplify  Web teams need simpler advice  Knowing what your team does and doesn’t do helps eliminate items which aren’t applicable.  Web site is entirely in HTML/JS/CSS?  Web team doesn’t handle PDF documents?  Web team is including a lot of video assets?  The best choice for your web team may be to not show them WCAG 2.0 directly.  But know that if claiming conformance that you are still responsible relative to the success criteria directly. 9

10. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Clarify Important Concepts  WCAG 2.0 is about HTML. But not just HTML  Accessibility Support  Conformant does not mean fully accessible 10

11. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Help make sense of the Success Criteria  Which success criteria apply?  Determine what can be ignored for each page or site  Involve the part of your brain that can think like a lawyer  Don’t expect that WCAG will provide specific technical guidance  The Understanding document provides additional informative advice to help interpret the Success Criteria (and Conformance Criteria) 11

12. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Programmatically Determined  1.3.1: Info and Relationships  Keyboard Interface  2.1.2: No Keyboard Trap  Programmatically Determined Link Text  2.4.4 Link Purpose (In Context)  Change of Context  3.2.1: On Focus and 3.2.2: On Input  Labels  3.3.2: Labels or Instructions  Name  4.1.2: Name, Role, Value 12

13. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Programmatically Determined  1.3.1: Info and Relationships  Are current tools able recognize and use information that is present in the code?  Tables, Lists, Headings, quotes, and more.  Technology-specific guidance is easier for web teams to take action  “Make sure that all text or images used to represent a section heading uses HTML heading elements [h1-h6]”  What about role=“heading” aria-level=“2”? 13

14. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Keyboard Interface  2.1.2: No Keyboard Trap  Speaks to a user agent issue  Does an iPhone have a keyboard interface? 14

15. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Programmatically Determined Link Text  2.4.4 Link Purpose (In Context)  User agent support question.  Avoiding the worst “click here” issues.  Can you have many “Read more” links in a list of article titles? 15

16. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Change of Context  3.2.1: On Focus  3.2.2: On Input  Classic issue is an HTML select element which jumps to a different page when the selection is changed. 16

17. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Labels  3.3.2: Labels or Instructions  Label is not always  A well-formed control label can meet 3.3.2 and provide the required name for the control.  The web team can define how they want to handle labels and provide that advice in the style guide. 17

18. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Some terms make Success Criteria confusing  Name  4.1.2: Name, Role, Value  Does this control have a name?  How about this one? 18

19. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. How do we know if we conform?  Conformance Criteria  Special Success Criteria  Techniques  Sufficient Techniques  Failures  Advisory Techniques 19

20. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. How do we know if we conform? 20 Techniques may be helpful in addressing Success Criteria Techniques are not required to conform to Success Criteria (but you need to be able to back up conformance claims)

21. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. We need more help  Community support  IAAP, WebAIM, and WAI Interest Group lists have many generous and knowledgeable people  A11y Slackers group  Encourage question-asking!  Professional help  Many qualified vendors  Accessibility tools get better all the time 21

22. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. Q & A  Thank you!  Contact:  akirkpat@adobe.com akirkpat@adobe.com  Twitter:  @awkawk (personal-ish)  @adobeaccess (accessibility team) 22

23. © 2014 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.