What web accessibility means, why it matters for your customers and your business, and a practical checklist of the fixes that make the biggest difference, most of which you can check yourself in an afternoon.
An accessible website is one that people can use whatever their abilities and however they browse: with a screen reader, with a keyboard instead of a mouse, zoomed in to 200%, with colour blindness, with a tremor that makes small targets hard to tap, or simply on a phone in bright sunlight. The W3C's introduction to web accessibility is a good, short overview.
Accessibility is not a special version of your site. It is mostly good, careful building: clear structure, readable text, forms that explain themselves, and nothing that only works with a mouse.
The Web Content Accessibility Guidelines (WCAG) are the international standard. They are organised around four principles: content must be perceivable (people can see or hear it), operable (people can use it with the tools they have), understandable (it behaves predictably and explains itself) and robust (it works with assistive technology).
Each guideline has success criteria at three levels: A, AA and AAA. Level AA is the usual target for business websites and the level most laws and policies refer to. WCAG 2.2 is the current version.
These checks catch many of the most common problems. You need no special software beyond your browser.
lang="en"), so screen readers pronounce it correctly.For an automated first pass, free tools such as the accessibility audit in Chrome's Lighthouse or the WAVE checker point out missing alt text, low contrast and empty links. They catch only part of the problems, so combine them with the keyboard test above.
Some products promise to make any site accessible with one line of JavaScript, adding a toolbar or automatic fixes. They cannot fix problems in the underlying code (missing labels, wrong heading structure, keyboard traps), and some users of assistive technology find they get in the way. Fixing the site itself is more reliable. The W3C's guidance on evaluation tools is a good reference for what automated tools can and cannot do.
Accessibility is far cheaper when it is built in than when it is added later. When you plan a new site or a redesign:
Accessibility is one of the checks in our website launch checklist, and part of how we approach website development.
Accessibility is good practice for every site, and in many places businesses that serve the public are expected to provide accessible websites. The exact legal requirements depend on where you operate and who your customers are; for a definite answer about your obligations, ask a lawyer.
They are levels of conformance. Level A covers the most basic barriers, AA adds the requirements most organisations aim for (such as contrast ratios), and AAA is the strictest and is not usually required for whole sites. Aim for AA.
Not completely. Automated tools reliably find issues such as missing alt text or low contrast, but they cannot judge whether alt text is meaningful, whether the reading order makes sense, or whether a form is usable with a keyboard. Use them as a first pass and test by hand as well.
Building it in from the start adds relatively little, because most of it is careful markup and design. Retrofitting an existing site varies: some fixes (alt text, labels, contrast) are quick, while a theme with deep structural problems may be cheaper to rebuild during a redesign.
Many accessibility practices also help search: descriptive headings, alt text, meaningful link text and fast, stable pages make your content easier for search engines to understand. Accessibility is worth doing for people first, with SEO as a side benefit.
Planning a new site or a redesign? See how we approach website development, or read SEO basics for small business websites.