My notes for making the web more inclusive. Don't follow this guide blindly. Read the references to learn more about certain rules.
Check out my general best practices for building better applications.
This page is a continuous work in progress.
To evaluate the accessibility of a web page, try out the following tools:
- WCAG Quick Reference
- WAI-ARIA Authoring Practices 1.2
- A11y Reviews (GitHub)
- Accessibility interview questions
- IBM Accessibility Checklist 7.1
- Accessibility motivation
- Web accessibility means that the site's functionality can be operated by literally anyone, including people with impairments or disabilities.
- Disability accommodations often benefit everyone, not just disabled people. Think about wheelchair ramps: parents pushing a stroller, someone walking a bicycle, or someone towing a heavy load on wheels.
- Provide a correct lang attribute.
- Ensure that interactive controls have at least a 44×44 pixels target click size.
- Accessible, responsive canvas.
- a11y-dialog - Accessible JS modal dialog.
- Comica11y - accessible comics.
- PDF Accessibility Checker (PAC)
- Accessibility tools audit — An example page to test the effectiveness of accessibility tools.
- There are multiple issues with AccessiBe and other overlays.
- Building the most inaccessible site possible with a perfect Lighthouse score.
- The WebAIM Million - An annual accessibility analysis of the top 1,000,000 home pages.
- Losing sight.
- I'm a software engineer going blind, how should I prepare?.
- A blog where the author describes their way to become certified in WAS and CPACC.
- It is okay to use the word "disabled".
- Consider different implementation techniques.
- The focus indicator must have a contrast ratio of 3:1 against its adjacent elements, or be at least 2px wide. (WCAG 2.2)
- The focus indicator must have a 3:1 (AA) / 4.5:1 (AAA) contrast ratio between its focused and unfocused states. (WCAG 2.2)
- It is not required that hover as a state is differentiated from the default (and presumably all other) states.
- Adjusting the flex order does not change the focus order.
- Provide a fallback for Windows High Contrast mode when using a
- A keyboard-only focus ring has pros and cons, but it is technically possible using
:focus-visible. Progressive enhancement handles older browsers.
- Enable proper tab behavior on Mac
- ☑ System Preferences → Keyboard → Shortcuts → Accessibility → Full Keyboard Access → All controls
- ☑ Safari Preferences → Advanced → Press Tab to highlight each item on a webpage
- Alt-Texts — The Ultimate Guide.
- Add punctuation to your alt text.
- There are limitations of
aria-describedby. It's complicated.
- Google Translate does not translate
aria-labellabels. Sometimes it does.
- HTML for vs wrapping label.
- There's no evidence that typefaces designed to help dyslexics have any effect.
- Accessible font types.
- Atkinson Hyperlegible Font.
- Eleventy starter for WCAG reports
- WCAG-compliant website showcase
- Rules for using ARIA.
- An in-depth guide to ARIA roles.
- Boolean ARIA attributes behave differently than HTML Boolean attributes:
required="foo"have the same effect and mark the referenced element as "required".
aria-required="false"consider the used value (either "true" or "false").
passwordrole is under discussion.
role="none"is not supported in IE11.
- Do not put
aria-hiddenon focusable elements.
- Keyboard shortcuts need modifier keys.
aria-descriptionis in W3C Editor's Draft for ARIA 1.3, but some browsers already support it.
- Using tabs over spaces in code is more accessible to braille device users.
- NVDA Keyboard Shortcuts
- User survey 2019 (browser/screen reader usage)
- Do not use screen reader detection.
- Screen reader icon (public domain):
- A screen reader may announce things differently than displayed in the text viewer. Pay attention to times, dates, currency, punctuation, special characters, emoji, math symbols, common (and uncommon) abbreviations & acronyms.
- Screen reader's punctuation announcement depends on its order, e.g. NVDA announces question marks only at the end of a sentence by default.
- Minus the minus - A PSA about screen readers and negative numbers.
- NVDA has fixed a related issue.
- Talkback doesn't recognize the
- Acronyms can usually be left as-is.
- NVDA announces values differently between divs and spans.
- NVDA does not announce emphasis elements (like
- Superscript and subscript are announced inconsistently.
- Improve the announcement of phone numbers:
<a href="tel:70355512" aria-label="7 0 3. 5 5 5. 1 2.">(703) 555-12</a>
::aftercontent is screen reader accessible (except IE11).
- CSS generated content is not fully accessible.
- How the
- German gender characters are not excluding screen reader users.
- For a live region to announce its content changes:
- The live region should be available in the DOM before changing the content.
- The live region must not be hidden (e.g. via
- ☑ Tools → Speech viewer
- ☑ Show Speech Viewer on Startup
- ☑ Preferences → Keyboard → Select NVDA Modifier Keys → caps lock
- ☑ Tools → Speech viewer
- NVDA does not focus inline links in browse mode, unless the link appears at the start of a line.
- ☐ Verbosity → Hints → Speak instructions for using the item in the VoiceOver cursor
- ☑ Sound → Mute sound effects
- Dragon does not support wrapping labels for inputs.
- HTML: The Inaccessible Parts.
- Avoid the strikethrough element, as the semantics are not announced by screen readers.
- Use buttons for actions and links for links.
- If it makes sense to "open in new tab", then it should be a link. Otherwise, it's a button.
Something I see (...) is the frustration with date fields that are anything other than a plain text field for well-known dates (like birthdays).
<dd>Black hot drink</dd>
<dd>White cold drink</dd>
It's worth noting that a definition list is the correct way to mark up a list of paired items. Changing markup patterns to satisfy the vagaries of specific assistive technologies tends to be a slippery slope. (source)
- There is no fixed rule where the focus should be moved to after opening a modal. A headline or the dialog itself are two good possibilities. There is an ongoing discussion about the default behavior for the HTML
- Read about using legend and fieldset.
legendhas to be a direct child of a
fieldset. A screen reader might not announce the label if the markup is malformed (e.g. NVDA). Solutions:
- Use a duplicate label
- There was a Chrome bug, making it impossible to adjust the
There are some rules regarding the
- The HTML footer element defines a
contentinfolandmark when its context is the body element.
- The HTML footer element is not considered a contentinfo landmark when it is a descendant of any of following elements:
- An H1 doesn't have to come first (example).
- These are no WCAG violations, but should still be avoided:
- Missing or more than one
- Skipping heading levels.
- Multiple headings with the same text.
- Missing or more than one
- Decorational images:
We tried to outsmart screen readers by letting them skip descriptive images. This turned out to be really unhelpful. Users that are not fully blind will still see an image and when the screen reader skips these images, users will assume they missed out on information. Solution: let the screen reader tell the users it’s a descriptive image. Or even better, write a descriptive alt-text for images. source
- Background images are mostly ignored in Windows High Contrast mode.
type="search"for search inputs, even though it currently offers little benefit.
- The perfect link
- Links don't require an underline effect when using a contrast ratio of 3:1 and a visual cue on focus. It is still recommended to use a visual cue other than color.
- Icon-only links fail WCAG 2.4.4.
- Accessible anchor links
- Mark links that open in a new window:
<span id="new-window-0">Opens in a new window</span>
<span id="new-window-1">Opens an external site</span>
<span id="new-window-2">Opens an external site in a new window</span>
- Download links:
<a>, not a
- Provide media type and file size visually readable.
- The trouble with mailto email links and what to do instead.
- There is a difference when pressing Enter or Space with buttons:
- A native
<button>fires on key down when that key is
Enter. If you hold down the
Enterkey, it continues to fire for as long you hold
Enter(or something crashes).
- A native
<button>fires on key up when that key is
Space. If you do not release the
Space, and also press
Tabto move away from the control, the control will not fire.
- A native
- Whether the pointer cursor applies to buttons is controversial.
<path d="..." />
- Safari [removes list semantics] for
- Include a table caption:
<caption>Populations of cities</caption>