Accessibility testing using browser tools such as the Web Developer or the WAVE toolbars is already a daunting task; add screen reader testing requirements to the mix, and for most people, it soon becomes way too complicated to even bother. This session is intended for anyone who does not consider himself or herself to be an accessibility expert, but yet needs to sometimes assess accessibility. In this session, we will be going over a series of techniques for testing the accessibility fundamentals of HTML using NVDA, an open source screen reader. No technical ninja skillz required! Join us if you are willing to discover 12 simple techniques in 30 quick minutes!
5. 39 000 000
people are blind
246 000 000
people have low vision
Visual impairment and blindness (WHO, 2014)
http://www.who.int/mediacentre/factsheets/fs282/en/
10. Meet Mary
Needs and Goals
• To know she can trust people
• Open her own music school
Behaviors
• Very outgoing, always seeking excitement
• Gets things done quickly when focused
Particularities
• Was born blind
• Is a power screen reader user
• Uses NVDA at a speech rate of 75
Demographics
• 35 years old
• Married
• Two boys
• Musician
• Works from home
11. Meet John
Needs and Goals
• Clear, simple instructions
• Not get lost in details
Behaviors
• Loves to make to-do lists for everything
• Frequently feels anxious and overwhelmed
Particularities
• Became legally blind after car accident
• Is a casual screen reader user
• Uses NVDA at a speech rate of 50
Demographics
• 47 years old
• Single
• No kids
• Accountant
• Works in small office
12. Meet Jim
Needs and Goals
• Spend as much time as possible with family
• Goes to church every Sunday
Behaviors
• Untrusting of computers and technology
• Finds interacting with computers impersonal
Particularities
• Has macular degeneration (low vision)
• Recently been introduced to screen readers
• Uses NVDA at a speech rate of 25
Demographics
• 75 years old
• Widower
• 15 kids/grandkids
• Retired
13. Meet Andrea
Needs and Goals
• Become a partner at her clinic
• Be a great mother to her only daughter
Behaviors
• Can sometimes be obsessive-compulsive
• Gets bogged down in details
Particularities
• Has dyslexia and difficulty concentrating
• Is an experienced screen reader user
• Uses NVDA at a speech rate of 50
Demographics
• 26 years old
• Single
• 1 daughter
• Physical Therapist
• Works in a Clinic
14. screen reader users
types of very specific needs
radically different uses
ways to make content accessible
4…
32. Getting Started
Reading Text with NVDA
Command Description
NVDA +↓ Read all from the current position
Ctrl Stop reading
NVDA +↑ Read current line
Ctrl + ← / → Read previous / next word
Ctrl + ↑ / ↓ Read previous / next paragraph
↑ / ↓ Read previous / next line
← / → Read previous / next character
37. Getting Started
General Navigation with NVDA
Quick Keys Description
H Navigate through headings
D Navigate through landmarks
1-6 Navigate through headings level 1 to 6
F Navigate through forms
T Navigate through tables
B Navigate through buttons
L Navigate through lists
I Navigate through list items
G Navigate through graphics
K Navigate through links
41. Getting Started
Test Case Template
Test Case Subject Test Description Step Name Step
Description
Step Expected
Results
42. Accessibility Related User Stories
Text Content Testing
As a user,
I need text content to be clearly exposed to my tools,
so that I can understand what the content is about and how I can use it.
43. a11yTip #1
Provide descriptive titles for web pages
http://bit.ly/1lKYkFE
2.4.2 (A) - Page Titles
Pages have descriptive,
informative and unique
page titles.
44. a11yTip #2
Identify the default language of the content
http://bit.ly/1lKWPaG
3.1.1 (A) - Default Language
The language of the page
is identified using the
HTML lang attribute.
45. Accessibility Test Cases
Page Titles Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. Set focus to the top of the page
4. Hit the NVDA+T key combination
5. Listen to the information conveyed
Expected Results
NVDA announces a meaningful page title that
clearly identifies and represents the content
of the page.
46. Accessibility Test Cases
Default Language Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
47. 1. Exercise files: http://bit.ly/1VrVgCA
2. Test case template: http://bit.ly/1LnsAG4
3. Turn NVDA on! (Windows key + R » type NVDA)
56. Photo Credits
All rights belong to their respective owners.
http://i.huffpost.com/gen/1760949/thumbs/o-BALANCE-SCALE-facebook.jpg
http://foto-ruta.com/wp-content/uploads/2012/01/FR_step5.jpg
http://www.bodybiz.nl/wp-content/uploads/2013/06/5redenenen.jpg
http://www.vibrantnation.com/wp-content/uploads/blah-blah.jpg
http://centerfordentalimplants.info/wp-content/uploads/2013/02/incredulous1.jpg
http://payload61.cargocollective.com/1/0/12581/3537536/ready_play_ID_860.jpg
http://kpumc.org/wp-content/uploads/2014/01/Angry-Woman.jpg
http://hemlocktime.files.wordpress.com/2014/03/4084963522_f50fc5ed37_b.jpg
http://imanageproducts.uk/wp-content/uploads/2015/01/Agile-pic-3.jpg
https://pbs.twimg.com/media/Bq5y-56IYAAAmkI.jpg:large
http://rabota5.ru/photo/zarabotat-na-shkolnyh-sochineniyah-3454.jpg
57. Accessibility Related User Stories
Document Structure Testing
As a user,
I need to be able to make sense of how the page is organized,
so that I can efficiently determine the document outline and what the
different sections of the page are.
58. a11yTip #3
Organize content using hierarchically nested headings
http://bit.ly/1ia4Gc6
1.3.1 (A) – Section Headings
Content is hierarchically
structured using heading
elements.
59. a11yTip #4
Use landmark roles to define page regions
http://bit.ly/1ryGRRx
1.3.1 (A) - Page Regions
WAI-ARIA landmarks are
used to identify various
sections of the page.
60. Accessibility Test Cases
Section Headings Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
61. Accessibility Test Cases
Page Regions Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
62. Accessibility Related User Stories
Navigation Testing
As a user,
I need all navigation mechanisms provided in a page to be
marked up in a way that is compatible with the tools I use,
so that I can easily and efficiently navigate through content.
63. a11yTip #5
Organize content in a sequential reading order that remains logical
http://bit.ly/1rPdEkF
1.3.2 (A) - Reading Order
The reading and navigation
order (determined by code
order) is logical and
intuitive.
64. a11yTip #6
Provide links that meaningfully describe their purpose
http://bit.ly/1mJNDCm
2.4.4 (A) - Link Purpose
The purpose of each link
can be determined from
the link text alone, or
from the link text and
its context.
65. Accessibility Test Cases
Reading Order Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
66. Accessibility Test Cases
Link Purpose Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
67. Accessibility Related User Stories
Images Testing
As a user,
I want every significant image displayed in the
page to be efficiently described in text,
so that I don't miss out on any important information or instructions.
68. a11yTip #7
Provide alt attributes for active images
http://bit.ly/1q0OVOJ
1.1.1 (A) - Informative Images
Informative images have
descriptive equivalent text
serving the same purpose
and presenting the same
information as the image.
69. a11yTip #8
Make decorative images invisible to assistive technologies
http://bit.ly/1fGdj3A
1.1.1 (A) - Decorative Images
Images that do not convey
content, are decorative, or
with content that is already
conveyed in text are given
null alternative text.
70. Accessibility Test Cases
Informative Images Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
71. Accessibility Test Cases
Decorative Images Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
72. Accessibility Related User Stories
Keyboard Accessibility Testing
As a user,
I need to be able to take advantage of every
functionality available using only my keyboard,
so that I can use the site to its full, expected extent.
73. a11yTip #9
Ensure pages can be fully controlled without a mouse
http://bit.ly/Sknpgr
2.1.1 (A) - Keyboard Access
Page functionalities are
available using the
keyboard.
74. a11yTip #10
Place active elements in a predictable tabbing order
http://bit.ly/1bUgxPZ
2.4.3 (A) – Keyboard Focus
Active elements receive
focus in an order that follows
sequence and relationships
in the content.
75. a11yTip #11
Provide a mechanism to skip content repeated across pages
http://bit.ly/1fGcXKr
2.4.1 (A) - Bypass Blocks
A method is provided to
skip navigation and other
elements that are repeated
across pages.
76. Accessibility Test Cases
Keyboard Access Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
77. Accessibility Test Cases
Keyboard Focus Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
78. Accessibility Test Cases
Bypass Blocks Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
79. Accessibility Related User Stories
Tables Testing
As a user,
I need all information contained in tables to be
explicitly associated with corresponding header cells,
so that I can understand how the information is organized.
80. a11yTip #12
Structure tabular information using table markup
http://bit.ly/1kvnzYG
1.3.1 (A) – Data Table Markup
Header cells and data cells
are properly coded using
data table markup.
81. a11yTip #13
Associate cells in complex data tables using headers and ID attributes
http://bit.ly/1IEt8Uk
1.3.1 (A) – Data Cells Association
Data cells in complex data
tables are programmatically
associated with every
corresponding header cell.
82. Accessibility Test Cases
Data Table Markup Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
83. Accessibility Test Cases
Data Cells Association Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
84. Accessibility Related User Stories
Forms Testing
As a user,
I need form controls, labels and instructions to be clearly conveyed back to me,
so that I can efficiently use the form to interact with the site.
85. a11yTip #14
Associate text labels with form controls using the LABEL element
http://bit.ly/Vr03GH
1.3.1 (A) - Forms Association
Labels are programmatically
associated with form controls
using the LABEL element
with matching values on
the for and ID attributes.
86. a11yTip #15
Do not rely on asterisks alone to define required fields
http://bit.ly/P0kjMk
3.3.2 (A) – Required Fields
Asterisk symbols on text
labels are used, in conjunction
with aria-required attributes
set to the form controls.
87. Accessibility Test Cases
Forms Association Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…
88. Accessibility Test Cases
Required Fields Test Case
1. Turn on NVDA screen reader
2. Open the page in Firefox
3. …
4. …
5. …
6. …
7. …
Expected Results
…