Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Demystifying Accessibility Testing

1,034 views

Published on

Everyone wants their election systems be usable and accessible. This is especially true for systems like online voter registration, polling place lookup apps, ballot delivery systems, and poll books — all the systems not covered by the VVSG. This presentation will discuss how to conduct accessibility testing in stages, starting with a simple inspection and ending with usability testing by voters with disabilities.

Presented at the 2015 Conference on State Certification of Voting Systems

Published in: Design
  • Login to see the comments

Demystifying Accessibility Testing

  1. 1. Demystifying Accessibility Testing Whitney Quesenbery Center for Civic Design @civicdesign | @whitneyq State Certification Conference May 19-20, 2015, Seattle
  2. 2. Why accessibility testing seems hard Invisible Hidden Misunderstood
  3. 3. Usability and accessibility Twins separated at birth
  4. 4. Elections are more than voting systems Elections information Online voter registration Polling place lookup Sample ballots Ballot tracking And...
  5. 5. The POUR Principles Perceivable Operable Understandable Robust
  6. 6. Accessibility testing in layers Principle Testing mode What it tests Perceivable Inspection Basic accessibility errors Robust Code review Use of code standards Semantic structure Operable Check AT Expert review Interaction using keyboard, screen reader, other AT Operable/ Understandable Usability testing Use by real people
  7. 7. Inspection Check for basic accessibility errors Quick checks that are perceivable without special technology  Image "alt" text  Text size and contrast  Captions and transcripts  Meaningful links and buttons  Easy access to content (skip links)  Keyboard navigation
  8. 8. Code review Check for accessible coding Look for robust code that meets standards.  Forms coding  Semantic markup for content structure  Reading order with a keyboard  Coded to W3C standards  Appropriate use of ARIA and HTML5 elements
  9. 9. Use Check with assistive technology Check that it is operable and understandable with assistive technology. Use the technology with  Screen readers: NVDA, VoiceOver or JAWS  Magnifiers: Browser magnification and ZoomText  Keyboard: Emulators, dual switches, Braille notes
  10. 10. Expert review Check with expert AT users Expert review by people who use assistive technology to be sure it is operable and understandable.  Does it work well with a range of AT?  Are there good cues for navigation and orientation through the task?  Can they complete all basic tasks, from the start to finish?
  11. 11. Usability testing Check with voters with disabilities Test again with a diverse set of "regular voters" to be sure it works for non- experts.  Can they complete all basic tasks, from the start to finish?  Does it work with their own AT, with their usual settings?  Are there good cues for navigation and orientation through the task?
  12. 12. Summing up Test in layers  Inspection  Code inspection  Use with assistive technology  Expert review  Usability testing Test entire tasks  Can they be completed from start to finish Test every template  For informational sites, test every feature or template
  13. 13. Designing accessible election websites and applications 1. Make sure information about accessible voting is easy to find 2. Code forms so they are accessible 3. Allow users to change text size and appearance 4. Structure the content with headings 5. Write specific, meaningful links 6. Make it easy to jump to the main content on the page 7. Provide alternative descriptions for images, audio, and video 8. Keep alternative formats together, so voters can choose 9. Make sure everything works with a keyboard 10. Test the site with voters with disabilities Coming soon
  14. 14. Get in touch! Whitney Quesenbery whitneyq@civicdesign.org @whitneyq civicdesign.org @civicdesign

×