Web accessibility has long stopped being a niche topic for standards enthusiasts. Since 2025 it has become a direct legal obligation for part of the private sector, and at the same time a readable signal to customers, partners and investors alike. Companies that have so far treated web accessibility as a side concern are now facing a combination of legislative pressure and rising user expectations — and it pays to know exactly where the obligations end and where the real business benefits begin.
What web accessibility means and who it's for
Web accessibility means that a website or application can be used fully by as wide a range of people as possible — including those with visual, hearing, motor or cognitive impairments. It typically rests on four principles summarised by the acronym POUR: content should be perceivable, operable, understandable and robust across devices and assistive technologies.
It's important not to see accessibility as relevant only to a small group of users with permanent impairments. The same principles also help someone with a temporary limitation (a broken arm, bright sunlight on a screen), an older generation that navigates the web more slowly, or an ordinary mobile user with only one free hand. In practice, an accessible website is simply a better-quality website for everyone.
Legal requirements: from the public sector to private companies
The EU's legislative framework for accessibility rests on two pillars that differ in scope.
The first is (EU) 2016/2102, the directive on the accessibility of websites and mobile applications of public sector bodies. It has long applied mainly to central and local government, schools and public institutions, and requires websites to comply with the WCAG technical standard at level AA.
The second, far more relevant to private companies, is the European Accessibility Act — Directive (EU) 2019/882. It has been enforceable in practice since June 2025 and extends the accessibility obligation to selected private-sector products and services — for example e-commerce, banking and payment services, telecommunications services, e-books, or information systems used in passenger transport. If a company operates an online store, internet banking or a digital service falling into these categories, web accessibility is no longer a voluntary topic but part of legal compliance.
| Area | Public sector (Directive 2016/2102) | Private sector (European Accessibility Act) |
|---|---|---|
| Who it affects | central and local government, public institutions | e-commerce, banks, telecoms, e-books and other selected services |
| Reference standard | WCAG, level AA | WCAG, level AA |
| Effective since | long-standing obligation | enforceable in practice since June 2025 |
| Typical impact | audits, accessibility statements | compliance of products and digital services |
WCAG requirements: what level AA means in practice
The technical foundation of both regulations is the Web Content Accessibility Guidelines (WCAG), published by the W3C consortium. In practice, level AA conformance is most commonly required, covering dozens of specific criteria — for example:
- sufficient colour contrast between text and background,
- alternative text for images and non-text content,
- full keyboard operability without needing a mouse,
- clear labels and error messages in forms,
- captions and transcripts for video and audio content,
- a logical heading structure and semantic HTML for screen readers.
Most of these rules overlap well with the technical foundations companies address for other reasons too — for example website performance and speed. If you're planning to work on Core Web Vitals and website speed, it's a natural moment to also sort out the page's semantics and structure alongside accessibility — both topics rest on the same technical foundation.
Benefits of web accessibility for a business
Legal obligation is only one side of the coin. An accessible website also brings a company direct business advantages that are worth considering separately from the compliance agenda.
First, wider reach. A website that works with a keyboard, a screen reader, or enlarged text also reaches a segment of users who would otherwise quietly drop out of the conversion funnel — without it showing up in ordinary analytics as a specific reason for leaving.
Second, the link to SEO. Search engines evaluate a website using signals similar to those accessibility requires — a semantic heading structure, descriptive alternative text, clear links and clean HTML code. A company that invests in accessibility therefore improves its technical foundation for SEO at the same time, without having to make these changes twice.
Third, reducing legal and reputational risk. A complaint about an inaccessible website or product can now be filed formally, and companies operating in regulated industries (finance, telecommunications, e-commerce) should address this topic proactively rather than reactively after the first complaint.
Fourth, the quality of the product itself. Teams that get used to testing with a keyboard and a screen reader typically uncover broader usability issues too — unclear forms, inconsistent components, missing error states — that would otherwise remain hidden.
How to approach accessibility in practice
Rather than trying to fix "everything at once", it pays to proceed systematically.
- Audit the current state. A combination of automated tools and manual testing (keyboard, screen reader) reveals the most serious barriers.
- Prioritise by impact. Not every WCAG criterion carries the same weight — start where a barrier prevents completing a key action (purchase, registration, contact form).
- Build accessibility into the design system. If a company works with unified components, contrast, focus states and labels only need to be fixed once at the level of the design system, not separately on every page.
- Include accessibility in the QA process. Just like functional or performance testing, accessibility checks belong in the standard software testing process before launch.
- Use a redesign as an opportunity. If a company is planning a website redesign, it's a natural moment to build accessibility into the architecture from the start — it's easier than retrofitting it onto a finished solution.
A principle familiar from software development generally applies here: a problem caught at the design stage can be fixed with a design or component change. The same problem discovered only after launch usually requires touching already-live code, regression testing and cross-team coordination. The exact cost comparison differs from project to project and depends on the scope of the website, the technology, and how early the issue is caught — but as a general rule, addressing accessibility at the design stage is simpler than fine-tuning it on a finished product.
The same "deal with it earlier, not later" principle applies to other topics related to digital product regulation too — for example when deploying AI agents, where it's worth thinking through GDPR compliance before launch rather than after.
Summary
Web accessibility is no longer an optional add-on — for part of the private sector it has been a legislative obligation based on the WCAG standard since 2025, and it also brings real business benefits in the form of wider reach, a stronger SEO foundation and lower risk. The exact scope of changes always depends on the type of website, target audience and industry, so it's worth assessing individually. If you're not sure where your website currently stands and what a potential modernisation should deliver, we're happy to talk it through in a no-obligation consultation.