The Open Web is an amazingly empowering platform for every human being. It’s our job as web developers to make it work for everyone.
It’s about everyone
Accessibility is about every human—not just extreme cases. Sometimes it’s easier to think in terms of extremes because it gives us a goal, but making our website work better for extremes also makes it work better for everybody else.
The great thing about the web and computers is that they empower everybody. It’s our goal to help every human accomplish what they want on our website, regardless of their physical, mental, or technological capabilities.
Impairments
Looking at specific impairments helps us narrow in on specific issues and fixing these issues helps our website work for everyone else.
There are lots of different impairments that can affect human beings. But it’s important thing to remember is that these impairments can be temporary—as an example: a broken arm.
Visual
Visual impairments are issues that affect eyes, e.g. blindness, partial or full; colour blindness; cataracts; glaucoma; age; etc.
Things we can do
- Allow text to be resized
- Have good contrast in colours
- Test for colour blindness related issues
- Make sure the website works well with screen readers
- Use proper alt attributes
- Don’t autoplay any sound
Mobility and dexterity
Mobility and dexterity impairments primarily affect people’s arms and hands, e.g. missing a hand, limited movement, difficulty with fine control, trouble holding a mouse, termors or shakes, etc.
Things we can do
- Recognize and prepare for the fact that not everybody will use a mouse
- Make the website keyboard accessible
- Increase hit areas of links and buttons
Auditory
Impairments that affect a person’s ability to hear, e.g. deafness, partial deafness, etc.
Things we can do
- Provide text captions and subtitles
- Don’t rely on sound for indicators.
- Don’t autoplay any sound
Cognitive
Generally considered something that affects a person’s brain, e.g. dyslexia, memory issues, problem solving issues, attention deficits, hyperactivity, reading abilities, etc.
Things we can do
- Make it clear where in the website the user is
- Organize your content correctly & use proper headings
- Make the text easily scannable
- Clearly mark links
- Use lots of images and graphics
- Don’t autoplay any sound
Tools
There are a few things that you should check on every website—at least—to help with accessibility.
The tools are still no replacement for proper user and accessibility testing.
- Bump the font-size up and down to make sure the layout doesn’t break: at least 2 sizes up and 2 sizes down; to make sure you site works with different default styles.
- Disabled images and see what happens to the layout without them.
- Disable the CSS to get an idea of what content is available to screen readers.
- Check the website with Sim Daltonism to look for colour blindness related issues.
- Run your website through one or all of the validators.
- Check all the pages with a screen reader like VoiceOver.
☛ Review the accessibility checklist for more.
Tools
Validators
Screen readers
Screen readers are accessibility tools to help users with poor vision or complete blindness get the content of a website read out to them.
They parse the content and understand the semantics and read the text out loud. The HTML semantics are interpreted and turned into understandable words.
Many screen readers also present lots of features to help users move around the screen with their keyboard.
Some popular screen readers:
VoiceOver
VoiceOver is the screen reader built into Apple’s operating systems, both desktop and mobile. It doesn’t require any installation, just needs to be turned on.
Here’s some shortcut keys for using VoiceOver:
Command + F5
— Turn VoiceOver on/offControl
— Pause VoiceOverControl + Option + Right Arrow
— Move to next itemControl + Option + Left Arrow
— Move to previous itemControl + Option + U
— Open the rotor (Use arrow keys to navigate)Control + Option + Command + H
— Next heading (+Shift
for previous)Control + Option + Command + L
— Next linkControl + Option + Command + G
— Next graphicControl + Option + Command + X
— Next list
Links
- VoiceOver Commands for Web Page Testing
- Using VoiceOver to Evaluate Web Accessibility
- Apple Accessibility
- iOS VoiceOver Gesture, Keyboard & Braille Shortcuts
Video list
- Accessibility: ARIA landmark roles
- Accessibility: labeling links
- Accessibility: extended descriptions for images
- Accessibility: focus styles
- Accessibility: skip links
- Accessibility: tools to help find issues
- Accessibility: validators
- Accessibility: VoiceOver
Supplemental links
- Dev.Mozilla: ARIA
- Simply Accessible
- WebAxe
- Paciello Group
- WebAim
- HTML5 Accessibility
- 456 Berea Street
- Accessibility Wins
- A11y Project
Articles
- Why Bother with Accessibility
- WebAim: Web Accessibility for Designers
- Design and Development: The Yin and Yang of Web Accessibility
- The Sound of the Accessible Title Text Separator
- Designing For The Elderly: Ways Older People Use Digital Technology Differently
- Accessibility and Low-Powered Devices
- The HTML5 Document Outline is a Dangerous Fiction
- Designing For Disabilities: Section 508 and International Accessibility Compliance For Beginners
- Top Mistakes in Web Accessibility
- Quick Tip Testing Web Content for Screen Readers
- User Testing for Web Accessibility
- Web writer’s accessibility checklist
- WCAG: Quick Reference
- Extending Semantics & Accessibility
- WebVTT and Video Subtitles
- Accessible Footnotes with CSS
- 7 Things Every Designer Needs to Know about Accessibility
- Notes on accessible CSS image sprites
- The Usability Principles, Accessibility Style, Part 2, Part 3
- Game Accessibility Guidelines
- Making Charts with CSS
- Why Your Links Need a Hover Effect
Videos
- How A Blind Person Uses A Computer
- How Blind People Use Twitter & You Tube on the iPhone 4S
- iPhone, iPad and Apple VoiceOver
- Christopher Hills: One Switch. One Head. The World.
- No Hands Ken
- WebAxe: Accessibility Videos
- Videos of Screen Readers Using ARIA
Books
- WebAxe: Free Online Books on Accessibility
- Paciello Group: Books
- InterACT with Web Standards, Chapters 22–24
Tools
- Color Contrast Analyser
- Contrast Ratio
- Tenon.io
- HTML5 Outliner
- HTML5 Outliner Chrome Extension
- Lynx Viewer
- A11y Command-line Tools
- Total Validator
Standards
Checklists
- WebAim: Checklist
- W3: Checklist
- Interactive WCAG 2.0
- WCAG 2.0 Checklist
- The Accessibility Cheatsheet