Usability testing for accessibility: Patterns for discovery #econfpsu16
-
Upload
devonpersing -
Category
Internet
-
view
135 -
download
1
Transcript of Usability testing for accessibility: Patterns for discovery #econfpsu16
![Page 1: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/1.jpg)
Usability testing for accessibility: Patterns for discovery Elements Penn State 13 June 2016
![Page 2: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/2.jpg)
![Page 3: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/3.jpg)
Devon Persing [email protected]
@devonpersing
Accessibility ConsultantSimply Accessible http://sateach.es
![Page 4: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/4.jpg)
Today 1. Why and how we do usability testing 2. Examples from the field 3. Making a usability practice for accessibility
![Page 5: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/5.jpg)
Usability testing for accessibility
![Page 6: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/6.jpg)
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.
![Page 7: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/7.jpg)
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.
![Page 8: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/8.jpg)
Context matters A solution that meets accessibility guidelines might be usable in one context but not in another.
![Page 9: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/9.jpg)
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.
![Page 10: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/10.jpg)
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
![Page 11: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/11.jpg)
BlindnessCognitiveSituational disabilities
Chemo brain
Color blindness
Cystic fibrosis
Gamer’s thumb
DyslexiaLanguage 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 controlParkinson’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 syndromeSleep deprivation
Vertigo
Illiteracy
Amputation
CataractsGlaucoma
Hearing
Autism Motor Diabetic retinopathy
Low vision
Noise-induced hearing loss
Aphasia
Reading disordersVisual
Vestibular disorders
And many, many, many more…
![Page 12: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/12.jpg)
Examples
![Page 13: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/13.jpg)
Best practice doesn’t make perfect
![Page 14: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/14.jpg)
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.
![Page 15: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/15.jpg)
Grid love
![Page 16: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/16.jpg)
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.
![Page 17: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/17.jpg)
The big picture
![Page 18: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/18.jpg)
The big picture
![Page 19: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/19.jpg)
The big picture
![Page 20: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/20.jpg)
The big picture
![Page 21: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/21.jpg)
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
![Page 22: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/22.jpg)
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
![Page 23: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/23.jpg)
Making a usability practice for accessibility
![Page 24: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/24.jpg)
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.)
![Page 25: Usability testing for accessibility: Patterns for discovery #econfpsu16](https://reader031.fdocuments.net/reader031/viewer/2022021814/58ef53c61a28ab05458b459d/html5/thumbnails/25.jpg)
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.