1. Accessibility of UW Information Technology Technology that works for all the ways people access UW services The same code that is best for Stephen Hawking’s assistive software is also best for iPhones!

2. Spot the Barrier

3. What Do We Mean By Accessibility? Sites and services that work with the technology people use Mouse users Mouseless users (keyboard only) Speech output users Speech input users Google Search users (Google Search is blind) PDA, smartphone, and cellphone users

4. Technologies People Use

5. The Need To Be Accessible The Law Americans With Disabilities Act Section 504 of the Rehabilitation Act Washington State Information Services Board Guidelines Section 508 of the Rehabilitation Act – Applies specifically to Federal sites but often used as a standard

6. The Need To Be Accessible University of Washington’s Mission Extend educational opportunities to many who would not otherwise have access to them Seek broad representation of the large and diverse community of which we are a part Educate students for life as global citizens Excellence, community, diversity, and innovation

7. The Need To Be Accessible Control Risk Minimize risk of lawsuits: Don’t be a Target Avoid negative publicity Avoid the high cost of mandated retrofits

8. Opportunity The UW Identity Project gives us an opportunity to address accessibility from the ground up! Templates Guides Training Building a Learning Community Sharing insights Developing methods Connecting with peers at the UW and elsewhere Finding the best resources

9. Designing For Accessibility Key Concepts 1.Getting information to the brain through one or more of the senses (Perceivable) 2.Not everyone uses a standard keyboard and mouse (Operable) 3.Usable not matter which technology is being used (Understandable) 4.Stable through time as technologies change (Robust)

10. Designing For Accessibility The Value of Standards Adhere to standards 1.Well formed 2.Compliant 3.Validated Following standards give technologies (including assistive technologies) something predictable and well structured to interact with

11. Designing For Accessibility The Value of Logical (Semantic) Markup (X)HTML elements are based on the logical model of the parts of a document Headings Paragraphs Lists Tables etc. Adhering to logical markup allows assistive technology to more intelligently present and navigate content

12. Documents are built with a set of logical types of text blocks or elements

13. (X)HTML is a language based on those same semantic element types

14. Designing For Accessibility Separating Content from Presentation 1.Put content in (X)HTML 2.Control presentation with CSS 3.Define behaviors with standards compliant scripting that operates on the (X)HTML elements Trying to control presentation in the (X)HTML, such as by using tables for layout, greatly complicates interpretation of the content by assistive technologies.

15. Strict separation of content and presentation greatly simplifies your content and makes content more coherent for non-visual access

16. Designing for Accessibility Alternative Text Provide alternative text for non-text content Gerberding Hall

17. Labelling Input Fields Which text applies to which input field?

18. Labelling Example First Name <input type="text" name="firstname" id="fname" /> Last Name <input type="text" name="lastname" id="lname" />

19. Designing For Accessibility Navigation Meaningful page title Meaningful menu items Meaningful headings o Use of headings for topic (H1), subtopic (H2), subsubtopic (H3), etc. Skip to Content links allowing bypass of menus Not dependent on one technology or access method o Menus in good structured (X)HTML o Usable without the mouse (not dependent on mouseovers) Scripting fully standards compliant

20. Designing For Accessibility Working With Contract Designers and Coders Assessing accessibility skills of candidate contractors o Knowledge of standards compliant methods o Knowledge of Section 508 standards o Knowledge of variety of ways pages are accessed, including with assistive technologies Contracts include statement of accessibility requirements o Testable compliance as a requirement of contract completion Understanding Web display or graphics o Relative sizes, scalability o Size and resolution of screens

21. Designing For Accessibility Sample Language NOTICE -- All electronic and information technology (EIT) procured through this RFP must meet the applicable accessibility standards of 36 CFR 1194. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at the following URL: http://www.section508.gov The following Section 508 technical standards are applicable to this RFP, as a minimum: " Software Applications and Operating Systems (1194.21)" Web-based Intranet and Internet Information and Applications (1194.22) " Video or Multimedia Products (1194.24) C.4 Applicants must state their level of compliance to applicable sections to be considered for purchase under this RFP. From Utah State University Center for Persons With Disabilities

22. Designing For Accessibility Responsibility o Adding accessibility after delivery is expensive and difficult o You are responsible for what your contractors do

23. Content Management Systems What counts is what gets to the browser CMS systems internally store, handle, and present content in many ways Different modules/web parts/widgets write code for different parts of the page. Ensuring that the net result is standards compliant and accessible can get complicated The Master Pages (basic page templates) often determine how accessible a site is.

24. Content Management System Widgets, Web Parts, Modules Master Page Site Management Wizard/Interface Contents Database A simple diagram of a CMS

25. Content Management Systems A typical CMS Web site

26. Content Management Systems The site uses tables layout nested ten tables deep on every page! However, this is a problem with the Master Page design, not the CMS.

27. Content Management Systems The same CMS (SharePoint) using an XHTML/CSS Master Page (no layout tables)

28. Content Management Systems Once you get a CMS, be careful not to disable its accessibility features Query the CMS community about accessibility of any product you are considering o CMS Watch CMS Watch

29. Procuring Accessible IT Request accessibility information from vendors Query accessible technology community for comment on products you are considering o Accessibility Working Group (AccessibleWeb@U) o University Web Developers (http://cuwebd.ning.com) Review product Voluntary Product Accessibility Template (VPAT) Conduct usability and accessibility tests o Can you use it without a mouse? o Access it with a voice browser (WebAnywhere) o Check for tables o Turn off the CSS and see what happens o Request an evaluation by the Access Technology LabAccess Technology Lab

30. Cloud Services When a cloud service is required for faculty, staff or students, pay attention to accessibility Cloud services are getting very good o Using them is becoming more practical, justifiable Constantly evolving, competitive o Accessibility not necessarily a high priority o Often accessibility improved later o Need to constantly keep evaluating services to be sure they meet your requirements Pay attention to process o Only inaccessible step in a process means the whole process is a problem for asssistive technology users.

31. In Conclusion We care about people Our mission is to enable and empower learning, knowledge creation, and service Standards enable interaction among devices and among people Standards give leverage, power

32. Where Do We Go From Here Open Discussion Raising awareness Education Tools and Resources Policy Top-level institutional support Community and culture