eLATED Accessibility and eLearning

1. eLATEDAccessibilityand eLearning Monica Ackermann, P.Eng. MA Scotiabank November 2, 2010

2. Enabling Solutions and Support Management Governance Training Government Industry Tools ESSM Customer AT – IT Solutions IT Accessibility Job Accommodation Support

3. Regulatory Factors – Accessibility in Canada 3 Accessibility for Ontarians with Disabilities Act (AODA 2005) • Ontario is the first jurisdiction in Canada to develop province-wide, enforceable accessibility standards. Human rights legislation exists in all provinces and federally. • End goal = a fully inclusive Ontario by the year 2025 • Fully enabled participation in society and economy • Removal of barriers to participation • There are 360,000 “obligated organizations” in the province that come under the regulations, approximately 4 to 5 million employees in the province are covered. • Public sector – municipal, regional, provincial governments, schools, colleges, universities, hospitals, agencies • Private sector – Ontario businesses that provide goods or services to people in Ontario Federal Policy: Canadian Government Ratifies the UN Convention on the Rights of Persons with Disabilities – March 11, 2010

4. Accessibility Standards There are 5 sets of standards under the AODA • Customer Service • In force as of 2008 – phased in and fully effective by Dec. 2011 • Affects the public sector as of January 1, 2010. • Information and Communication • Web, print, oral communication must meet accessibility standards • Internal and external I/T systems • Employment • Address barriers to employment for People with Disabilities • Transportation • Transit, buses, etc • Built Environment • Building codes

5. Proposed Timelines 2013: • Ontario Government; Net new sites WCAG 2.0 Level A • Educational Institutions & Public Libraries; accessible materials and training 2014: • Ontario Government; Accessible Formats & Communication Supports • Public Sector (50+); Net new sites WCAG 2.0 Level A • Private and Not-for-profit (50+); Net new sites WCAG 2.0 Level A 2018 - 2025: • Internet and Intranet* websites and web content conforms with WCAG level AA (including live captioning and audio description) • Educational libraries – multi-media / digital resources * Ontario Government

6. Perceivable • 1.1 Text alternative • 1.2 Time-based media • 1.3 Adaptable • 1.4 Distinguishable • Understandable • 3.1 Readable • 3.2 Predictable • 3.3 Input Assistance • Operable • 2.1 Keyboard Accessible • 2.2 Enough time • 2.3 Seizures • 2.4 Navigable • Robust • 4.1 Compatible WCAG 2.0: 4 Principles POUR12 Guidelines65 Success Criteria

7. KEY ACCESSIBILITY ISSUES • Images • Keyboard Access • Page Structure • Navigation • Forms • Universal design

8. Images All Images must have alt-text: • Ensure that the text alternatives communicate the purpose of the graphic accurately and succinctly. • Provide empty or null alt text for graphics which do not convey content. <img src=“scotialogo1.jpg" alt=“Scotiabank Logo" /> Misconception: Accessible sites are unattractive and cannot use images

9. Keyboard Accessible: Make all functionality available from a keyboard. Rollovers Use both keyboard and other device-specific functions.

10. Keyboard Accessible • No Keyboard Trap • Make JavaScript actions keyboard accessible. • The keyboard tab key must be able to be used to "stop" at the element and then activate it by pressing the Enter key.

11. Keyboard Accessible User must be able to access each element on the page in a logical and understandable way using the keyboard. Billing Address Shipping Address

12. Page Structure • Use <h1> - <h6> to identify headings. • Use ol, ul and dl for lists. • Use the <strong> element to provide visual emphasis • Use CSS for offscreen text for additional structure

13. NavigableProvide ways to help users navigate, find content, and determine where they are. • Provide a method to Skip Navigation and get to main content areas • Provide a descriptive and informative page title • Link Purpose (more …, Click Here..)

14. Forms Each form field must have a label that is more than visual. It must be structural HTML markup: <label for="name">Name:</label><input id="name" type="text" name="textfield" /> Notice the for and id values are the same, thus associating the label with the appropriate form element. Each id on a page must be unique.

15. Universal Design • Understand and respect learner’s unique abilities and experiences • Balance standardization with personalization of experience • Branding, marketing, support

16. Tips and Opportunities for the eLearning Community • Some authoring tools have accessibility checks built-in. • Ensure that your multimedia content is accessible. (e.g. accessible structure, framework, captioning) • Business will be including accessibility requirements into RFP’s • New opportunities for creating training to meet requirements under the AODA. Accessible content about accessibility requirements.

17. Accessibility Demo Before and After http://www.w3.org/WAI/demos/bad/Overview.html

18. Resources • ESSM Team, Scotiabank enablingsolutions@scotiabank.com • WCAG guidelines version 2.0 www.W3C.org/wai • IBM Human Ability and Accessibility Centre www.ibm.com/able • WebAIM www.webaim.org • AODA Standards www.accesson.ca • Sample Accessible Sites http://www.w3.org/WAI/demos/bad/draft/2009/after/home/

19. THANK YOU