What Accessibility Overlay Widgets Mean for EAA Compliance

What are the accessibility overlay widgets?

Accessibility overlay widgets are third-party tools that are added to a website, usually through a piece of JavaScript.

These tools typically appear as a button or icon on the page and, when selected, the widget can offer a range of settings intended to make the website easier to use.

Depending on the tool, these features can include:

• Text size adjustments

• Contrast or colour changes

• Text-to-speech functionality

• Keyboard navigation options

• Focus indicators

• Animation controls

• Reading aids

• Different display modes

• Other user preference settings

Although these features can be helpful and improve the user experience, they don’t automatically make a website accessible, especially in relation to EAA requirements.

An overlay generally works as an additional layer on top of an existing website. It does not change the underlying HTML, content, components or functionality that may be creating an accessibility barrier in the first place.

For example, if a website has an image without an appropriate text alternative, adding a widget does not automatically give that image the correct alternative text.

If a form field does not have a properly associated label, the widget does not fix the underlying form structure.

With that, we have a very clear answer. An overlay widget is a valuable accessibility feature to improve the experience of people with disabilities on a website. But it can only remove some accessibility barriers.

This means that some types of disabilities might be covered, but not others.

Do accessibility overlay widgets make a website EAA compliant?

As we mentioned before, accessibility overlay widgets aren’t comprehensive and cannot resolve all accessibility barriers. On their own, they don’t make a website EAA compliant.

The European Commission specifically states that “overlays which do not ensure that the website itself meets the detailed criteria of the standard are not an appropriate solution.”

The standard it refers to is EN 301 549. For digital products and services marketed within the European Union, this standard at version v3.2.1 provides the relevant European accessibility requirements.

In effect since June 2025, under the EN 301 549 requirements, the EAA points to WCAG (Web Content Accessibility Guidelines), level 2.1 AA, as the relevant framework to achieve compliance.

It provides a set of success criteria based on four essential principles, known as POUR: perceivable, operable, understandable, and robust.

Perceivable

Information needs to be available in ways users can perceive.

Common examples of barriers for people with disabilities include missing image alt text, poor colour contrast, inaccessible video or audio, and unclear page or content structure.

To make content perceivable, the website should provide more than one way to access it. For a video to be understood by a user with hearing disabilities, for example, it needs to have appropriate subtitles and caption. This way they can comprehend that exact situation, with the complete context and scenario.

Operable

Users need to be able to navigate and interact with a website independently. Issues with this principle normally include problems with keyboard navigation, poor focus management, inaccessible links and buttons, dynamic content, and navigation menus that are overly complicated.

Here, the key is simplicity. A website that is simple and clear to navigate can offer a smoother user experience, giving them autonomy, especially to users with motor and cognitive disabilities.

Understandable

Content and interactions should be clear and predictable. Things like unclear forms, confusing error messages, inconsistent navigation and poorly structured content can make websites hard to understand.

For example, a person with dyslexia may find it harder to process information when a webpage contains long blocks of text, unclear headings, complicated language or instructions that are difficult to follow.

Robust

Websites should work well with different browsers, devices and assistive technologies. Issues can happen when website features are not built correctly or when content does not work properly with tools such as screen readers.

These problems are part of the website itself. An accessibility overlay can offer additional features, but in cases like these, it cannot fix the website's code, content or functionality.

To have a comprehensive understanding of WCAG Principles, we recommend the read of our article: What is POUR and Why is it Critical to WCAG Standards?

Why accessibility overlays are not a replacement for accessibility testing

Although accessibility overlays are great features, they’re not enough to resolve accessibility barriers.

For example, consider a website with a product search form.

The colours may have sufficient contrast. The text may be large enough to read. An overlay may allow users to increase the font size.

These are important for making content accessible. But if the search field has no accessible label, a screen reader user may still struggle to understand what the field is for.

The same principle applies to navigation.

A website might offer a widget with a keyboard navigation feature, but if the website's own navigation has focus problems or controls that are difficult to use, it can still create barriers for keyboard users.

These are just some examples of why overlays are not a replacement for accessibility testing. Just a full website accessibility audit, along with continuous monitoring, can uncover accessibility issues and highlight areas that need improvement.

Accessibility testing can be performed in two main ways: using automated tools or through manual audits.

Automated tools are very helpful to detect accessibility issues quickly and consistently. It’s a way to understand how accessible a website is and start resolving the barriers that affect users most.

The Nexus Inclusion website scanner tool can do a comprehensive analysis of the entire website in a few minutes and present issues by severity, so teams know where to start, understand how they affect users with disabilities, and see which WCAG criteria they fail.

The tool analyses each issue against WCAG success criteria, helping you understand the reason behind the error and how to avoid repeating it on your website. It also provides detailed guidance to how each issue can be fixed effectively.

Manual audits are also an option. While they provide a comprehensive analysis performed by accessibility experts, they can also be time-consuming and expensive.

What should organisations do to achieve EAA compliance?

Rather than relying solely on accessibility overlay widgets, to achieve EAA compliance, organisations need to adopt an ongoing accessibility strategy.

They should involve teams to integrate website accessibility into every process and start a practical accessibility programme that should be built around four key stages.

1. Find accessibility issues

The first step is understanding what is happening across your website.

Start with automated accessibility scanning and detect potential issues across pages, without having to manually inspect every page individually.

It’s common to find that errors happen repeatedly across different pages. So, fixing one issue can quickly resolve barriers across multiple pages at once.

Some of the most common errors are include missing alternative text, colour contrast failures, form-related issues, and improper labelling.

2. Analyse issues against accessibility requirements

Once issues have been identified, teams need to understand what they mean in relation to EAA compliance.

Receiving a list of accessibility errors is not enough. The development and content teams need to know what to do next.

When the issues are connected to the relevant accessibility requirements and prioritised based on how they impact users, the fixing process becomes easier and more effective.

This is especially important so teams can know where an accessibility widget overlay is or not enough.

3. Fix the source of the problem

The next step is remediation.

While an accessibility overlay is a tool to work around an inaccessible component, organisations should resolve the component issue itself.

For example, instead of relying on a widget to change contrast, make sure the website's text, controls and components meet the contrast requirements.

When issues are fixed at the source, they can be resolved across the website. It also helps teams understand where the problem came from and avoid it happening again.

All of these have strong impact on the user experience.

4. Monitor accessibility over time

Because websites change constantly, continuous monitoring is essential to maintain EAA compliance over time.

When new pages are published, components are updated, or new functionalities are added, there’s a chance that new accessibility issues are also introduced.

Ongoing monitoring can help organisations detect these issues early, before they impact users with disabilities, while also helping to reduce potential legal risks.

Another way to support accessibility over time is investing in accessibility training.

When development, design and content teams understand what causes digital accessibility issues on a website, it’s easier to avoid introducing them.

Find accessibility issues before they become a bigger problem

Nexus Inclusion helps organisations identify, understand, monitor and fix accessibility issues across their websites, so teams can move from detection to remediation efficiently.

By understanding the accessibility regulations that apply to your business, adopting recognised accessibility standards, testing your digital products, and training your teams, you can build a strong foundation for long-term accessibility.

The first step is discovering where your website stands now, and you can do that using our Free EAA Compliance Checker. Try it now!