Header and navigation
Dropdowns, mega menus and the mobile menu: can they be opened, used and closed with the keyboard, and is the state announced?
Applies to this website and is saved in your browser.
Good to know: this website is built to work well without these switches. They are personal preferences only: they do not change the code and do not replace accessibility, even though overlay widgets promise that. Why overlays do not help · Our accessibility statement
Tip: zoom (Ctrl/Cmd and +), contrast and read-aloud can also be set in your browser and operating system, then for every website.
Plain EnglishServices · Websites
Most barriers on a website come from a handful of templates and components: the header, the menu, the cards, the footer. We test one page per template, find what repeats, and show your developers exactly where to fix it.
A website with hundreds of pages is usually built from a small set of templates. If the main menu cannot be opened with the keyboard, it fails on every one of those pages. So we follow the W3C evaluation method WCAG-EM: home page, one page per template, contact, forms, legal pages and the journeys that matter to you.
Some barriers come from content, not code: an image without a useful alt text, a heading level skipped by an editor, a link that just says “more”. The report separates the two, so your developers and your editors each know what is theirs.
The CMS does not matter. We test the HTML your visitors receive, whether it comes from WordPress, TYPO3, a headless setup or hand-written code.
Dropdowns, mega menus and the mobile menu: can they be opened, used and closed with the keyboard, and is the state announced?
A logical outline and regions such as header, main and footer, so screen reader users can jump straight to what they need.
Alt texts that say what an image means in its context, and decorative images hidden from screen readers.
Text contrast, contrast of buttons and inputs, and a focus indicator that is clearly visible on every background.
200% zoom, reflow at 320 CSS pixels and wider text spacing, all with screenshots as evidence.
Cookie banners, maps, video players and chat widgets often bring their own barriers. We test them as part of your page.
Missing, meaningless or duplicated alt texts, especially on linked images and logos.
Focus styles removed in the stylesheet, leaving keyboard users without a cursor.
Layouts that force sideways scrolling at 320 CSS pixels, typically wide tables, fixed-width banners and carousels.
Text cut off or overlapping when line, word and letter spacing are increased, often in buttons with fixed heights.
“Read more” and “Click here” links that make no sense out of context.
Input borders and icon buttons with too little contrast against the background.
You send the URL; we propose the page sample and confirm it with you before we start.
axe-core, keyboard walk, zoom, reflow and text spacing on every page, with screenshots.
A person decides all 55 criteria and walks through your key journeys with a screen reader.
Findings grouped so that one fix in a template resolves them everywhere. Then re-test and certificate.
Rarely. Most findings sit in shared templates or components. Fix them once and every page using them improves. Content issues such as alt texts are listed per page.
The certificate covers the tested version on the test date. Monitoring scans regularly and after changes, and warns you when new content introduces a barrier. Our checklists help editors get it right from the start.
Yes. Start with the free home page check, then try the keyboard test and the contrast checker. They show you the most common problems in a few minutes.
See and practise focus
With the nearest passing shade
For design, code and content
All 55 criteria, openly described