Website accessibility in 2026: new rules, new deadlines

What is the European Accessibility Act

The European Accessibility Act (EAA), also known as Directive 2019/882, is a European Union law that requires digital products and services to be accessible to people with disabilities. EU member states have transposed it into their national legislation.

In simple terms: if you have a website through which you sell products or provide services to consumers in the EU, starting June 28, 2026, that website must be adapted for people with visual impairments, hearing loss, motor difficulties or cognitive limitations.

That means a blind person using a screen reader must be able to buy your product. Someone who can't use a mouse must be able to navigate with a keyboard. A person with low vision must be able to enlarge the text without the page "falling apart."

Who is required to comply

The EAA applies to a wide range of digital services. If your business involves any of the following, the law applies to you:

• Online stores - all e-commerce websites accessible to consumers in the EU
• E-banking and financial services - online banking, investment platforms
• Telecommunications services - operators, VoIP services, messaging platforms
• E-books and readers - digital publications and reading software
• Transportation services - online ticket purchasing, information systems
• E-service platforms - online ordering, reservation systems

What the WCAG 2.1 AA standard requires

WCAG (Web Content Accessibility Guidelines) is the international standard that defines how web content should be accessible. The EAA requires compliance with the AA level, which is a mid-level of strictness. The standard is based on four principles.

1. Perceivable

Content must be presented in a way that users can perceive it. This includes: text alternatives for images (alt text), captions for video content, sufficient color contrast between text and background (minimum 4.5:1 for normal text), the ability to enlarge text to 200% without losing functionality, and content that adapts to different devices.

2. Operable

Users must be able to operate the interface. All functions must be accessible via keyboard, with no traps that you can't escape using the Tab key. Users need enough time to read and interact with content. Animations must be pausable, and the page must not contain elements that flash more than three times per second.

3. Understandable

Text must be readable and predictable. The page must behave consistently, navigation must be logical, and forms must have clear labels and error messages. The page language must be declared in the HTML so that screen readers know which language to use when reading the content.

4. Robust

Content must be robust enough to be correctly interpreted by a variety of user technologies, including screen readers, magnifiers and other assistive tools. In practice, this means: valid HTML, proper use of ARIA attributes and semantic elements.

Practical steps toward compliance

The law might sound abstract, but in practice it comes down to specific technical requirements that you can check and fix. Here's what you need to do.

Semantic HTML

Use the correct HTML elements for their intended purpose. Headings go in <h1> through <h6> in order, without skipping levels. Navigation goes in <nav>, main content in <main>, footer in <footer>. Screen readers use this structure for navigation, just as you use the visual layout of a page.

Alt text for images

Every image that conveys information must have a meaningful description in its alt attribute. Not "IMG_4523.jpg," but "The WebDesignbyTomi team in the office" or "Graph showing a 40% traffic increase after the redesign." Decorative images that carry no information should have an empty alt (alt="") so screen readers skip them.

Keyboard navigation

Every interactive element (link, button, form) must be reachable using the Tab key. Focus must be visible, typically as an outline around the active element. A user should never get stuck in a "trap" they can't escape with the keyboard. Testing is simple: try using your website without a mouse.

Color contrast

Text must have sufficient contrast against its background. WCAG 2.1 AA requires a ratio of at least 4.5:1 for normal text and 3:1 for large text (18px bold or 24px regular). Light gray text on a white background doesn't pass. Use tools like the WebAIM Contrast Checker to verify.

ARIA labels

Accessible Rich Internet Applications (ARIA) attributes help screen readers understand interactive elements that standard HTML can't adequately describe. For example, aria-label provides a description for an icon-only button, and aria-expanded indicates whether a menu is open or closed. Use them only when standard semantic HTML elements aren't sufficient.

Screen reader compatibility

Test your website with at least one screen reader. NVDA is free for Windows, and VoiceOver is built into macOS and iOS. This is the most important test because it reveals problems that automated tools can't detect, such as a confusing reading order or unclear form labels.

Accessible vs inaccessible website - comparison

Here are the concrete differences between a website that meets WCAG 2.1 AA and one that doesn't. These are the elements that regulators check.

How to check your website

You don't have to guess whether your website is accessible. There are free tools that can show you specific problems right away.

• WAVE (wave.webaim.org) - visually highlights issues on the page, great for a quick check
• axe DevTools - a Chrome extension that automatically detects WCAG errors
• Google Lighthouse - built into Chrome DevTools, has an accessibility section with scoring
• WebAIM Contrast Checker - for verifying color contrast

However, automated tools catch only about 30-40% of problems. For a more thorough check, test manually: disable your mouse and navigate with the keyboard, zoom text to 200%, turn on a screen reader and try to complete key tasks on the page.

How much does adaptation cost

The cost depends on whether you're building a new website or adapting an existing one.

• New website - accessibility should be built in from the start at no additional cost. If someone charges you for "accessibility" as an add-on, that's a red flag.
• Existing website with minor issues - €200-500 for adding alt text, improving contrast and semantic structure
• Website with serious shortcomings - €500-1,500 for a complete overhaul, including navigation and form refactoring

Compare that with a potential fine of €25,000 and the potential lost customers who simply can't use your website. Proactive investment always pays off.

How we build accessible websites

At WebDesignbyTomi, accessibility isn't an add-on option or a premium package. It's a standard built into every website from the first line of code.

• Semantic HTML from the start - every page uses the correct elements for each purpose, from headings to navigation
• Skip-to-content link - allows screen reader users to bypass navigation and go directly to content
• Visible focus - every interactive element has a clearly marked focus state for keyboard navigation
• Color contrast tested - all color combinations pass the WCAG 2.1 AA contrast check
• ARIA attributes - buttons, navigation and interactive elements have appropriate labels for screen readers
• Responsive design - text can be enlarged to 200% without losing functionality, on any device
• Tested with NVDA - every page is tested with a screen reader before delivery

Why accessibility is good for business

Beyond avoiding fines, an accessible website delivers tangible business benefits that are rarely discussed.

• Larger audience - you open the door for 15-20% of the population who otherwise can't use your website
• Better SEO - many accessibility practices (alt text, semantic structure, clean HTML) are also SEO best practices. Google rewards them.
• Better user experience for everyone - older users, people with temporary limitations (broken arm, tired eyes), users on slow networks
• Positive brand image - you show that you care about all users, not just those without any difficulties
• Legal protection - you reduce the risk of lawsuits and regulatory fines that can be many times more expensive than prevention

Accessibility isn't a cost - it's an investment. And with the legal deadline of June 28, 2026, the time to act is now. Don't wait for regulators to tell you what should have been done. Check out our packages or contact us for a free accessibility review of your current website.

If you're curious about what else can go wrong with a website, also check out our article on WordPress vs custom-coded websites.