Imagine you own the best shop on the high street, with a beautiful storefront and curated products, but the entrance has a forty-centimeter step. Anyone using a wheelchair, parents with a stroller, or a customer on crutches will simply walk past. The same thing happens online every day: gorgeous websites that millions of people cannot enter. Web accessibility is, in essence, removing that step.
In 2026, this is no longer a recommendation or a nice-to-have. It is law. Directive (EU) 2019/882, known as the European Accessibility Act, came into full effect on June 28, 2025, and now governs much of the private sector. If you run a website, an app, an online shop, or a digital banking service, this article explains what you must comply with, why, and how to do it without losing your mind.
What exactly is web accessibility?
Web accessibility is the set of techniques, standards, and design decisions that ensure anyone can perceive, understand, navigate, and interact with a website regardless of their physical, sensory, cognitive, or technical abilities. It is not just “for blind users.” It is for everyone.
The reference standard is WCAG (Web Content Accessibility Guidelines), developed by the W3C. Three versions coexist in 2026: WCAG 2.1 (the legal baseline in many regulations), WCAG 2.2 (released in October 2023, now the practical reference), and WCAG 3.0 (still in draft). When someone tells you “we comply with WCAG,” always ask which version and which level.
Back to the analogy: if your website were a building, WCAG would be the building code’s accessibility chapter. It tells you the door width, the corridor clearance, the contrast of the exit sign, and the height of the counter. Accessibility is not aesthetics. It is structure.
Why web accessibility matters in 2026
Three reasons reinforce each other: human, economic, and legal. Any one of them on its own should be enough; together they make accessibility an obvious strategic decision.
Human reason: we are talking about a lot of people
According to the World Health Organization, around 16 % of the world population lives with a significant disability. That is roughly 1.3 billion people. The European Union alone has approximately 87 million people with disabilities. The CDC estimates that 1 in 4 adults in the United States has a disability. Add ageing-related functional losses and you get a vast group of users.
And here is what most people miss: accessibility also helps users with temporary disabilities (a broken arm, eye surgery) or situational disabilities (sunlight on the screen, ambient noise muting your video, a slow connection in a rural area).
Economic reason: the cost of being inaccessible
An inaccessible website excludes potential customers. The British Click-Away Pound study estimated that inaccessible websites lose billions of pounds every year because users with disabilities simply switch to competitors. If you exclude 15 % of your audience, you are giving away revenue.
Key data: WebAIM analyzes the world’s top one million home pages every year. In its 2025 report, 95.9 % of pages had detectable accessibility errors, with an average of 51 errors per page.
Legal reason: it is no longer optional
Since June 28, 2025, digital accessibility is mandatory for a very large share of the private sector across the European Union, thanks to Directive (EU) 2019/882. The public sector was already covered by Directive 2016/2102. In 2026, every major actor in the digital ecosystem operates under this legal umbrella. Outside the EU, parallel regimes apply (ADA Title III in the United States, AODA in Ontario, accessibility regulations in the United Kingdom).
Who must comply with web accessibility
The right question in 2026 is no longer “who is affected” but “who is not.” Only a few cases remain outside, and you should know them.
| Type of organization | Obligation in 2026 |
| Public sector (administrations, universities, agencies) | Required since 2018-2020 under WAD. Must meet WCAG 2.1 AA and publish an accessibility statement. |
| Private companies offering digital services to EU consumers | Required since June 28, 2025 under EAA: ecommerce, banking, transport, e-books, audiovisual services. |
| Microenterprises providing services | Exempt if <10 employees AND turnover/balance <EUR 2M (cumulative criteria). |
| Microenterprises manufacturing products | NOT exempt. Any covered product must comply. |
| Pure B2B companies with no consumer service | Outside EAA scope, but may be obliged through contracts and supplier requirements. |
When web accessibility applies: key dates
If I had to draw the timeline, this is the summary of the milestones already reached by April 2026 and those still ahead.
| Date | Milestone |
| 1999 | WCAG 1.0 published by the W3C. |
| 2008 | WCAG 2.0 published, the foundation for European laws. |
| December 2016 | Directive (EU) 2016/2102 (Web Accessibility Directive) for the public sector. |
| June 2018 | WCAG 2.1 published. |
| April 2019 | Directive (EU) 2019/882 (European Accessibility Act, EAA) approved. |
| September 2020 | Public sector deadline: WCAG 2.1 AA + accessibility statement. |
| October 2023 | WCAG 2.2 becomes a W3C Recommendation. |
| June 28, 2025 | Full application of the EAA. Covered private sector must comply. |
| 2030 | End of the transition period for products and services already on the market in 2025. |
Where it applies: territory, sectors and exceptions
The territory is straightforward: the entire European Union plus the EEA. If your company is based outside the EU but offers products or services to European consumers, you are also in scope.
Products and services covered by the EAA
- General purpose computer hardware and operating systems: PCs, tablets, smartphones, system software.
- Self-service terminals: ATMs, ticket machines, check-in kiosks at airports.
- Telecommunication equipment and services.
- Audiovisual media services and access services (smart TVs, set-top boxes, streaming platforms).
- Consumer banking services: online banking, mobile apps, e-identification.
- E-commerce: online stores, marketplaces, booking platforms.
- E-books and dedicated reading software.
- Passenger transport services in their digital components: websites, apps, ticket machines, real-time information panels.
Disproportionate burden and reasonable exceptions
The EAA allows businesses to claim a “disproportionate burden” when a specific adaptation would be excessively costly relative to their size and resources. It is not a free pass: the analysis must be documented and reviewed at least every five years. The same applies to “fundamental alteration” when accessibility would force a redesign of the product itself.
Note: disproportionate burden cannot be invoked when public funds explicitly earmarked for accessibility have been received. And it never removes the obligation to inform users about the limitations.
How to make a website accessible: the four POUR principles
WCAG organizes everything under four principles. If you internalize them, you have the bulk of the job covered. The mnemonic is POUR: Perceivable, Operable, Understandable, Robust.
1. Perceivable
All information must be perceivable through at least one of the senses. This includes text alternatives for images (success criterion 1.1.1), captions for video (1.2.2), audio description (1.2.5), a 4.5:1 contrast ratio for normal text (1.4.3), and the ability to resize text up to 200 % without loss of functionality.
2. Operable
Users must be able to operate the website with any input method, not just a mouse. The keyboard must always work (criterion 2.1.1), the tab order must be logical (2.4.3), users must have enough time to read (2.2.x), and nothing should flash dangerously (2.3.1, photosensitive epilepsy).
3. Understandable
The content and behavior must be predictable. This covers declared language (3.1.1), predictable navigation (3.2.x), clear form labels (3.3.2), and error correction help (3.3.3, 3.3.4).
4. Robust
The code must be compatible with current and future assistive technologies (screen readers, refreshable braille displays, voice control software). In practice this means valid HTML, correct ARIA, and accessible names/roles/values for components (criterion 4.1.2).
A, AA and AAA conformance levels
| Level | Criteria covered | Use case |
| A | 30 criteria. Bare minimum. | Old regulations only. Not enough for the EAA. |
| AA | 55 criteria (A + new ones). | The level required by EAA, EU WAD and most national laws. Mandatory. |
| AAA | All criteria. | Excellence. Recommended for essential public services and content for vulnerable groups. Cannot be applied globally because some criteria conflict. |
How to assess your website: methodology and tools
A serious evaluation combines three layers. Skipping any one of them is like a medical check that only takes your temperature: you feel reassured while the disease quietly progresses.
Layer 1: automated testing
Tools such as axe DevTools, Lighthouse, WAVE, Pa11y, or Siteimprove detect between 25 % and 35 % of real issues: contrast, missing attributes, broken heading hierarchies. Fast and cheap, but it gives a false sense of safety if you stop here.
Layer 2: expert manual review with WCAG-EM
A trained evaluator examines criteria no bot can verify: whether alt text is semantically correct, whether forms are understandable, whether the logical order makes sense. For large sites, the W3C’s WCAG-EM (Website Accessibility Conformance Evaluation Methodology) defines how to sample representative pages.
Layer 3: usability testing with real users
The layer most people skip. Putting people with visual, motor, or cognitive disabilities in front of your website surfaces findings no software can. If you want grounded data, this is the only honest approach.
Penalties for non-compliance
Let me be blunt: penalties exist, they are serious, and they are starting to be applied.
-
- Each Member State sets its own sanction regime under the EAA. Fines for very serious infringements can reach hundreds of thousands of euros.
-
- Indirect consequences include product withdrawal, suspension of activities, and the obligation to compensate affected individuals.
-
- Lawsuits in the United States have demonstrated the cost of inaccessibility: the case of Robles v. Domino’s Pizza is a frequently cited precedent.
- Reputational damage is often the most expensive penalty: a public ruling on discrimination harms the brand for years.
Who is responsible inside the organization
Accessibility is not the job of “whoever built the website.” It is a team effort.
-
- Leadership and compliance: define scope, allocate budget, and sign the public accessibility statement.
-
- UX/UI design: integrate accessibility from the wireframe stage, not as an afterthought. Contrast, minimum sizes, and alt text decisions originate here.
-
- Front-end development: implement semantic HTML, correct ARIA, and maintain assistive technology compatibility.
-
- Marketing and content: write understandable copy, correct alt text, and avoid inaccessible PDFs.
-
- Quality assurance: integrate accessibility tests into CI/CD and pre-release checks.
- Customer service: receive complaints and route them to the technical team. The accessibility statement must include a feedback channel.
Practical steps to make your website accessible this quarter
Now you understand the theory. But what do you do on Monday morning? Here is an order that works in companies of any size.
-
- Run a mixed initial audit (automated + manual) on a representative sample of your website. Document each finding with WCAG criterion, severity, and URL.
-
- Build a remediation plan prioritized by user impact and technical effort. Fix blocking Level A criteria first.
-
- Train your design and development teams in WCAG 2.2 AA. Without training, the same defects return at every release.
-
- Integrate automated accessibility tests into your CI/CD pipeline using axe-core, Pa11y CI, or similar. No PR should regress what was fixed.
-
- Publish an accessibility statement at a stable URL with conformance level, non-accessible content, and a feedback mechanism.
-
- Set up a re-audit calendar at least once a year and after every redesign or major change.
-
- Document an internal content policy: alt text, heading hierarchy, contrast, captions, plain language.
- Commission an external audit every two years. A fresh, certified perspective uncovers what your internal team can no longer see.
“Accessibility is not a feature, it is a fundamental right. When we treat a group of users as second-class citizens, we are saying something profound about what kind of internet we are building.”
– Leonie Watson, accessibility expert and W3C member
Frequently Asked Questions (FAQs)
It is the set of practices that allow anyone, regardless of ability, to use a website on equivalent terms. The W3C defines it as enabling people with disabilities to perceive, understand, navigate, and interact with the web.
WCAG 2.2 was released in October 2023. It adds nine new criteria focused on cognitive and motor accessibility (better focus visibility, consistent help, accessible authentication). WCAG 2.1 is still the version most laws cite, but if you want to stay current, target 2.2 AA.
Run a free automated tool such as WAVE (wave.webaim.org), Lighthouse (in Chrome DevTools), or axe DevTools. Then try navigating with the keyboard only: if you cannot reach a key button, you already have a 2.1.1 problem. For a real evaluation, you will need an expert audit.
Microenterprises (under 10 employees and turnover/balance below EUR 2 million) providing services are exempt from the EAA. Those manufacturing products are not. And every company, exempt or not, is subject to non-discrimination law that applies to digital services.
You must respond within the timeframes set by the national law and your accessibility statement. Failure to respond can trigger an enforcement procedure by the national supervisory body, with the corresponding sanctions.
It depends on the size and current state of the site. A professional initial audit for a mid-size website ranges from EUR 3,000 to EUR 8,000. Remediation can cost a few thousand to tens of thousands depending on findings. The good news: when accessibility is built into a new design, the extra cost is close to zero. Retrofitting is the expensive part.
Yes, significantly. Google rewards semantic HTML, well-structured headings, alt text, performance, and keyboard navigation (which ties into Core Web Vitals). An accessible website tends to rank better. It is not coincidence: Googlebot and a screen reader “read” the web in similar ways.
