How do you recognise a truly accessible website?

How to check if a website is accessible

At first glance, it is almost impossible to judge a website’s accessibility. While visible elements like design or add-on features provide clues, they reveal very little about how usable a site actually is – for example, whennavigating via keyboard or screen reader.

In this article, you will learn: 

• Why digital accessibility often remains invisible

• Which criteria really matter – beyond widgets and aesthetics

• How to realistically assess your website’s accessibility status 

Why overlay tools alone cannot achieve digital accessibility

Many companies rely on so-called overlay tools – small add-on programmes that sit on top of a website and offer individual display or navigation options. This is often done under the assumption that it is a quick way toensure compliance. 

Such tools allow for features like text resizing, contrast adjustments, or text-to-speech functions. However, overlays usually only provide an additional "view" of the website and can even increase barriers for people using assistive technology like screen readers. They do not resolve the underlying issues – such as poor semantic structure, lack of keyboard navigation, or insufficient screen reader compatibility. 

A matter of perspective:

Assistive solutions like Eye-Able Assist can be a valuable first step. They provide users with immediate customisation options and improve accessibility in daily use – particularly where a comprehensive technical overhaul is still in progress.

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

Specialist associations and users alike agree: assistive software can cushion barriers, but it cannot eliminate them. Sustainable digital accessibility is only achieved when assistive tools like Eye-Able Assist are combined with technical measures, audits, and long-term monitoring. 

How to recognise genuine accessibility – visible and invisible 

Accessibility is rarely obvious at first glance. Many measures are implemented invisibly in the background and only become apparent through targeted testing or the use of assistive technology. Nevertheless, there are visible signs of advanced accessibility efforts.

Visible indicators 

• Accessibility widgets (e.g. buttons for adjusting the display): These signal the presence of tools but do not replace underlying accessibility.

• Accessibility statement: A legal requirement that summarises implemented measures and current limitations.

• Certificates and seals of approval: These show that a website has been tested against defined criteria – for example, through a structured manual assessment like the BIK BITV-test or the Eye-Able Seal. In these cases, the website is audited by certified accessibility experts and evaluated based on numerous test steps. It is important to remember: a seal of approval only reflects the status at the time of testing. 

An accessible website is recognised not by its design, but by its usability. 

Invisible indicators 

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

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

• Screen reader compatibility: Content is read out logically and meaningfully; the order of elements is correct, and all controls are labelled and accessible.

• Colour contrasts: Text and UI elements are designed with sufficient contrast to be legible for people with visual impairments.

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

The majority of accessibility processes remain invisible. While visible elements like widgets and statements indicate a commitment, they do not guarantee accessibility on their own.

Background processes: What makes a website genuinely accessible?

Legal and technical requirements  

With the implementation of the European Accessibility Act, many websites have been required to be accessible since June 2025. These legal requirements are based on the international WCAG guidelines (currently WCAG 2.1), which define minimum criteria for content to be perceivable, operable, understandable, and robust. The technical specifications of EN 301 549 serve as the definitive standard. 

Audits and testing: Manual is a must

Automated scans are an important first step. They detect many formal barriers, such as missing alt-text, insufficient colour contrast, or basic structural errors. However, they quickly reach their limits: complex content, logical workflows, or real-world usage scenarios – such as a checkout process – cannot be reliably evaluated by automation alone. 

This is precisely why manual testing is an essential component of WCAG compliance. Many success criteria can only be verified by human assessment. In manual audits, certified experts analyse elements such as thelogical reading order, keyboard and screen reader operability, and the actual user experience. Only this combination allows for a sound assessment of accessibility. 

Software-guided testing  

Software-guided testing helps to eliminate identified barriers step-by-step – even without prior experience or deep IT expertise. Users are guided through specific measures in an easy-to-understand way, knowing exactlywhat to do and why. This allows many barriers to be fixed immediately, while more complex adjustments are implemented in the code in parallel.

Practical tips: How businesses can tell the difference and take action

Self-tests for businesses

Many barriers can be uncovered with simple self-tests: 

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

• Colour contrast check: Use tools like the "WebAIM Contrast Checker", the "Colour Contrast Analyser", or the contrast checker in the Eye-Able dashboard to see if your contrasts are sufficient.

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

• Form logic: Check if all fields are clearly labelled, accessible via the Tab key, and arranged in a logical order. 

From self-testing to auditing 

• External audits: Have your website audited regularly by certified experts. They test according to current standards, evaluate real-world usage scenarios, and provide specific recommendations for long-term improvement. Eye-Able provides additional support here with manual accessibility audits that specifically highlight real user experiences.

• Certificates and audit reports: Publish seals of approval and audit reports to demonstrate transparency. The Eye-Able platform allows you to document results, keep them up to date, and present them in a clear, traceable way.

What’s next?

Anyone serious about accessibility needs more than just isolated measures or tools. The key is a clear, manageable path – from the initial overview to long-term improvement.

Accessibility with Eye-Able means: 

• Testing: Automated and manual tests make barriers visible – even those that remain hidden at first glance.

• Optimising: Identified barriers are clearly grouped and prioritised in the dashboard, showing their impact on your accessibility score. This makes it clear at a glance where action is most needed and which measures will have the greatest effect.

• Documenting: Accessibility measures are recorded transparently, for instance through an Accessibility Statement or a seal of approval. This makes it easy to track where you stand – and what has already been implemented.

• Monitoring: Continuous monitoring ensures that accessibility is maintained – even when updates are made or new content is added. 

In this way, accessibility becomes a continuous process rather than a one-off project.