MISA AODA Working Group: Accessibility Toolkit and User Testing. Logan Trafford (City of Ottawa) Elaine Decleir (esolutionsgroup)

Transcription

1 MISA AODA Working Group: Accessibility Toolkit and User Testing Logan Trafford (City of Ottawa) Elaine Decleir (esolutionsgroup) June 10, 2014

2 Identifying a Need

3 Problem How to tackle all the issues related to accessibility with limited resources available including software, people.

4 MISA Toolkit Contributors In recognition and with thanks to

5 Major Partner

6 MISA AODA Working Group Provide information on accessibility best practices and case studies to MISA membership Provide a forum for collaboration among MISA members focused on accessibility Identify opportunities for securing grants and/or cofunding for MISA Ontario activities. Communicate the activities of the SIG throughout MISA Ontario membership and encourage participation in the SIG

7 Toolkit Approach 1. Subcommittee Meeting 2. Divide into smaller groups to work on specific documents 3. Subcommittee Meeting 4. Provide opportunity for members of the subcommittee to review documents

8 Guiding the Way

9 The Goal This toolkit aims to help municipalities throughout Ontario to create accessible web content beyond the Accessibility for Ontarians with Disabilities Act (AODA).

10 General Best Practices Headings Images Links Tables Colour Contrast Font and Font Size

11 The Guts..

12 MS Word

13 Adding a Document Title Under S.C (Level A) Web pages/documents have titles that describe topic and purpose

14 Major Difference of 7 vs. 10 MS Word 2010 has a built-in A11Y checker. Check does NOT guarantee compliance but can be used as a starting point.

15 Adobe Acrobat

16 Touch Up Reading Order

17 MS Excel

18 Worksheet Names All worksheets in an Excel Document require a UNIQUE and descriptive name

19 Accessible Forms

20 PDF form input fields require tooltips Adding Tooltips

21 InDesign

22 Tag all images Add appropriate alt text to all images or tag them as artifacts

23 Other Documents

24 Not limited to creating electronic documents Beyond Documents

25 Resources Colour Contrast Checkers Free Screen Readers to test your pages Conferences Much More

26 Real Life Scenarios

27 Working with the Community

28 User Testing & Assistive Technologies

29 Compliancy vs. Optimization

30 User Testing Strategies The purpose of user testing is to evaluate website accessibility through the observation of the use of assistive technologies by visually impaired participants. We will use the results of this evaluation to refine our approach to website design and development to ensure that we are doing our part to create an open, usable web. esolutions strives to create web applications that are designed with the full range of human diversity in mind.

31 User A Profile: Assistive Technology: Jaws Approximate hours a day on a computer: 5-6 hours Activities: browse the web, Preferred Browser: Internet Explorer (90% of the time) Comfort Level: Advanced

32 User B Profile: Assistive Technology: ZoomText Approximate hours a day on a computer: 1-2 hours Activities: Facebook, browse the internet Preferred Browser: Internet Explorer Comfort Level: Beginner

33 User C Profile: Assistive Technology: Jaws Approximate hours a day on a computer: 3-4 hours Activities: Calendar, Brose the Internet Preferred Browser: Internet Explorer Comfort Level: Beginner Intermediate

34 Using Symbols

35 Alt text not quite right

36 Search

37 Do What Makes Sense

38 Heading Structure

39 Compliant but not necessarily Accessible

40 Optimization

41 Skip to Content

42 Bypass Blocks

43 Document Accessibility

44 What s Next?

45 Moving Forward Subcommittee continues to meet on a quarterly basis Create new supporting documents MS PowerPoint Auditing and Testing methods Templates

46 Anticipate Future Needs Continue to raise awareness and knowledge Educate vendors / consultants Discuss potential issues Compliance Reporting / Auditing Governance