The document provides an overview of prototyping accessibility for a workshop presentation. It includes instructions for group exercises to prototype user interface elements and develop personas. It also covers various accessibility topics like disability types, user experience models, technical accessibility standards around text alternatives, typography, links, color contrast, labeling fields, document structure, and keyboard/screen reader support. The goal is to educate attendees on inclusive design practices through hands-on exercises and discussions.
4. • I’ve written some stuff,
• Member of W3C,
• Building for the web
since 1993,
• Learn more at
AdrianRoselli.com,
• Avoid on Twitter @aardrian.
About Adrian Roselli
6. Group Exercise!
• Decide on a user interface element. Examples:
• Login form,
• Disclosure widget,
• Data grid,
• Search,
• etc.
• Quickly describe or draw it on paper (no code).
• 15 minutes.
8. What is a11y?
• A numeronym for “accessibility”:
• The first and last letter (accessibility),
• The number of characters omitted (a11y).
• Prominent on Twitter (character restrictions):
• #a11y
• Examples:
• l10n → localization
• i18n → internationalization
9. Disability is not just a health problem. It is
a complex phenomenon, reflecting the
interaction between features of a person’s
body and features of the society in which
he or she lives.
— World Health Organization
12. Disability Types
• Physical
• Epilepsy
• Mobility
• Fine motor skills
• Hearing
• Deaf
• Hard of Hearing
• Vision
• Color blindness
• Low vision
• Blind
• Cognitive
• ADD/ADHD
• Autism
• Dyslexia/Dyscalculia
• Learning and Language
• Speech
• Stuttering
• Non-verbal
• Cluttering
• Apraxia of speech (AOS)
13. Disability Types
• Blindness
• Low Vision (including color blindness)
• Deaf and Hard of Hearing
• Speech
• Physical
• Intellectual & Cognitive
14. Blindness
• Screen reader user
• Keyboard-only user
• Relies on:
• Headings
• Form Elements
• Links
• Landmarks
15. Low Vision
• May use high contrast modes
• May not be able to differentiate colors
• May scale fonts
• May use a screen magnifier
• May use a screen reader
• Relies on:
• Scaling fonts
• Good contrast
16. Deaf and Hard of Hearing
• Cannot hear audio cues
• Will struggle if captions are not synchronized
• First language may be sign language
• Relies on:
• Good captions
• Visual cues
• Color cues
• Haptic cues
17. Speech
• May speak less clearly
• May be non-verbal
• Can be stymied by voice interfaces
• Phone interaction may not be possible
• May use assistive technology
• Relies on:
• Other interactions
18. Physical
• Temporary to permanent
• Slight to severe
• Can change throughout a day
• May use specialized hardware
• May use a screen reader
• May use dictation software
• Relies on:
• Generous hit areas
• Simple interactions
19. Intellectual & Cognitive
• May use a screen reader
• May use dictation software
• May benefit from any/all considerations already listed
• Relies on:
• Well-structured content
• Plain language
• Good context
38. Group Exercise!
• Each person in your group must pick a disability type:
1. Low vision
2. Blindness
3. Hearing and Speech
4. Physical
5. Cognitive
• Within your group, discuss where each of your types overlap in:
• Barriers, abilities, needs, etc.
• 15 minutes.
41. Personas
Adrian
• Works when he should be relaxing, relaxes when he should be
working.
• Lives between motorcycles.
• Works late at night with the TV on.
• Uses sub-titles in Netflix.
• Keeps all screens as dark as possible.
42. User Stories
• Components:
• User,
• Outcome,
• Value.
• Writing:
• As user, I want outcome.
• As user, I want outcome so that value.
• In order to get value as user, I want outcome.
43. Selfish User Stories
• As a user on a sun-lit patio, I want to be able to read the
content and see the controls.
Add beer and as a user I may have trouble focusing.
44. Selfish User Stories
• As a user in bed with a sleeping spouse, I want to watch a
training video in silence so that I can get caught up at work.
As a user who doesn’t want to get punched for having slacked off at work.
45. Selfish User Stories
• In order to click links as a user with no elbow room in coach
class with a tiny trackpad, I want click areas to be large enough
and adequately spaced.
As a user in coach class who also paid too much for the drink he’s spilling on his keyboard.
46. Selfish User Stories
• As a user distracted by the TV, I want clear headings and labels
so that I don’t lose my place.
As a user who really should be finishing his work in the office.
48. Group Exercise!
• Develop a (proto-) persona.
• Develop user stories for your persona.
• As user, I want outcome.
• As user, I want outcome so that value.
• In order to get value as user, I want outcome.
• Consider the UI element you created.
• 15 minutes.
50. Text Alternatives for Images
• Can you still make sense of the page?
• Is content missing?
• Can you still use the site?
• Is your alt text useful?
• Do you account for CSS background images?
• What about SVGs?
• Or CSS-generated symbols / icons?
http://www.4syllables.com.au/2010/12/text-alternatives-decision-tree/
http://dev.w3.org/html5/alt-techniques/#tree
53. Typography Matters
• Leading / line height at least 1.5× font size (WCAG 2.1),
• Space after paragraphs at least 2× font size (WCAG 2.1),
• Letter spacing / tracking at least 0.12× font size (WCAG 2.1),
• Word spacing at least 0.16× font size (WCAG 2.1),
• Avoid justified text,
• Avoid italics,
• Use larger text (lean on browser default),
• Use good contrast,
• Use clear, concise writing.
55. Hyperlinks!
• Is there any “click here,” “more,” “link to…”?
• Are you using all-caps, URLs, emoticons?
• Do you warn before opening new windows?
• Do links to downloads provide helpful info?
• Are you using pagination links?
• Are your links underlined (or otherwise obvious)?
• Is there alt text for image links?
• Is the link text consistent?
56. Hyperlinks!
• You are not Google:
• Users know Google’s layout,
• Users probably don’t visit your site daily.
• Relying on color alone will not suffice (WCAG 1.4.1 [A], 1.4.3 [AA]),
• Necessary contrast values:
• 4.5:1 between text and its background for copy,
• 3:1 between text and its background for larger text,
• 3:1 between surrounding text and a hyperlink, plus an additional visual cue
(G183).
http://adrianroselli.com/2014/03/i-dont-care-what-google-did-just-keep.html
58. Hit Areas
• Make areas large enough to tap,
• Leave space between hit areas to avoid mis-taps/clicks,
• Fitts’ Law (time to target as function of size of target),
• Apple: 44pt × 44pt,
• Microsoft: 48px × 48px (spaced 2mm apart),
• Android: 48dp × 48dp (spaced 8dp apart),
• BBC: 7mm × 7mm (inside an exclusion zone of at least 7mm × 7mm)
• WCAG 2.1 Success Criterion 2.5.5 Target Size (AAA).
63. Color Contrast
• Is there enough contrast?
• Are hyperlinks, menus, etc. still visible?
• WCAG 2.0:
• 4.5:1 for normal text
• 3:1 for large text (14+pt & bold, or 18+pt)
• WCAG 2.1:
• 3:1 for UI components, graphical objects
64. Color Contrast
• WCAG 2.1 has broadened it,
• Typography,
• Icons and glyphs,
• Form elements, error messages,
placeholders,
• Hover, focus, selected states.
65. Label Your Fields
• Provide instructions for the entire form,
• Provide a programmatic indication of required fields,
• Provide formatting advice,
• Use ARIA to associate formatting advice,
• Avoid placeholder text,
• Associate error messages with fields.
66. Label Your Fields
• Match the for attribute to the corresponding field’s id
attribute.
• Label text provides a larger hit area for mouse / touch,
• Label text should appear above or the left of text inputs or
menus (for LTR languages),
• Label text should appear after checkboxes / radio buttons (for
LTR languages).
• Label grouped fields (<fieldset> / <legend>)
68. Structure Your Document
• Sectioning elements already have accessibility built in. Use
them.
• <header>
• <nav>
• <main> (one per page)
• <aside>
• <footer>
• <form> (a search form)
73. Structure Your Document
• Use only one <h1> per page,
• Don’t skip heading levels,
• Use appropriate nesting,
• There is no Document Outline Algorithm:
• Don’t use <h1> within every new <section> nor <article>,
• This will not affect your SEO.
http://adrianroselli.com/2013/12/the-truth-about-truth-about-multiple-h1.html
75. Structure Your Document
1. Ordered lists
2. …
3. …
Description lists
As statement and
their description
Key
Value
• Unordered lists
• …
• …
76. Structure Your Document
1. Boil water
2. Add pasta
3. Drain water
Pasta
1 pound
Water
4 quarts
Olive oil
Not 4 quarts
• Pasta
• Water
• Olive oil
77. Display vs Source Order
• CSS techniques allow visual order to break from DOM order:
• Floats,
• Absolute positioning,
• Flexbox (see 5.4.1 of ED for a11y note),
• Grid (read Rachel Andrew on subgrid).
• WCAG 1.3.2 and 2.4.3 describe meaningful sequence and tab
order matching visual flow,
• Different behavior among different browsers, MQs.
http://adrianroselli.com/2015/09/source-order-matters.html
http://200ok.nl/a11y-flexbox/
78. Display vs Source Order
http://codepen.io/aardrian/full/MavVeb/
Firefox
Chrome
79. Be Keyboard Friendly
• tabindex="-1"
• Use to set focus with script,
• Does not put it in tab order of page.
• tabindex="0"
• Allows user to set focus (eg: via keyboard),
• Puts in tab order of page (based on DOM).
• tabindex="1" (or greater)
• Do not do this,
• Messes with natural tab order.
http://adrianroselli.com/2014/11/dont-use-tabindex-greater-than-0.html
81. Be Keyboard Friendly
• Do you have scrolling content boxes?
• Keyboard users cannot access it.
• Do you have content that displays on hover?
• Keyboard users probably cannot access it.
• A technique:
• <div role="region" aria-label="[if appropriate]"
tabindex="0">
http://adrianroselli.com/2016/02/keyboard-and-overflow.html
84. Be Keyboard Friendly
• Do not use a <div> nor <span> as a control.
• Does the control take me to another URL?
• Use an <a href>.
• Note: does not fire on space-bar.
• Does the control change something on the current page?
• Use a <button type="button">.
• Does the control submit form fields?
• Use <input type="submit"> or <button type="submit">.
http://adrianroselli.com/2016/01/links-buttons-submits-and-divs-oh-hell.html
86. Be Keyboard Friendly
• Define :focus styles,
• Particularly if you removed link underlines,
• Everywhere you have :hover, add :focus,
• Look for :focus{outline:none;} in libraries:
• If you find it, remove it.
• Do not rely on browser defaults,
• Easy to test with the tab key.
http://adrianroselli.com/2014/06/keep-focus-outline.html
89. Use Captions, Subtitles, Transcripts
• Everybody uses them:
• Working in public, in bed, at home,
• Surfing in public, in bed, at work.
• Should include audio descriptions,
• Should include speaker identification,
• Review auto-captions (“craptions”):
• NoMoreCraptions.com
http://adrianroselli.com/2013/11/captions-in-everyday-use.html
90. Use Captions, Subtitles, Transcripts
• Do video/audio clips have text alternatives?
• Are links to closed-captions or transcripts built into the player or
separate text links?
• Is there an audio description available?
• Tools:
• Media Access Australia YouTube captioning tutorial, Vimeo captioning
tutorial,
• Tiffany Brown’s WebVTT tutorial,
• DIY Resources for Closed Captioning and Transcription from 3 Play Media.
http://webaim.org/techniques/captions/
92. Pattern Libraries
• Document all this for your custom widgets,
• Use this to build a larger pattern library,
• For many custom widgets: WAI-ARIA Authoring Practices 1.1,
• It is not perfect, but gets you started,
• Be wary of application-specific patterns.
• For truly custom widgets you have never seen before, consider
simplifying to an existing pattern.
93. Tab order indicated via numbers above
Accessibility requirements
See 3.1 Accordion in the WAI ARIA Authoring
Practices for requirements.
Focus and keyboard tab order
• Left/Up arrow moves to previous accordion
header
• Right/down arrow moves to next accordion
header
• Enter opens a panel when on the header
• When opened focus stays on the element, tab
moves to the first item in the header
Roles and states
• Accordion is a tablist
• Each header is a tab
• Use visibility hidden to hide content of tabs
Behavior
• Contents of accordion hidden from screen readers
when closed
• Contents remain open until closed by the user
• Header and arrow is a single touch target
97. Group Exercise!
• Take your user interface element and discuss how you might
design / spec / build / code it.
• Represent the disability category you championed earlier.
• Remember your personas, user story/ stories.
• Consider changing needs of users.
• 15 minutes
We will be doing group activities.
This gets the chaos organization out of the way early.
Have this slide showing as people come in.
1980 definition:
“In the context of health experience, a disability is any restriction or lack of ability (resulting from an impairment) to perform an activity in the manner or within the range considered normal for a human being.”
Everyone is different. No two people are alike.
With that in mind, it only makes sense that not everyone's body is going work the way everyone else's. Because of this, some people might not be able to see, hear, speak, understand, or move the way other people do.
A blind user cannot see what is on their screen. This may seem obvious, but it's important to think about what this really means. Most users don't think twice about how they ingest or interact with the content on their screen, nor does it really matter what the underlying code looks like. This is not the case for someone who cannot see the screen.
When looking at the screen is not an option, assistive technology (AT) such as a screen reader must be used to navigate the web. Screen readers rely on HTML to navigate. If the website or application is not properly coded, AT will not be able to pass along the correct information to the user. This includes such important elements such as:
Most likely a keyboard only user
Using a mouse is most likely difficult, if not impossible, for a user who cannot see what is on the screen. As a result, a user who is blind will most likely use a keyboard to navigate.
A keyboard-only user requires all functions performed by a mouse to be actionable via keyboard. These users are also prone to keyboard and/or programmatic focus issues if their experience isn't managed properly.
Someone with low vision has an impairment that cannot be corrected. In many cases, the person may be "legally blind" but still have some visual perception. There are different kinds of low vision and each has its own considerations. These considerations are different from blindness, though there may be overlap in approaches.
Some people may not be able to hear at all, or may have some kind of hearing impairment. This means any cues or information that are communicated by sound alone may be missed. The following barriers can occur.
Someone with a speech disability may be able to speak less clearly than others, or perhaps be entirely non-verbal (and this could be due to physical/motor or cognitive challenges). Some factors to bear in mind are:
Web-based services or functionality that require voice interactions will be difficult if not impossible
Websites or applications that offer a phone number as the only way to communicate with a company
A person who struggles with a speech impairment might use specialized AT, or none at all, depending on the root cause of their impairment. For example, someone who has lost their voice due to an injury or sickness might not require AT to navigate the web whereas someone who is non-verbal due to autism might require a screen reader or a more specialized application to communicate.
There are many possible forms of physical impairment, such as mobility or dexterity issues. When thinking about web accessibility, the most prominent physical impairments are motor control and the inability to use two hands at once, as these most affect interaction with a device.
Cognitive disabilities affect far more people than sensory disabilities. There's a large variety of reasons for cognitive barriers, and a corresponding wide range of effects they can have. Some causes and conditions are…
Asperger's Syndrome
Attention deficit disorder (AD/HD)
Autism
Dementia
Down Syndrome
Dyscalculia
Dyslexia
Learning disabilities
Rett Syndrome
Stroke
Traumatic brain injury (TBI)
Williams Syndrome
In order to make sense of the many different cognitive barriers people could experience, and to help us address them, they can be categorized broadly as follows.
Memory
Problem solving
Attention
Reading, linguistic, verbal comprehension
Math comprehension
Visual comprehension
Beware of disability stereotypes
It's very important that we do not generalize people when talking about then individual needs. No two people are alike. With that in mind, we must be certain that we avoid the following:
Using oversimplified terminology such as:
Vision, hearing, physical and cognitive impairments
These types of impairments are not one size fits all, for example "Vision" could mean someone who is low vision, someone who is light sensitive, or someone who is completely blind
Using Misleading terms like:
Screen reader users
Many people require a screen reader, for many different reasons
Incorrect:e.g. "Accessibility users“
Accessibility isn't something we use, but rather something we can't use without.
Our inclusive design principles
Recognize exclusion
Exclusion happens when we solve problems using our own biases. As Microsoft designers, we seek out those exclusions, and use them as opportunities to create new ideas and inclusive designs.
Learn from diversity
Human beings are the real experts in adapting to diversity. Inclusive design puts people in the center from the very start of the process, and those fresh, diverse perspectives are the key to true insight.
Solve for one, extend to many
Everyone has abilities, and limits to those abilities. Designing for people with permanent disabilities actually results in designs that benefit people universally. Constraints are a beautiful thing.
Trying to check into your airline in a foreign country
Keyboards, system in different language
Great way to extend a trip
The objective is to get people to champion their disability type and think about where its needs and challenges intersect with others.
It should prime them for the personas and user stories section to maybe write more aggregated stories.
Talk about the general benefits, citing SR users, SEO (ugh), bad connections.
Do not dwell on the technical stuff; let it be just the background
With images
Without
Call out the logo (useful alt), the nav (CSS BG), the giant kid photo (blank alt)
Again, background. Do not dwell on the items, Talk about typography as an art, how legibility benefits all users, but also helps those with cog, low vision, and folks traveling on bumpy planes
Animated GIF, ~2s cycle
Specialized solutions generally aren’t so good
Compare to resizing widgets
Link text warrants some thought
Context, destination, purpose all matter
Please make them obvious
Contrast is a real concern… which we will discuss
What here is the link? The photo? The title? The date? The abstract?
Hopefully not all of them, as that would be confusing to a SR user
It is not obvious.
WCAG 2.1 AAA: 44px
Excludes:
Equivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
Inline: The target is in a sentence or block of text;
User Agent Control: The size of the target is determined by the user agent and is not modified by the author;
Essential: A particular presentation of the target is essential to the information being conveyed.
Apple
Microsoft
Android
BBC
Not a platform; this is good for planning your own internal guidelines
We see this failure all the time
I hate them because of all the screen shots I need for the audits
The screen shot is from the TPG style guide
Note that it shows good color combinations and calls out ones to avoid
Essentially you want a screen reader user to know what field they just focused
You want voice users to be able to focus fields by name
Note that larger hit area benefit
Video with audio
This is 1:44, so maybe talk over it for a bit
These allow SR users to jump to a section
They are valuable for a reader view
As we move to voice interfaces, these are valuable for the parsing algorithms
Also helps screen reader users
Also helps reader mode
Also helps future Uis (voice)
Animated GIF
Power users
Mobility impaired
Screen reader users
Animated GIF
Animated GIF
Video with audio
Animated GIF
You can style anything to look like anything, so do not get hung up on choosing based on _how_ it looks
Screen shot of a link with the blue Chrome focus ring on the blue background of the Chrome help page.
Animated GIF
Pattern as taken from the WAI Authoring Practices Guide