Do you and your team know how to test for accessibility? These slides are from a recent workshop we were invited to present at #A11yTO's recent Meetup. It covers learnings from conducting accessibility testing with users, as well as some tools and tips for automated testing.
Discover some of principles and design considerations geared toward making web experiences accessible, and how to conduct an accessibility focused usability test.
3. • Types of impairments and assistive technologies
• How to test for accessibility with automated and manual
accessibility evaluation tools
• Preparing to test with users
• How to test for accessibility with real users
• Usability testing vs. accessibility testing
What you’re going to learn
3
4. Types of impairments that can impact how
people use your website
4
Visual impairments Auditory impairments
Mobility impairments Cognitive impairments
5. Overview of Assistive Technology
• Screen readers (JAWS, NVDA,
VoiceOver, TalkBack)
5
Image credit: http://westernblind.blogspot.ca/
2011/06/cat-skills-zoomtext.html
• Screen magnification (ZoomText,
through the browser)
• Speech recognition (Dragon
NaturallySpeaking)
• Eye-tracking, dynamic braille
display, alternative keyboard,
oversized trackball mouse, etc.
6. Making sure the product is accessible
• Need to make sure what we design and build works for people
with impairments and people using assistive technology
• The way we do that is through testing:
- automated testing
- manual testing
- testing with users
6
7. What to test with
• Can’t be low fidelity/paper prototype
• Must be compatible with assistive technology
7
8. Ensuring test artifact is ready
• Don’t want to waste time
• Code to WCAG 2.0 standards
• Manual and automated accessibility evaluation tools
• Test it yourself
8
9. HTML CodeSniffer
• Browser extension
• Cut and paste code
9
http://squizlabs.github.io/HTML_CodeSniffer/
10. HTML CodeSniffer
• Results need appropriate
interpretation
• Tool will point to error on the
screen, if available
10
14. Colour Contrast Analyser app
• Ability to check colour
contrast for different types
of colour blindness
14
15. Sim Daltonism
• Free Colour blindness simulator app for Mac OS X
• “Filters in real-time the area around the mouse pointer and
displays the result – as seen by a color blind person – in a floating
palette”
15
https://michelf.ca/projects/sim-daltonism/
24. Usability vs Accessibility testing
• Methodology is the same
24
• Being mindful when facilitating
• Tasks for screen reader to include everything
• Adapt number of tasks
• More specific recruiting
• Using users set up – going into their home
25. Recruiting for accessibility testing
with users
• Professional recruit
• Personal networks
• Challenging to find larger samples
• Novice vs. expert users
25
26. What to test on
• Think about the device (laptop, mobile, desktop, tablet)
• Type of assistive technology
26
27. Personal set up
• Set up is calibrated in specific
ways
27
Image credit: http://www.cccblog.org/2014/05/16/vis
ions2025-interactions/
• Avoid bringing a cast of 1000s
• Recording can be a challenge
• Important to note the specifics of
the user’s set ups and settings
• Speed of the screen reader
• Advanced screen reader user’s can
get up to 900-1200 words per
minute
28. Technology versioning
• Assistive technology can be quite finicky
• People don’t always upgrade to new versions
• Intense learning curve
28
29. Testing at a facility
• Facility itself has to be accessible
• User’s tech set up needs to be portable
• Alternatively -allow time for the participant to
calibrate the technology
29
30. Remote testing
• Difficult to view user’s tech set up and how they use it
• Software/applications needed to download must be accessible
• Software/application must not interfere
• Tech issues -> difficult to help find solutions
30
31. Facilitation
• Usual facilitation techniques: echo, boomerang, columbo
31
• Need to avoid using visual cues/clues
• Any supporting printed material needs to be large and
clearly legible
• When testing with screen readers, you may need to ask
users to slow down their speed (words per minute)
33. Challenges
33
• Recruiting
• Getting enough users with the same technology
• Travel time going to people’s homes
• Recording
• Things not coded to standard meant upfront effort recruiting,
planning was ‘wasted’
• Forgetting to note down people’s set ups
• Sometimes you can’t recreate the set ups
• Wide range of technologies meant hard to identify patterns
35. Usability Matters
215 Spadina Ave, Toronto
www.usabilitymatters.com
info@usabilitymatters.com
Thank you
facebook.com/UsabilityMattersInc
@umatters
linkedin.com/company/usability-matters
Heather Moore
416 598 7770 ex 20
heather@usabilitymatters.com
Linn Vizard
416 598 7770 ex 19
linnea@usabilitymatters.com