In this session, we will discuss some established patterns and techniques that are “technically” accessible but that can nonetheless affect usability, based on user studies with people who have disabilities. We’ll discuss the ways that users came to discover (or not) the tasks at hand using the tools they rely on to browse the web, and solutions recommended by those users. We’ll also touch on practical ways to integrate testing with users with disabilities into your usability practice. Major takeaways: Why we do usability testing: ● The interface is not the goal. Users access your content to achieve a goal, not to interact with your content. The interface is a means to an end. ● Usability is not compliance. Accessibility often begins with an assessment against WCAG 2.0, but meeting guidelines doesn’t guarantee usability. ● Context matters. A solution that meets accessibility guidelines might be usable in one context but not in another. ● Assumptions hold us back. Letting go of assumptions about how users with disabilities use technology lets us focus on creating holistic solutions that benefit everyone. Opportunities for discovery: • See exactly how users choose to interact with and understand complex interactions. • Understand why users are able or unable to access or use content. • Discover ways that users access content outside of a controlled setting. Making a usability practice for accessibility Don’t: ● Test with users before assessing and remediating for accessibility. ● Use WCAG 2.0 as a checklist for usability. ● Make assumptions about your users’ devices and screens. ● Throw out the baby. (But maybe change the bathwater.) Do: ● Allow participants to test with their own devices and software in their own environments. ● Use what you know about your users to inform decision about what you test. ● Make testing low stress for participants and moderators. ● Compensate participants.

1. Usability testing
for accessibility:
Patterns for
discovery
Elements
Penn State
13 June 2016

3. Devon Persing
devon@simplyaccessible.com
@devonpersing
Accessibility Consultant
Simply Accessible
http://sateach.es

4. Today
1. Why and how we do usability testing
2. Examples from the field
3. Making a usability practice for accessibility

5. Usability
testing for
accessibility

6. The interface is not the goal
Users access your content to achieve a
goal, not to interact with your content.
The interface is a means to an end.

7. Usability is not compliance
Accessibility often begins with an assessment
against the Web Content Accessibility
Guidelines (WCAG 2.0), but meeting
guidelines doesn’t guarantee usability.

8. Context matters
A solution that meets accessibility guidelines might be
usable in one context but not in another.

9. Assumptions hold us back
Letting go of assumptions about how users
with disabilities use technology lets us focus on
creating holistic solutions that benefit
everyone.

10. How we do usability testing
• Moderated remote or in-person tests
• Participants select software, hardware, and environment
• Combination of functional testing and feedback on visual
designs or wireframes
• Test only with content that has been assessed (and
remediated, if necessary) for accessibility
• Usability is a standard process with an owner

11. BlindnessCognitive
Situational disabilities
Chemo brain
Color blindness
Cystic fibrosis
Gamer’s thumb
Dyslexia
Language barriers
Photosensitive epilepsy
Astigmatism
Hard of hearing
Lazy-Eyes
Directionally challenged
Poor hearing
Age-related macular degeneration
Multiple sclerosis
Learning difficulties
Visual impairments
Tremors
Muscle slowness
Deuteranopia Monochromacy
Dichromacy
Anomalous trichromacy
Protanopia
Protanomaly
Deuteranomaly
Tritanopia
Tritanomaly
Deafness
Achromatopsia
Loss of fine muscle control
Parkinson’s disease
Muscular dystrophy
Cerebral palsy
Stroke
Photoepileptic seizures
Developmental disabilities
Dyscalculia
Attention deficit disorder
Dementia
Acquired brain injuries
Neurodegenerative diseases
Difficulty concentrating
Dysgraphia
Getting older
Post-concussion syndrome
Sleep deprivation
Vertigo
Illiteracy
Amputation
Cataracts
Glaucoma
Hearing
Autism
Motor Diabetic retinopathy
Low vision
Noise-induced hearing loss
Aphasia
Reading disordersVisual
Vestibular disorders

12. Examples

13. Best practice doesn’t make perfect

14. ARIA tabs for primary content
• Most users had a hard time. (One breezed through!)
• AT users struggled with finding the content in context
without additional way finders like headings and links.
• AT users struggled with using the controls, once found.
• If another way to do the activity was available via
navigation, users preferred accessing the content
elsewhere.

15. Grid love

16. Form/grid with large touch targets
• AT users could navigate easily via standard keys for forms
and tables.
• Low vision users could scan the grid easily.
• Sighted keyboard-only users interacted easily with the
visible radio button controls.
• Mouse users and users of devices and software that mimic
mouse movements found the large target size easy to use.

17. The big picture

18. The big picture

19. The big picture

20. The big picture

21. Size matters
• Non-visual AT users may not use a monitor at all.
• Low vision users may trigger smaller breakpoints via:
• Browser-native zoom
• Resizing text with a plugin or at the OS level
• Sizing down the browser window to fit a portion of a
magnified screen
• A combination of any of the above

22. Opportunities for discovery
• See exactly how users choose to interact with
and understand complex interactions
• Understand why users are able or unable to
access or use content
• Discover ways that users access content
outside of a controlled setting

23. Making a usability
practice for
accessibility

24. Don’t…
• Test with users before assessing and remediating for
accessibility.
• Use WCAG 2.0 as a checklist for usability.
• Make assumptions about your users’ devices, screens,
and habits.
• Throw out the baby. (But maybe change the bathwater.)

25. Do…
• Allow participants to test with their own hardware and
software, in their own environments.
• Use what you know about your users and product to inform
decisions about what you test.
• Make testing flexible and low stress.
• Have an owner.
• Compensate participants.

26. Thank you!
/ Devon Persing
/ Simply Accessible
/ devon@simplyaccessible.com
/ @devonpersing