1. How to evaluate technology for accessibility Terrill Thompson Technology Accessibility Specialist University of Washington tft@uw.edu @terrillthompson http://uw.edu/accessibility

2. What is "accessible technology"?

3. Can I access it without seeing it?

4. Can I access it without a mouse?

5. Can I access it without sound?

6. Accessible technology standards

7. Web Content Accessibility Guidelines (WCAG) WCAG 1.0 published in 1999 WCAG 2.0 published in 2008

8. WCAG 2.0 Four principles: –Perceivable –Operable –Understandable –Robust 62 specific success criteria –Level A — 26 success criteria –Level AA — 13 success criteria –Level A — 23 success criteria

9. Example WCAG 2.0 Success Criteria at Level A/AA Alt text on images Captions on videos Color not the sole means of communicating information Proper heading structure Labels on form fields Visible indication of keyboard focus

10. Section 508 Standards (2000) Technical Standards –Software and operating systems –Web content and applications (based on WCAG 1.0 Priority 1 checkpoints) –Telecommunications products –Video and multimedia products –Self contained, closed products –Desktop and portable computers Functional Performance Criteria

11. WCAG 2.0 Level AA as the de facto standard Many higher education policies Many resolution agreements and legal settlements Many international accessibility laws DOJ proposed new rules for the ADA regarding web accessibility –Public comment period ended in 2011 508 standards refresh –Latest draft published February 2015

12. ARIA "Accessible Rich Internet Applications" Communicates roles, states, and properties of interface elements to accessibility APIs, for the benefit of AT users. Answers questions like: –What is this? –How do I use it? –Is it on/selected/expanded/collapsed? –What just happened? The email you entered is not valid. Please try again.

13. role="tree" role="treeitem" aria-hidden="true" aria-expanded="false" aria-controls="id-of- submenu" etc. ARIA Example

14. Is Product X accessible? How do we know?

15. Three Steps 1.Ask questions about the product's accessibility 2.Ask your peers about the product's accessibility 3.Test the product, and share your findings!

16. Ask about the product's accessibility

17. Who to ask The person/group making the purchasing decision The vendor

18. What to ask Is it accessible? Can users perform all functions without a mouse? Has it been tested using assistive technologies? If so, which AT? What was your method? What were your findings? Who did the testing? If it supports audio, does it support captions? If it produces output, is the output accessible? Is accessibility documentation available?

19. Sources of Information from Vendor Voluntary Product Accessibility Template (VPAT) Accessibility information on website Product user forums (search for "accessibility" or "disabilities") – Note users' reported issues – Note vendors' response to these issues

20. Example: Vendor's Accessibility Web Page Company X is committed to making its tools accessible for all users, including people with disabilities. Our tools comply with Federal Section 508 guidelines, Bobby, and W3C WCAG recommendations.

21. Example VPATs Canvas LMS: http://www.canvaslms.com/accessibility http://www.canvaslms.com/accessibility Adobe Captivate: http://www.adobe.com/accessibility/compliance/adobe- captivate-5-section-508-vpat.html http://www.adobe.com/accessibility/compliance/adobe- captivate-5-section-508-vpat.html TechSmith (Camtasia) Relay: https://www.techsmith.com/accessibility.html https://www.techsmith.com/accessibility.html Some bad examples: http://www.karlgroves.com/2011/07/07/why-a-third-party- should-prepare-your-vpatgpat/ http://www.karlgroves.com/2011/07/07/why-a-third-party- should-prepare-your-vpatgpat/

22. Ask your peers about the product's accessibility

23. Where the IT Accessibility People Are ATHEN http://athenpro.org http://athenpro.org EDUCAUSE IT Accessibility Constituent Group http://educause.edu/groups/itaccess http://educause.edu/groups/itaccess WebAIM Email Discussion List http://webaim.org/discussion http://webaim.org/discussion Accessing Higher Ground Conference http://accessinghigherground.org http://accessinghigherground.org

24. Test the product and share your findings!

25. Take the #nomouse challenge! nomouse.org

26. How to approach product testing Define functions/workflows to test Can you perform all functions? – With keyboard alone – With a screen reader – With screen magnification / large fonts / high contrast – With speech input Recruit users to help with testing – Understand that users have varying skill levels

27. Tools can help, but they don't tell the whole story WAVE http://wave.webaim.org http://wave.webaim.org Functional Accessibility Evaluator (FAE) http://fae20.cita.illinois.edu http://fae20.cita.illinois.edu Various browser toolbars & plugins http://www.washington.edu/accessibility/web /tools-and-resources/ http://www.washington.edu/accessibility/web /tools-and-resources/

28. Overwhelmed? Don't be.

29. Everyone, in descending order by how much they should know about web accessibility Web/IT accessibility specialists Web/IT developers Web/IT managers, administrators Support staff for content authors Content authors Everyone else

30. Everyone needs to know That users are incredibly diverse The sorts of questions to ask Where to turn for help

31. Overall Strategy Talk to vendors about accessibility Request VPATs, but review them critically Include accessibility requirements in RFPs Develop a procedure for evaluating products for accessibility Include accessibility requirements in contracts Participate in collaborative efforts with other institutions (e.g., through ATHEN)

32. Accessible Technology Resources UW Accessible Technology http://uw.edu/accessibility http://uw.edu/accessibility AccessComputing http://uw.edu/accesscomputing http://uw.edu/accesscomputing The DO-IT Center http://uw.edu/doit http://uw.edu/doit