Integrate Accessibility Management

1. Integrate Accessibility Management "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect." -- Tim Berners-Lee, World Wide Web Consortium (W3C) Director and inventor of the World Wide Web

2. Welcome! Where to begin with institutional accessibility Identify stakeholders Motivate Build capacity Test Integrate Sharron Rush srush@knowbility.org

3. Accessible People with disabilities …can acquire the same information …participate in the same activities …be active producers as well as consumers

4. Universal Design… • supports all people • supports all technology • improves experience for all • strong relationship to usability • “Good design IS accessible design” ~ Dr. John Slatin

5. You’re the accidental expert …now what?

6. Steps to IT accessibility • Listen to your stakeholders • Enlist executive sponsor • Where are we going? • Choose/define standard • Policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Test, measure, report • Inclusive practice becomes integral

7. …yes all of them • Survey customers, clients, students, citizens depending on your type of org • Collect data from staff, all departments • What are they afraid of? • What myths are they holding on to? • Listening can be magical

8. Steps to IT accessibility • Listen to your stakeholders • Enlist executive sponsor • Where are we going? • Choose/define standard • Policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Tesst, measure, report • Inclusive practice becomes integral

9. Executive Leadership is critical

10. With the proper leadership, your journey will be easier

11. Steps to IT accessibility • Listen to your stakeholders • Recruit executive sponsor • Where are we going? • Choose/define standard • Adopt explicit policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Test, measure, report • Inclusive practice becomes integral

12. Role of Standards • Shared understanding of requirements among: • Consumers • Authoring Toolmakers • Developers • Makers of browsers and AT devices • “How to” Techniques and testing criteria for content creators

13. Components of Web Accessibility ATAG(authoring tools) Diagram of the relationship between authoring and evaluation tools, Web content, and user agent tools such as browsers and assistive technologies. As each component adheres to common standards, accessibility and interoperability are improved. At the W3c, groups of experts work in collaboration on the ATAG – authoring tools accessibility group; WCAG – web content accessibility group; and UAAG – user agent accessibility group, and others. WCAG(web content) UAAG(user agent)

14. Global Standards • WCAG - Web Content Accessibility Guidelines. International standards for the web • ATAG - Authoring Tool Accessibility Guidelines. Vendor standards for interoperability • UAAG - User Accessibility Guidelines for browsers and assistive technologies • ARIA - Accessible Rich Internet Application research for emerging technologies www.w3.org/WAI

15. Section 508 Guidelines • Only used in US • Subpart B - technical standards • 16 rules of web-based intranet and internet accessibility standards • In process of “Refresh” www.section508.gov

16. Standards are being revised • Section 508 in “refresh” (expect to harmonize with WCAG 2.0) • WCAG 2.0 released in December 2008 – accessibility defined within 4 basic principles. 508 WCAG

17. Section 508 to WCAG2 Map • Created by Tom Jewett and Wayne Dick for CSUN 2009 http://www.tomjewett.com/accessibility/508-WCAG2.html

18. Four principles of accessibility POUR • Content is Perceivable • …is Operable • …is Understandable • …is Robust

19. POUR Principles are widely applicable • Documents • Web pages • Web applications • Content management

20. Policy Development • Who is policy being developed for and why. • Identify stakeholders and their various needs, requirements, possible barriers to adoption • Define scope – will policy apply to web sites? purchases? other software? hardware? • Choose an existing guideline or standard • Make the conformance level explicit • Involve stakeholders to every extent possible

21. Policy Implementation Create an accessibility work plan • Set milestones • Provide training • Create enforcement mechanisms • Include in specifications, requirements • Define monitoring, conformance claims, and follow-up process • Provide for integration (for example within purchasing process) • Create review dates and procedure for policy revision

22. Developing and implementing policy http://www.un.org/disabilities/default.asp?id=1516 GENERAL Guidelines from the United Nations Enable Summit http://architecture.hhsc.state.tx.us/myweb/Accessibility/policy_htm/default.htm Fully developed, applied policy at Texas HHSC

23. Steps to IT accessibility • Listen to your stakeholders • Recruit executive sponsor • Where are we going? • Choose/define standard • Policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Test, measure, report • Inclusive practice becomes integral

24. Initial Assessment • What kind of entity? • Policy alignment • Set base line

25. Manual Review • Establish typical user pathways • Test broad cross-section • Test for standards conformance • Include experience of users with disabilities • Maintain detailed documentation

26. We test so we don’t do this to our users • Cartoon of woman at computer with finger on mouse clicker. The screen says Repetitive Stress Injury – click here 100 times to enter

27. Enterprise testing tools • Automated, large scale testing and reporting • Manage progress across enterprise • Multiple report formats, trend analysis • Remediation prioritization • Track multiple divisions, departments • Monitor over time

28. Steps to IT accessibility • Listen to your stakeholders • Recruit executive sponsor • Where are we going? • Choose/define standard • Adopt explicit policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Test, measure, report • Inclusive practice becomes integral

29. Why advocate for inclusive design? Legal Technical Market Humanitarian Visionary

30. Find and empower champions Image of 9-year old girl in home-made super girl costume, arms crossed, goggles on, looking determined!

31. Build game plan • Accessibility is not a solo act • Accessibility Responsibility Breakdown

32. Steps to IT accessibility • Listen to your stakeholders • Recruit executive sponsor • Where are we going? • Choose/define standard • Adopt explicit policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Test, measure, report • Inclusive practice becomes integral

33. Role specific training • Administrators • Designers • Developers • Content Providers • Procurement staff • QA team

34. Maintain training resources • Online training • Best practice guides • Repository of experiences, tools, templates, processes

35. Steps to IT accessibility • Listen to your stakeholders • Recruit executive sponsor • Where are we going? • Choose/define standard • Adopt explicit policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Test, measure, report • Inclusive practice becomes integral

36. Establish coordination and communication plan • Identify representatives from key departments and regions • Designate a team member to track new developments in accessibility practice • Map responsibilities to various roles within organization

37. Integrated support • Published policy/standards/exceptions • Widget libraries w/accessibility built in • CMS prompts for accessibility • Report templates, iterative validation • Procurement checklists • Sample RFP language • VPAT verification guide • Repository of role-based resources • Departmental competitions

38. WCAG2 Trading Cards from Knowbility

39. Steps to IT accessibility • Listen to your stakeholders • Recruit executive sponsor • Where are we going? • Choose/define standard • Adopt explicit policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Test, measure, report • Inclusive practice becomes integral

40. Create testing template Choose a standard explicitly • Section 508 • WCAG 2 • Conformance Level A • Conformance Level AA • Conformance Level AAA • Other …reflect in procedures and materials

41. Create reporting template Knowbilitystandard form Reporting template examples and on BAD demo report Customized by request www.w3.org/WAI/eval/template.html www.w3.org/WAI/demos/bad/before/reports/home.html

42. Automated one-page tests • ACheckerhttp://achecker.ca/checker/index.php • The Wave http://wave.webaim.org/ Results emailed to you by • AMP Expresshttps://amp.ssbbartgroup.com/express

43. Manual reviewperformed throughout design, development, QA

44. User testing • If usability is part of your process, include users with various disabilities • Post to user groups • User testing through AccessWorks Remote Accessibility Testing Portal http://tinyurl.com/accessworks

45. Steps to IT accessibility • Listen to your stakeholders • Recruit executive sponsor • Where are we going? • Choose/define standard • Adopt explicit policy • Where are we now? • Build and integrate teams • Train to win • Integrate support structures • Test, measure, report • Inclusive practice becomes integral

46. Accessibility is a process that must be woven into all IT practices from inception: included in design, development, and QA through management and procurement

47. Thank you You make all the difference! srush@knowbility.org @knowbility on Twitter www.facebook.com/knowbility