Web accessibility for SME websites: the 20% that covers 80%
Easy Insight Team ·
Start with the six failures automated scans find most: low-contrast text, missing image alt text, unlabelled form fields, empty links, empty buttons and a missing page language. WebAIM's February 2026 scan of a million home pages found 96% of detected errors in those six. Then test with a keyboard, which no scanner can do for you.
What are the most common accessibility failures?
Every year WebAIM runs an automated scan of the top one million home pages. The 2026 edition, run in February 2026, found detectable WCAG 2 failures on 95.9% of them, with an average of 56.1 errors per page, up from 51 the year before (WebAIM Million). The same six problems account for nearly all of it.
| Failure | Home pages affected (Feb 2026) | What it means for a visitor | Typical fix |
|---|---|---|---|
| Low-contrast text | 83.9% | Text is hard to read for people with low vision, or anyone on a phone in sunlight | Darken text or lighten backgrounds in the site's colour tokens |
| Missing image alt text | 53.1% | A screen reader announces nothing, or a file name | Describe images that carry meaning; mark decorative ones as decorative |
| Missing form input labels | 51% | Fields are announced as "edit text" with no clue what to type | Give every field a visible label tied to it in the code |
| Empty links | 46.3% | A link is announced with no purpose, often an icon or logo | Add text, or an accessible name, saying where it goes |
| Empty buttons | 30.6% | A button with only an icon has no name | Add an accessible name such as "Open menu" |
| Missing document language | 13.5% | Screen readers may read the page with the wrong pronunciation | Set the page language once in the site template |
Source: WebAIM Million, 2026 report (results from February 2026).
Why do six problems cover most of the work?
Because most failures come from a handful of habits repeated on every page. WebAIM reports that 96% of all errors it detected fall into those six categories. The Department for Work and Pensions' accessibility team says something similar from its own testing: most WCAG failures fall under the same 15 to 20 criteria (DWP Accessibility Manual).
That is where "the 20% that covers 80%" comes from. It is our rule of thumb, not a statistic. A short list of fixes, made once in the templates, deals with most of what goes wrong on a typical business site. Most of these failures are cheap to put right while a site is being built and tedious to find later. That is why accessibility belongs in a website redesign scope rather than a later phase.
How can you check your own site in an afternoon?
The DWP's basic checklist is the best free starting point we know of, and it is public. Run these checks on your homepage, your main service page and your contact form, as of November 2026:
- Run an automated checker. The DWP names ARC Toolkit, axe DevTools and WAVE. Each is a free browser extension. Fix what they flag first, starting with the six failures in the table.
- Put the mouse away. Use Tab, Shift+Tab, Enter and Space to reach every link, menu, button and form field. You should always be able to see where you are, and you should never get stuck inside a pop-up or cookie banner.
- Check contrast. The DWP's targets are 4.5:1 for normal text and 3:1 for large or bold text. Colour should never be the only way something is shown, such as a red border alone marking an error.
- Look at the headings. One H1 per page, no skipped levels, and headings that describe the section below them.
- Zoom in. Text should scale without breaking the layout, and at a 320-pixel-wide view the page should not need sideways scrolling.
- Submit the form with mistakes. Errors should be easy to spot and explained in words, not just colour.
The DWP is clear that completing its checklist does not guarantee full WCAG compliance. WebAIM says the same about automated tools: a page with no detected errors is not necessarily accessible. These checks find the common problems quickly. They do not prove the site is accessible.
What does WCAG 2.2 add for older sites?
WCAG 2.2 became a W3C Recommendation on 12 December 2024 and has three conformance levels: A, AA and AAA (W3C). It added new success criteria to WCAG 2.1, including minimum sizes for click and tap targets and making sure the element with keyboard focus is not hidden behind something like a sticky header or chat widget.
A site built before 2024 was tested against an older version, if it was tested at all. The two additions above are the ones a busy marketing site most often fails: small icon buttons in the header and footer, and sticky bars that cover whatever you tab to. When you brief an agency, name the standard. The questions to ask a web development agency include whether accessibility comes up unprompted.
Does UK law require an accessible website?
Not in the way many people assume. The Public Sector Bodies Accessibility Regulations 2018 require WCAG 2.2 AA and an accessibility statement, but they apply to public sector bodies, not private businesses (GOV.UK guidance, updated 30 September 2024).
What does apply to a business is the Equality Act 2010. Section 29(7) puts a duty to make reasonable adjustments on anyone providing a service to the public (legislation.gov.uk). GOV.UK's guidance says all UK service providers have that obligation. The Act does not mention websites, and how it applies to yours is a legal question we cannot answer for you.
If you sell online to consumers in the EU, the European Accessibility Act also lists e-commerce among the services it covers (European Commission). Check how it applies to your business with a specialist.
What does the other 80% involve?
The remaining work is less frequent but harder: captions and transcripts for video, accessible PDFs, complex widgets such as date pickers and carousels, and testing with a real screen reader. In our view, a small business site with a contact form and some service pages can get a long way with the checks above. A site with an online shop, bookings or a customer portal is worth a proper audit against WCAG 2.2 AA, because those flows are where a visitor who cannot finish the task simply leaves.
Accessibility work also overlaps with speed. Many of the same template fixes make a page lighter and easier to use, and Core Web Vitals for business websites covers the performance side.
What to do next
Run the six checks above on your three most important pages this week and fix the template-level problems first. If your platform makes the fixes hard, or you are planning a rebuild anyway, talk to us about website design and development across our web practice, or tell us about your site.
Frequently asked questions
Is website accessibility a legal requirement for UK small businesses?
The regulations that require WCAG 2.2 AA and an accessibility statement apply to public sector bodies, not private businesses. A business that provides services is under the Equality Act 2010 duty to make reasonable adjustments for disabled people. The Act does not mention websites, so how it applies to yours is a question for a lawyer, but WCAG 2.2 AA is the benchmark most organisations work to.
Which WCAG level should a small business aim for?
WCAG 2.2 Level AA. It is the level the UK public sector regulations require and the one most audits test against. Level A alone leaves out checks that matter to many visitors, such as minimum text contrast.
Can an automated checker make my site accessible?
No. WebAIM, which scans a million home pages each year, says not every failure can be detected automatically and that a page with no detected errors is not necessarily accessible. Use a checker to find the common failures quickly, then test by hand with a keyboard and zoom.
Do I need to fix every page one by one?
Usually not. Headers, footers, navigation, forms and buttons come from shared templates and components, so fixing the template fixes every page that uses it. Start with the templates behind your busiest pages, then deal with one-off content such as images and documents.
Easy Insight is a UK consultancy for AI, web, apps and data — senior specialists only, no juniors.
Next step
Thinking about a site or a web app?
One scoping call with the developer who would build it, then a fixed written estimate before any work starts. Websites from £3,500, custom web apps from £8,000, on the same stack as the page you're reading.

