94.8% of Websites Fail Accessibility Standards — Here's What Oxford Businesses Must Know

The WebAIM Million project tests the home pages of the world's top one million websites every year. In February 2025, it found that 94.8% had detectable failures against WCAG 2.2 Level A and AA — the accessibility standard that UK law increasingly expects websites to meet. That's an average of 51 distinct errors per page. Over 50 million barriers, on just one million home pages.

The number has improved. In 2024 it was 95.9%. In 2019, when the study began, it was 97.8%. But the pace of improvement is glacial against the scale of the problem — and against a regulatory environment that has shifted significantly in the past twelve months. The European Accessibility Act became enforceable on 28 June 2025, extending binding accessibility requirements to private sector businesses for the first time. The UK's Public Sector Bodies Accessibility Regulations now mandate WCAG 2.2 AA compliance, with the Government Digital Service actively monitoring and enforcing. The Equality Act 2010 has always applied to websites, and the direction of travel — in regulation, procurement, and public expectation — is unmistakably toward stricter enforcement.

This article explains who the law applies to, what the most common failures are, and what Oxford businesses can do about it — starting today.

Three laws, one requirement

Web accessibility in the UK sits under three overlapping pieces of legislation, and which ones apply to a given business depends on what it does and who it serves. But they all point in the same direction: websites must be usable by people with disabilities.

The Equality Act 2010 applies to every organisation in England, Scotland, and Wales that provides goods, services, or facilities — which includes websites. Section 20 requires service providers to make "reasonable adjustments" to avoid disadvantaging disabled people. Section 29 prohibits discrimination in the provision of services. The Equality and Human Rights Commission's statutory Code of Practice explicitly identifies websites as services, and government guidance now specifies WCAG 2.2 Level AA as the benchmark for compliance.

There is no exemption for small businesses, and the duty is anticipatory — meaning businesses are expected to identify and address barriers before a disabled person encounters them, not in response to a complaint. No UK court has yet delivered a landmark website accessibility ruling under the Equality Act, but the RNIB has initiated and settled multiple cases, and legal commentators widely regard a high-profile test case as a matter of when, not if. The cost of defending such a case runs into tens of thousands of pounds regardless of outcome (Oxford Academic / Current Legal Problems, 2025).

The Public Sector Bodies Accessibility Regulations 2018 (PSBAR) apply to all public sector organisations, including universities, NHS bodies, local councils, and their suppliers. The regulations require WCAG 2.2 AA compliance, the publication of a detailed accessibility statement, and participation in GDS monitoring. This is directly relevant to Oxford, where the university, its 39 colleges, the NHS, and the county and city councils are major employers and procurers of services. Any business working with or supplying to these institutions should understand that accessibility is a procurement criterion, not a suggestion.

The European Accessibility Act (EAA) became enforceable across all EU member states on 28 June 2025. It applies to any organisation — regardless of where it is based — that provides products or services to consumers in the EU. This catches UK businesses with eCommerce sites selling into the EU, booking platforms accessible to European visitors, and any digital service used by EU citizens. The EAA requires WCAG 2.2 Level AA compliance. Penalties are set at national level and vary: some member states have established fines up to €250,000 or percentage-based penalties, with daily accumulating fines for persistent non-compliance (AbilityNet, 2025). There is no grace period for businesses that missed the June 2025 deadline.

A small business exemption exists under the EAA for organisations with fewer than 10 employees and annual revenue below €2 million. But even for exempt businesses, the Equality Act still applies domestically, and the reputational and commercial arguments remain.

What GDS monitoring actually found

The Government Digital Service published its second accessibility monitoring report in December 2024, covering 1,203 public sector websites and 21 mobile apps tested between January 2022 and September 2024. The findings are instructive — not just for public sector organisations, but for any business that wants to understand what accessibility failures look like in practice.

GDS found 29,787 accessibility issues across the monitored sites and apps. Of these, 16,482 (55.3%) were fixed during the monitoring process. But 3,693 issues — 12.4% — remained unfixed at retest. Only 68% of organisations had fully addressed their issues or committed to short-term plans by the time of the retest, up from 59% in the previous reporting period.

The most common issues GDS found were: insufficient colour contrast between text and background, which affects people with visual impairments; lack of visible focus indicators, which affects keyboard and screen reader users; problems navigating with a keyboard alone, which affects users who cannot operate a mouse; and failure to reflow content when the browser window or device size changes, which affects users who rely on magnification or specific screen orientations.

For public sector bodies, the consequences of non-compliance are concrete. GDS sends audit reports directly to organisations, gives them 12 weeks to fix issues, and retests. Unresolved cases are referred to the EHRC, which has sent enforcement letters to 93 public sector bodies in England and Wales since January 2022. Compliance was secured with 66 of those without further action. For the remainder, the EHRC can enter binding agreements or launch formal investigations.

The relevance to private sector businesses is indirect but significant. If public sector procurement teams are being told their websites must meet WCAG 2.2 AA, they will increasingly expect the same of their suppliers and partners. Oxford businesses that work with the university, the NHS, or local government ignore this at their commercial peril.

The six errors that account for nearly everything

WebAIM's 2025 analysis identified that just six categories of error accounted for 96% of all detected failures across one million home pages. Understanding them matters because most are straightforward to fix — which makes their persistence all the more difficult to justify.

Low contrast text was found on 79.7% of home pages. This means text that doesn't have enough visual difference from its background for people with visual impairments to read it. WCAG requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Light grey text on a white background — a common design choice — routinely fails this threshold.

Missing alternative text for images affected pages with 18.5% of all images lacking alt text entirely — down from 21.6% in 2024, but still meaning roughly one in five images are invisible to screen reader users. Of those that did have alt text, 13.4% had questionable or repetitive values like "image", "graphic", "blank", or a file name. Nearly half of images missing alt text were linked images, meaning the link destination was entirely undescribed.

Missing form input labels means that form fields — name, email, phone number, enquiry details — lack the programmatic labels that tell screen readers what each field is for. A sighted user sees the word "Email" above a text box. A blind user hears nothing, or hears "edit text" with no context. For any business whose website includes a contact form, booking form, or checkout process, unlabelled inputs create a barrier at exactly the point where the user is trying to become a customer.

Empty links are links that contain no accessible text — often icon-only social media links or image-based navigation without alt text. A screen reader announces "link" but cannot describe where the link goes.

Empty buttons operate on the same principle. A button that submits a form, opens a menu, or triggers an action, but has no accessible name. "Button" is all the user hears.

Missing document language means the HTML page doesn't declare its language (typically <html lang="en"> for English). Screen readers use this declaration to select the correct pronunciation engine. Without it, a French screen reader might attempt to read English text using French phonetics, or vice versa. It's a single line of code, and its absence affects every word on the page.

These six issues — contrast, alt text, labels, empty links, empty buttons, and language declaration — are not edge cases. They are the overwhelming majority of the problem. They are also, without exception, fixable without redesigning a website. Most can be addressed in hours rather than days.

The commercial case beyond compliance

The legal case for accessibility is clear but, in the UK, underenforced. The commercial case is arguably more immediately compelling.

More than one in five people in the UK — 16.1 million — have a disability (GDS, 2024). Tourism spending by those with an impairment, or travelling within a group where someone has one, reached an estimated £14.6 billion annually in England alone, with an average spend per inbound visit of £863 — higher than the £819 average across all trips (VisitBritain, 2024). For Oxford, where the visitor economy reached £2.4 billion in 2024 and international overnight stays grew 5%, the accessibility of tourism websites is not an abstract concern — it directly determines whether a significant segment of higher-spending visitors can find and book local services.

The Click-Away Pound survey — the most substantive UK research into the online shopping behaviour of disabled consumers, last conducted in 2019 — found that 71% of disabled customers will leave a website they find difficult to use. 73% experienced barriers on more than a quarter of websites they visited for the first time. 85% limit their shopping to sites they already know are accessible. And 82% said they would spend more if websites were more accessible (Click-Away Pound, 2019).

Perhaps most revealing: only 8% of disabled customers who have difficulty using a site will contact the business about it. The other 92% simply leave. A business with an inaccessible website is losing customers it will never know about — and the behavioural pattern behind that finding is unlikely to have improved in the years since, given that WebAIM's data shows only marginal improvement in actual website accessibility over the same period.

Where education faces the sharpest edge

Oxford's education sector sits at the intersection of all three pieces of accessibility legislation — and faces additional scrutiny that most private businesses do not.

Universities and colleges are public sector bodies under PSBAR, which means WCAG 2.2 AA compliance is a legal requirement, not a best practice aspiration. GDS monitors and audits university websites, and the EHRC can enforce compliance. The December 2024 GDS report noted that monitoring had expanded beyond main websites to include secondary sites such as recruitment platforms — meaning institutions can no longer assume their primary site is the only one being assessed.

For Oxford's estimated 24 to 29 English language schools, the accessibility challenge is particularly acute. These schools recruit internationally, primarily through their websites. Prospective students in the EU are now protected by the EAA, meaning a language school's website is subject to enforceable accessibility requirements if it accepts enrolments from European countries. Many language school websites — built on aging platforms with limited mobile optimisation — are unlikely to pass even a basic WCAG assessment.

Document accessibility is an area where educational institutions consistently underperform. PDFs, course brochures, application forms, and timetables are frequently published as scanned images or untagged PDFs that are entirely inaccessible to screen readers. The GDS report specifically highlighted document accessibility as a recurring concern. For a language school whose entire admissions process relies on downloadable PDFs, this isn't a minor compliance gap — it's a barrier that prevents disabled applicants from applying at all.

eCommerce after the European Accessibility Act

For Oxford businesses selling products or services online — whether that's a retailer with an eCommerce shop, a tour operator selling tickets, or a consultant offering bookable services — the EAA has changed the compliance landscape.

Before June 2025, UK private sector businesses had an accessibility obligation under the Equality Act, but enforcement was effectively non-existent. The EAA introduces a different regime for anyone serving EU customers. Enforcement is handled at national level by each EU member state, meaning a UK business selling into France, Germany, and Ireland could theoretically face separate investigations and penalties in each jurisdiction. Some member states have established fines ranging from €5,000 to €250,000, with daily penalties for persistent non-compliance.

The EAA also introduced a formal requirement for accessibility statements — similar to those already required of UK public sector bodies under PSBAR. A compliant statement must document the current accessibility status of a website, acknowledge known barriers, and explain what steps are being taken to address them. Generic statements copied from templates, or those generated by accessibility overlay tools, do not satisfy the requirement.

Accessibility overlays — JavaScript widgets marketed as instant accessibility fixes — deserve specific mention because they are widely sold and widely ineffective. These tools typically add a toolbar to a website that offers features like increased text size or high contrast mode. They do not fix underlying code issues and cannot make a genuinely inaccessible website accessible. Multiple disability organisations, including the National Federation of the Blind, have publicly opposed overlay products. The EAA explicitly requires accessibility to be built into the design and code of digital products, not bolted on as an afterthought.

What accessible design actually does for SEO

There is a practical overlap between accessibility best practice and search engine optimisation that is worth understanding, because it means accessibility improvements often deliver measurable commercial returns beyond compliance.

Descriptive alt text for images serves both screen readers and search engines. Google cannot see images — it reads alt text to understand what an image depicts. A product photo with alt="blue merino wool jumper, size medium" is simultaneously accessible and optimised for image search. A product photo with alt="" or alt="IMG_4582.jpg" fails on both counts.

Semantic HTML — using heading tags (H1, H2, H3) in a logical hierarchy, using list elements for lists, using landmark regions for navigation — helps screen readers parse page structure and helps search engines understand content hierarchy. A page that uses <div> tags for everything looks the same visually but is both less accessible and harder for Google to interpret.

Keyboard navigability — ensuring every interactive element can be reached and operated without a mouse — correlates with the kind of clean, well-structured code that search engines reward. Pages bloated with JavaScript that breaks keyboard navigation tend to be the same pages that load slowly and score poorly on Core Web Vitals.

As we examined in our previous article on what one second of load time costs Oxford businesses, website performance is a direct commercial variable. Accessibility improvements frequently improve performance by the same mechanism: cleaner code, smaller page weight, fewer unnecessary scripts, and better-structured content. The two disciplines are more complementary than most businesses realise.

A self-audit checklist: where to start today

A full accessibility audit requires specialist expertise, but a business can identify the most significant issues on its own website in under thirty minutes using free tools. This is not a substitute for a professional assessment — automated testing catches only an estimated 20–30% of accessibility issues — but it establishes a baseline and identifies the quick wins.

Run WAVE on your home page and one key conversion page. WAVE (wave.webaim.org) is a free browser extension developed by WebAIM. It highlights errors, contrast failures, and structural issues directly on the page. Focus on the red error flags first — these are the issues most likely to create genuine barriers.

Check your colour contrast. Use WebAIM's free contrast checker (webaim.org/resources/contrastchecker) to test your main text colour against your background. You need at least 4.5:1 for body text and 3:1 for large text (18px or above, or 14px bold). If your brand palette fails, you don't need to change your brand — you need to adjust how it's applied to text.

Test with your keyboard only. Close your mouse. Tab through your home page. Can you see where the focus is at all times? Can you reach the navigation menu, click links, fill in forms, and submit them? Can you open and close any dropdown menus or popups? If you get stuck at any point, a keyboard user will get stuck at the same point.

Check your images. Right-click any image on your site, select "Inspect", and look for the alt attribute. If it says alt="" on a meaningful image, or is missing entirely, that image is invisible to screen readers. Every image that conveys information needs a concise, descriptive alt text. Decorative images should have alt="" explicitly set to tell screen readers to skip them.

Review your forms. Every input field should have a visible label that is programmatically associated with the field. Placeholder text — the grey text inside a form field that disappears when you click — does not count as a label. Check that error messages are clear, specific, and announced to screen readers.

Check your page language. View the source code of your home page and look for <html lang="en"> (or whichever language your site is in). If the lang attribute is missing, add it. This is a single-line fix that affects every screen reader user on every page.

Test your PDFs. Open any PDF published on your site and try selecting the text. If you can't select it — if the PDF is essentially a photograph of a document — it is completely inaccessible. Tagged, text-based PDFs are the minimum requirement. Better still, consider whether the content needs to be a PDF at all, or whether it could be published as a web page.

Check your accessibility statement. If you're a public sector body, you must have one. If you're a private business, it's not legally required under the Equality Act but is best practice and is required under the EAA if you serve EU customers. A good accessibility statement acknowledges known issues, explains what you're doing about them, and provides a way for users to report problems. The honest version — "we know these things aren't perfect and here's our plan" — is worth more than a generic template that claims compliance.

The compound effect — again

We made this point in our analysis of website performance, and it applies equally here. Accessibility is not a standalone metric. It interacts with, and amplifies, every other aspect of a website's commercial effectiveness.

A website that is inaccessible excludes 20% of the UK population from the outset. Marketing spend that drives traffic to an inaccessible site wastes a proportion of every pound spent. SEO improvements that increase organic visibility are undermined if the resulting traffic encounters barriers. A beautifully designed eCommerce experience that cannot be navigated with a keyboard is invisible to the users who might most benefit from being able to shop online rather than in a physical store.

Conversely, an accessible website converts more of its traffic — not just disabled visitors, but everyone. Clear headings, readable text, well-labelled forms, fast load times, and logical navigation benefit every user. The same changes that make a site accessible to a screen reader user make it easier for a mobile user on a slow connection, a desk-bound user switching between tasks, and a 65-year-old who just needs the text to be a bit larger.

In Oxford's market — where knowledge-intensive businesses set high digital expectations, where international visitors arrive via mobile on variable connections, and where the university and public sector set procurement requirements that ripple through the supply chain — accessibility is not a compliance burden to be minimised. It is a competitive position to be occupied.

The data is clear. The regulatory direction is clear. The commercial incentive is clear. The only question is how long a business waits before acting.

Oxford Web Services has been building accessible websites for Oxford businesses for over 20 years. If you'd like to know where your site stands, get in touch for a free accessibility review.

Sources

All statistics cited in this article are drawn from publicly available, verified sources:

• WebAIM — The WebAIM Million: 2025 report on the accessibility of the top 1,000,000 home pages (February 2025)
• WebAIM — 2024 report and year-on-year comparisons (February 2024)
• Government Digital Service (GDS) — Accessibility monitoring of public sector websites and mobile apps from 2022 to 2024 (December 2024, GOV.UK)
• AbilityNet — European Accessibility Act guidance and compliance resources (2025)
• Taylor Wessing — "The UK's regulatory approach to accessibility" (May 2025)
• Oxford Academic / Current Legal Problems — "Accessibility and the Limits of the Equality Act 2010" by Anna Lawson (Volume 78, 2025)
• Disability Rights UK — Accessibility Act campaign and legal analysis
• Pinsent Masons — "Disabled access to websites under UK law" (October 2025)
• We Are Purple / DWP — UK disability population and household data
• VisitBritain — Purple Pound tourism expenditure data (£14.6 billion annually, average spend per visit; November 2024)
• Click-Away Pound — 2019 survey: online shopping experience of people with disabilities (behavioural data: 71% click-away rate, 73% encountering barriers)
• Equality and Human Rights Commission — Statutory Code of Practice for services, public functions and associations
• GOV.UK — Understanding accessibility requirements for public sector bodies (updated September 2024)
• GOV.UK — Public sector website and mobile application accessibility monitoring methodology
• Bird & Bird — UK accessibility requirements for websites and mobile applications (2025)
• Accessibility Audit UK — European Accessibility Act 2025 UK enforcement analysis (January 2026)