1 / 54

Quick Ways to Test for Accessibility … Without Doing It All by Yourself

Quick Ways to Test for Accessibility … Without Doing It All by Yourself. Angela M. Hooker # QuickA11yTesting @ AccessForAll # AHG13 angela hooker.com. Hello !. Angela Hooker @ AccessForAll # QuickA11yTesting | # AHG13. So, what’s up? ….

emele
Download Presentation

Quick Ways to Test for Accessibility … Without Doing It All by Yourself

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Quick Ways to Test for Accessibility … Without Doing It All by Yourself Angela M. Hooker #QuickA11yTesting @AccessForAll #AHG13 angelahooker.com

  2. Hello! Angela Hooker @AccessForAll #QuickA11yTesting| #AHG13 #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  3. So, what’s up? … #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  4. Plan and prioritize #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  5. What are you testing? #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 A video gallery? A site? Is it responsive? A page? A mobile app? Is it for an official review or just a quick check for potential problems?

  6. How much time do you have? #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  7. Prioritizeagain #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Do you only have to test or are you responsible for remediating the problems? Do you need to tell people how to fix the problems?

  8. Use checklists and other resources #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 • Create or find a checklist for your specific needs: • 25 Ways to Make Your Website Accessible (check for the items listed), by Dennis Lembree • Accessibility Quick Check, Tom Jewett • WCAG 2.0 Checklist, WebAIM • Video and Audio Accessibility Checklist • Course Accessibility Checklist • Mobile: In “Resources” section in this document

  9. Gethelp … for now #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 • Colleagues (we’ll discuss them more later) • Students • Volunteers • Survey (depends on time)

  10. After you test … #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Think about what tools you like best—what appeals to me may not appeal to you.

  11. How about a quick test now? #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 • Just for a few minutes, let’s see what we accessibility problems we can find on a popular site. • I’m going to use a few tools that I like: • WAVE Toolbar • Web Developer Toolbar, by Chris Pederick • Juicy Studio Accessibility Toolbar • Paciello Group Web Accessibility Toolbar • No assistive technologies (?!)

  12. Accessibility remix! #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  13. Consideranother perspective and approach… #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  14. Consideranother perspective and approach… create an accessibility team from peopleyou alreadyhave on staff. #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  15. Share the workbased onrolesinstead of correctingyour colleagues’ work. #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  16. This makes your entire teamresponsibleand accountable for their own work. #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  17. Talkwith management.(See Carol Smith’s Negotiate for the User.) #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  18. Canadian Government’s resources • Accessibility Responsibility Breakdown • Canadian Government • Based on WCAG 2.0 • CoopérativeAccessibilitéWeb #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  19. 4 keysto building in accessibility #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  20. Understanddisabilities #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  21. Train your colleaguesaccording to each of their roles. #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  22. Teachthem … #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 … that we need to test and plan for accessibility throughout each project's lifecycle. ... how to choose technology that's accessible. ... the importance of accessible platforms. ... to not just do what the cool kids are doing for the sake of doing it. … development principles (good, clean, accessible code).

  23. Teachthem … #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 ... accessible design principles. ... how people who have low-English proficiency, dyslexia, cognitive impairments, etc. need plain language and other principles. … that we need to conduct usability testing with people with disabilities. … how people with disabilities use their assistive technologies—and that successfully using one assistive technology on a project doesn't mean blanket accessibility.

  24. Divvy up thestandards #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  25. Give them tools. #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  26. The roles overlap. #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  27. Create a policy #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 • Write an in-house policy (not an accessibility statement for the public). • Developing Organizational Policies on Web Accessibility, W3C-WAI • Get management support to make it stick.

  28. It won’tall happen overnight. #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  29. What doesn’t work #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Putting the work before relationships Disinterest from upper management Thinking our process won’t evolve Allowing the accessibility program to be personality driven—it must outlive you

  30. What you’ll gain #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Save money by not making costly accessibility fixes later. You’ll have a solid process that fights the “accessibility is time consuming and expensive” issues. You’ll have a fluid process—stands despite staff changes, work demands, etc.

  31. Now, back to you… #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  32. Keep calm and test quickly #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  33. Thank you! Angela Hooker @AccessForAll SlideShare ange@angelahooker.com angelahooker.com #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  34. Resources #QuickA11yTesting | #A11y | @AccessForAll | #AHG13

  35. Sampleprocess #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Tailor this to your needs and to each project. Document this entire process and testing. Choose who should work on the project, and assign tasks/roles to everyone according to their skills and strengths. Plan/gather requirements with the decision makers, stakeholders, designers, developers, content providers, etc.

  36. Sample process #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Determine which standards and guidelines are appropriate for your project (WCAG 2.0, Mobile Best Practices, ATAG, CVAA, iOS Accessibility Standards, etc.). Put accessibility requirements in any vendor requests for proposals and/or contracts. Determine your users’ top tasks.

  37. Sample process #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Review the information architecture. Analyze the resulting wireframes. Conduct usability testing withpaper prototypes (wireframes). Choose and test the color scheme. Assess the design mockups. Review the final written content.

  38. Sample process #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 • Conduct more informal user testing (test the mockups, content, information architecture). • Review the templates (including ARIA); validate/remediate the (semantic) code. • Just because your code validates doesn’t mean your project is accessible—validate anyway! • Just because your site doesn’t validate doesn’t mean it’s inaccessible—validate anyway!

  39. Sample process #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Review the style sheets; validate/remediate the styles. Test with automated accessibility tools. Review the scripting (JavaScript, AJAX, jQuery, YUI, whatever); add more ARIA, if needed. Test again with automated tools.

  40. Sampleprocess #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Test with assistive technologies. Test on mobile devices and e-readers. Test with real people, including several people with different disability types—don’t forget to test the written content, too. Continue to improve and test after the launch (since browsers and software change).

  41. WCAG 2.0 and general *a11y #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Government of Canada Web Experience Toolkit (WET)—above all else, see the Accessibility Responsibilities Breakdown; it will help you create your process and define roles. Constructing a POUR Website, WebAIM BBC’s Future Media Standards and Guidelines A11y Buzz * accessibility

  42. Mobile #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Mobile Accessibility Guidelines, BBC Mobile Accessibility Tests, HennySwan iOS Accessibility – A Useful Guide For Testing, Rosie Sherry Setting Up iOS and Android for Accessibility Testing, Kathy Wahlbin Why Mobile Accessibility Matters: Best Practices to Make Your Mobile Site Accessible, mobiForge

  43. Disabilities #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 • Disability types/issues • Visual, cognitive, motor, and hearing impairments; neurological/seizure disorders; elderly and aging • What Is Assistive Technology? – ATIA • Videos of people using assistive technologies, from AssistiveWare • How Assistive Technology Works (demonstrations), University of Dundee

  44. Project management #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Integrating Accessibility in the Organization’s Web Development Life Cycle, Denis Boudreau Accessibility for Project Managers, Henny Swan Managing Accessibility Compliance in the Enterprise, Karl Groves Plan for Accessibility, Option Keys

  45. Project management #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Planning Accessibility, Government of Canada Just Ask: Integrating Accessibility Throughout Design, Shawn Lawton Henry

  46. Writing content #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Accessibility for Web Writers, by 4 Syllables Content and Usability: Web Writing, Web Credible Make it Plain: Accessibility and Usability Through Plain Language, Angela Hooker (hey!) Plain Language: Accessibility for Information, Whitney Quesenbery Plain Language Checklist, PlainLanguage.gov

  47. Design #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 • Web Accessibility for Designers, WebAIM • Just Ask: Integrating Accessibility Throughout Design, Shawn Lawton Henry • Design Considerations, WebAIM • Color Contrast Checker, WebAIM • Accessibility Color Wheel • Trace Photosensitive Epilepsy Analysis Tool (PEAT) – tests flashing content

  48. Development #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Web Accessibility for Developers (videos), BBC Build a code library! Use code generators (see Accessify’s tools). Web Developer Toolbar, Chris Pederick Firebug, Mozilla WCAG 2.0 Checklist, WebAIM Web Accessibility Gone Wild, WebAIM

  49. Development #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 W3C Mobile Web Best Practices Juicy Studio Accessibility Toolbar —for ARIA, data tables, color contrast aChecker, Inclusive Design Institute at OCAD University WAVE Toolbar, WebAIM Favelets for Checking Web Accessibility, Jim Thatcher

  50. Quality assurance #QuickA11yTesting | #A11y | @AccessForAll | #AHG13 Template for Accessibility Evaluation Reports, W3C-WAI Accessibility Evaluation Resources, W3C-Web Accessibility Initiative Evaluation, Testing, and Tools, WebAIM WCAG 2.0 Checklist, WebAIM Wickline Color Blind Web Page Filter Web Developer Toolbar, Chris Pederick

More Related