Written by Carolin Kaulfersch on January 28, 2026

How do you recognise a truly accessible website?

Accessibility is much like an iceberg: what is visible at first glance is only a small fraction. A modern look or a widget says little about whether a website is WCAG-compliant. Learn which technical criteria are crucial – and why true accessibility starts deep below the surface.

Key points at a glance

  • You recognise accessibility by usability, not by design.

  • Widgets and overlays alone do not make a website accessible.

  • What counts are invisible factors such as structure, keyboard operation and screen reader compatibility.

  • Automated tests are not enough – manual testing is essential.

  • WCAG 2.2 is becoming the new benchmark.

How to recognise a truly accessible website

At first glance, accessibility is hard to judge. Visible elements such as design or additional features give some indication, but say little about how well a website can actually be used – for example with a keyboard or screen reader.

In this article, you will learn:

  • why accessibility on websites often remains invisible

  • which criteria really count – beyond widgets and appearance

  • how to realistically assess the accessibility status of your website

Why overlay tools alone do not create accessibility

Many organisations rely on so-called overlay tools – small add-on programs that sit on top of a website and offer individual display or operating options. This is often done on the assumption that it is a quick way to be on the safe side.

Such tools allow users to enlarge text, switch contrast or have content read aloud, for example. However, overlays usually only provide an additional view of the website and can even increase barriers for people who use assistive technologies such as screen readers. The actual problems – such as a faulty semantic structure, missing keyboard operation or poor screen reader compatibility – remain unsolved.

That is why it is important to put them into context: assistive solutions such as Eye-Able Assist can be a useful first step. They give users immediate options to adjust the website to their needs and improve accessibility in everyday use – especially where a comprehensive technical overhaul has not yet been completed.

What they cannot and should not do, however, is make the underlying website accessible. That requires structural changes to the code, manual testing and continuous optimisation.

Disability organisations and users therefore agree: assistive software can cushion barriers, but not remove them. Lasting digital accessibility is only achieved when supporting tools such as Eye-Able Assist are combined with technical measures, audits and long-term monitoring.

Redirection to the Eye-Able free website testHow to recognise genuine accessibility – visible and invisible

Accessibility is rarely obvious at first glance. Many measures are implemented in the background and only become visible through targeted testing or the use of assistive technologies. Nevertheless, there are visible signs that an organisation is taking accessibility seriously.

Visible indicators

  • Accessibility widgets (e.g. buttons for adjusting the display): They show that assistive features are available, but do not replace underlying accessibility.

  • Accessibility statement or accessibility information: Public sector bodies in the EU and the UK must publish an accessibility statement. Companies covered by the European Accessibility Act must provide information on the accessibility of their services. Both summarise the measures implemented and any remaining limitations. The accessibility statement generator helps you create such a statement.

  • Certificates and seals: They show that a website has been tested against defined criteria – for example through a structured manual assessment such as the BIK BITV/WCAG test in Germany or the Eye-Able Seal. Accessibility experts test the website and assess it against numerous test steps, depending on the scope. It is important to remember that a seal only ever reflects the status at the time of testing.

You recognise an accessible website not by its design, but by its usability.

Invisible indicators

  • Semantic structure: Correct HTML markup (heading hierarchy, lists, tables, etc.) so that screen readers can understand and navigate content.

  • Keyboard navigation: All functions and content can be reached using the keyboard alone, without "keyboard traps" or hidden elements.

  • Screen reader compatibility: Screen readers can read content aloud in a meaningful and logical order, and all controls are labelled and reachable.

  • Colour contrast: Text and interface elements have sufficient contrast to be recognisable for people with visual impairments.

  • Form logic: Forms are clearly structured, all fields are correctly labelled and fully operable.

Most accessibility work remains invisible. Visible elements such as widgets and statements show commitment, but do not guarantee accessibility.

Behind the scenes: what really makes a website accessible?

Legal and technical requirements

Since June 2025, the European Accessibility Act (EAA) has required many websites and online shops in the EU to be accessible. Each member state has transposed it into national law, for example Germany through the BFSG. National authorities are now actively checking compliance. For public sector bodies, the Web Accessibility Directive continues to apply. In the UK, the Equality Act 2010 and the Public Sector Bodies Accessibility Regulations 2018 apply – and UK companies selling to consumers in the EU must also meet the requirements of the EAA.

Technically, the legal requirements are based on the European standard EN 301 549 and therefore on the international WCAG guidelines. These define criteria for perceivable, operable, understandable and robust content. WCAG 2.1 Level AA is currently still the relevant benchmark. In September 2026, EN 301 549 V4.1.1 was published, aligning the standard with WCAG 2.2. Once it is cited in the Official Journal of the EU, WCAG 2.2 will become the new benchmark – so it is worth working towards it now.

Audits and tests: manual testing is essential

Automated testing is an important first step. It detects many formal barriers such as missing alternative text, insufficient colour contrast or simple structural errors. But it quickly reaches its limits: complex content, logical sequences or real-life user journeys – such as a checkout process – cannot be reliably assessed automatically.

That is exactly why manual accessibility testing is part of a sound WCAG assessment. Many success criteria can only be checked by people. In manual audits, accessibility experts analyse, among other things, the logical order of content, operability with keyboard and screen reader, and the actual user experience. Only the combination of automated and manual testing allows a well-founded assessment.

Software-guided tests

Software-guided tests help you remove identified barriers step by step – even without prior experience or in-depth IT knowledge. You are guided clearly through concrete measures and know immediately what to do and why. This means many barriers can be fixed right away, while more complex changes are implemented in the code in parallel.

Practical tips: how to spot the difference and take action

Self-tests

Many barriers can be uncovered with simple self-tests:

  • Tab test: Can you navigate through all menus and forms using the Tab key (without a mouse)? Is the focus always visible?

  • Colour contrast check: Use tools such as the "WebAIM Contrast Checker", the "Colour Contrast Analyser" or the contrast checker in the Eye-Able dashboard to check whether contrast is sufficient.

  • Screen reader check: Use free screen readers such as NVDA (Windows) or VoiceOver (Mac) to check the flow and clarity of your website.

  • Form logic: Check whether all fields are clearly labelled, reachable with the Tab key and logically arranged.

From self-test to audit

  • External audits: Have your website tested regularly by accessibility experts. They test against current standards, assess real-life user journeys and give concrete recommendations for improvement. Eye-Able supports you with manual accessibility testing that makes real usage scenarios visible.

  • Certificates and test reports: Publish seals such as the Eye-Able Seal and test reports as a sign of transparency. With the Eye-Able platform, results can be documented, kept up to date and presented clearly.

What next?

If you are serious about accessibility, you need more than individual measures or tools. What matters is a clear, traceable path – from the first overview to long-term improvement.

Accessibility with Eye-Able means:

  • Testing: Automated and manual testing against WCAG 2.1 and WCAG 2.2 reveals barriers – even where they are hidden at first glance.

  • Optimising: The dashboard groups and prioritises identified barriers clearly and shows their impact on the accessibility score. This lets you see at a glance where action is most needed and which measures have the greatest effect.

  • Documenting: Measures are recorded transparently, for example in an accessibility statement or through a seal. This makes it clear where you stand and what has already been implemented.

  • Monitoring: Continuous monitoring helps to detect new barriers early – even after updates or when new content is added.

This turns accessibility from a one-off project into a continuous process.

Get an initial overview of your website's accessibility status – free of charge and without any prior knowledge.

Get an initial overview of your website’s accessibility status – with no obligation and no prior expertise required.

Filter

Filter by category

Confirm your selection with the button at the end of the list after choosing the categories.

Reset filters

How to make your online shop accessible: requirements, advantages, and implementation tips

Read story

Checklist: Accessible web design for your website

Read story
Laptop displaying an online shop for headphones with a warning sign. Text: "Avoid BFSG warnings: Make your online shop accessible now."

BFSG warnings: What you need to consider now regarding accessibility

Read story

Accessibility statement explained in simple terms: content, obligations, examples

Read story

Eye-Able Audit Update 3.7 – Easier management and hiding of errors

Read story
A red and green graph pointing down is depicted.

A Missed EAA Deadline, a Costly Lesson: The Real Risks of Ignoring the European Accessibility Act in the Netherlands

Read story
A smiling man with a laptop with graphs and statistics on the right side.

Accessibility as Business-Booster

Read story
A young man with two prosthetic legs is skateboarding in a halfpipe. He wears a helmet and knee pads. The setting feels athletic and empowering.

Halfpipe instead of hurdles - Sit’n’Skate

Read story

Let's clarify: The AGID Guidelines of May 15, 2025

Read story
A black dachshund wearing sunglasses is holding a smartphone and looking at it. The background is light with a yellow semicircle behind the dog.

The superpower of diversity: What animals reveal about barriers

Read story
Colorful puzzle pieces with various patterns in the background.

Making the Difference - Inclusion vs Integration

Read story

You need more information?

Contact us and we will be happy to help you.

a man with down syndrome shows a woman something on the computer. they both laugh