This document outlines Karl Groves' presentation on accessibility testing techniques. It discusses various types of disabilities and challenges they pose on the web. It then covers principles of accessibility, assistive technologies, and different approaches to testing including automated, manual, use case, and usability testing. The rest of the document provides guidance on testing specific types of web content like markup, forms, images, media, navigation, and JavaScript to evaluate accessibility.
Por estos dos motivos, defensa de JOH solicita repetir juicio
Viking methodology
1. 1Monday, May 20, 13
Viking Accessibility:
The Warrior's Approach to Hands-on Testing
2. 2Monday, May 20, 13
Karl Groves
karl@simplyaccessible.com
@karlgroves
3. 3Monday, May 20, 13
Goals and Objectives
• Understand accessibility testing
techniques
• Understand common challenges by
content type
• Gain hands-on knowledge
4. 4Monday, May 20, 13
Resources
http://examples.simplyaccessible.com/vikinghandson/
6. 6Monday, May 20, 13
Visual Impairment
• Blindness
• Partially Sighted
• Low Vision
• Colorblindness
What types of challenges will they have on the web?
7. 7Monday, May 20, 13
Hearing Impairment
• Deafness (one/ both ears)
• Hard of hearing
• High/ low frequency hearing loss
What types of challenges will they have on the web?
8. 8Monday, May 20, 13
Motor Impairment
• Loss of limbs, digits
• Palsy disorders
• Repetitive stress injuries
• Arthritis
• Spinal cord injuries
• more
What types of challenges will they have on the web?
9. 9Monday, May 20, 13
Cognitive Impairment
• Autism
• Brain injury
• Parkinson’s
• Dyslexia
• Alzheimer’s
• more
What types of challenges will they have on the web?
10. 10Monday, May 20, 13
Speech Impairment
• Stuttering
• Muteness
• Dysarthria (resulting from motor control
disorders)
• Articulation & phonemic disorders
What types of challenges will they have on the web?
23. 23Monday, May 20, 13
Automated Testing
What is it? Use of tool to access web document and
subject it to predetermined heuristic checks
• Plugins/ Toolbars
• Desktop Apps
• Web Apps
24. Automated Testing
24Monday, May 20, 13
Pros:
• Unprecedented
efficiency (cost per issue)
• Some issues don’t
require humans
Cons:
• Incomplete coverage
• False positives
• Subjectivity in a11y
• DOM testing
• User interaction
25. 25Monday, May 20, 13
Manual Testing
What is it? Use of hands-on techniques to inspect for
potential failures, possibly by emulating disabled user
scenarios
• Code inspection
• Hardware manipulation
• Software/ Settings manipulation
• AT Testing
26. Manual Testing
26Monday, May 20, 13
Pros:
• Accuracy
• Reliability
• Judgment
Cons:
• Time
• Reliant on tester’s skill
27. 27Monday, May 20, 13
Use Case Testing
What is it? Analysis of system behavior by subjecting it to
scenarios that touch on functional requirements - in this case
doing so with assistive technologies
28. Use Case Testing
28Monday, May 20, 13
Pros:
• Can happen
concurrently with
other testing
• Gives glimpse of
real-world issues
faced by PWD
Cons:
• Time
• Tester must know the AT
• Success with one AT !==
success with all
29. 29Monday, May 20, 13
Usability Testing
What is it? Observation of test participants using core
user tasks, measuring efficiency, accuracy, recall, emotional
response.
30. Usability Testing
30Monday, May 20, 13
Pros:
Most closely represents
user’s actual experience
Cons:
• Expensive
• Time-Consuming
• Results may be skewed
by high impact issues
31. 31Monday, May 20, 13
Tools
“It’s a poor mechanic who blames his tools” - Old Man Brian
46. 46Monday, May 20, 13
Driving Factors
• Modern websites are not composed of static content
• Certain types of issues occur more often than others
• Certain types of content have more issues than others
• Certain types of issues are more impactful than others
47. 47Monday, May 20, 13
Audits vs. QA
Audits:
• Should maximize utility
• Focus on UI component types
• Priority given to high use, high
risk features and components
QA:
• A11y should be part of
QA process
• Deliver fast, accurate
results & guidance
• Focus only on in-scope
work (i.e. user stories &
features under dev)
49. 49Monday, May 20, 13
Markup and A11y
• All content must be marked up
using the most appropriate
elements & attributes for the job
• All scripted controls must operate
like the native controls which they
mimic
51. Markup and A11y
51Monday, May 20, 13
Page Structure Requirements:
• Valid, semantic markup
• Page titles: unique, terse, clear, informative
How do we test this?
53. 53Monday, May 20, 13
Keyboard Access/ Focus Control
Keyboard Access, Focus Control:
What is it?
How are users impacted?
54. Keyboard Access/ Focus Control
54Monday, May 20, 13
Keyboard Access, Focus Control
Requirements:
• Focus order matches expected interaction
order
• Items that should get focus do; Items that
should not get focus don’t
How do we test this?
56. 56Monday, May 20, 13
CSS
Cascading Stylesheets:
What is it?
How are users impacted?
57. CSS
57Monday, May 20, 13
• Content must remain readable and operable
• Visual indications must also be represented
programmatically
• Color contrast
How do we test this?
59. 59Monday, May 20, 13
Forms
Forms:
What are they?
How are users impacted?
60. Forms
60Monday, May 20, 13
Forms Requirements:
• All fields labeled tersely, clearly
• Constraints identified
• All fields operable via keyboard
• Errors prevented
• Error recovery facilitated
How do we test this?
65. 65Monday, May 20, 13
Images
Images:
What are they?
How are users impacted?
66. Images
66Monday, May 20, 13
Image Requirements:
• Images not used to replace text
• All images have text alternative
• All text alternatives sufficiently clear
and informative
• Background images, sprites not used
for actionable items or content
How do we test this?
71. 71Monday, May 20, 13
Navigation
Navigation:
What is it?
How are users impacted?
72. Navigation
72Monday, May 20, 13
Navigation Requirements
• “Links”are actual links & use
valid href
• Link text is unique, terse,
clear, informative
How do we test this?
74. 74Monday, May 20, 13
Tables
Tables:
What are they?
How are users impacted?
75. Tables
75Monday, May 20, 13
Table Requirements
• No tables for layout
• Headers identified
• Header relationships
identified
• Good structure
How do we test this?
77. 77Monday, May 20, 13
Text Content
Text Content:
What is it?
How are users impacted?
78. Text Content
78Monday, May 20, 13
Text Content Requirements
• Proper use of headings
• Headings are unique, terse,
clear, informative
• Proper use and structure of
lists & sub-lists
How do we test this?
80. 80Monday, May 20, 13
JavaScript-driven Content
JavaScript Content:
What is it?
How are users impacted?
81. JavaScript-driven Content
81Monday, May 20, 13
JavaScript Requirements
• Device independence
• Keyboard access/ focus
control
• Name, State, Role, Value
How do we test this?
82. JavaScript-driven Content
82Monday, May 20, 13
Name: What do we call this thing?
State: What is it doing? (Implicitly) What else can it do?
Role: What type of object is it?
Value: What is its value (if it can have one)
Using standard controls in standard ways gives this to us for free.
84. 84Monday, May 20, 13
simplyaccessible.com
Accessibility consulting, strategy and assessments
Accessible development and remediation services
Training courses, workshops and conferences Karl Groves
karl@simplyaccessible.com
@karlgroves
+1 443.875.7343