Quick accessibility check
A quick test for the most common barriers that can be found automatically: missing alt texts, unlabelled form fields, blocked zoom and more. For the European Accessibility Act it gives you a useful first picture, but it’s not a full audit.
What gets checked
- Page language and page title
- Heading structure
- Alt texts for images
- Labels for form fields, links and buttons
- Whether zooming is allowed on mobile
- Skip link and accessibility statement
Limits of this check
- Automated tests find roughly a third of all barriers. Contrast, keyboard use and screen reader behaviour need manual testing.
- Only the HTML of the entered page is checked, without JavaScript.
Every check explained
What each point in the report means, why it matters and how to fix it.
- Page language
The page language is not specified. Screen readers may read the text with the wrong pronunciation.
How to fix it: Add the lang attribute to the html tag, for example lang="en".
- Page title
The page has no title.
How to fix it: Add a meaningful title tag.
- Main heading
There is no main heading (h1).
How to fix it: One h1 per page that says what the page is about.
- Heading structure
The structure skips levels. Screen reader users navigate by headings, so gaps make them lose track.
How to fix it: Don’t skip levels, so an h2 is followed by an h3 rather than an h4. If you want a different look, change it with CSS instead of picking another level.
- Alt texts
Several images have no alt attribute. Screen readers then read the file name or skip them without notice.
How to fix it: Give every image an alt attribute. Describe meaningful images, mark purely decorative ones with alt="".
- Form fields
Several form fields have no label that screen readers can announce.
How to fix it: Connect each field to a label element. Placeholder text alone is not enough.
- Links without text
Several links have no readable name, often icon links to social media.
How to fix it: Give icon links an aria-label, for example aria-label="Instagram".
- Buttons without text
Several buttons have no readable name, such as menu or close icons.
How to fix it: Give icon buttons an aria-label, for example aria-label="Open menu".
- Meaningful link texts
Several links just say “here”, “more” or similar. Out of context they say nothing.
How to fix it: Write link texts that make sense on their own, such as “Prices for roof repairs”.
- Zoom allowed
Zooming on mobile is blocked. People with low vision cannot enlarge text.
How to fix it: Remove user-scalable=no and maximum-scale from the viewport meta tag.
- Embedded content
Several embedded elements such as maps or videos have no title.
How to fix it: Give each iframe a title attribute, for example title="Directions on Google Maps".
- Duplicate IDs
Several IDs appear more than once. This can mix up labels and skip links.
How to fix it: Use each ID only once per page.
- Skip link
No skip link to the main content found. Keyboard users have to tab through the whole menu on every page.
How to fix it: Add “Skip to content” as the first link on the page, pointing to the main area.
- Accessibility statement
No link to an accessibility statement found. Businesses covered by the accessibility law must provide one.
How to fix it: Create an accessibility statement and link it in the footer.
- Autoplay
Several media elements play automatically. That interferes with screen readers and is distracting.
How to fix it: Remove autoplay or at least start muted and provide a pause button.
- Tab order
Several elements force their own order with tabindex, which confuses keyboard users.
How to fix it: Remove tabindex values above 0 and control the order through the HTML structure.
- Needs manual testing
Contrast, keyboard use, focus visibility and screen reader behaviour can’t be tested automatically. That’s what a full audit is for.
Matching package
from€490
Accessibility audit against WCAG 2.1 AA with an action plan for the EAA.
Questions
If everything is green here, am I compliant?
No. The test only finds what can be detected automatically. For a reliable answer you need manual testing against WCAG 2.1 AA, as in the wwwery open package.
More checks
Does AI mention your business?
We ask ChatGPT, Perplexity and Google’s AI Overview the questions your customers would ask and see whether you come up in the answers.
Create an llms.txt for your website
An llms.txt is a file in the root of your website that tells AI systems, in a simple format, which pages matter and what each one covers.
How fast does your website load?
The measurement runs on Google Lighthouse.
What does your website load before consent?
We open your page the way a new visitor would, before clicking anything, and list every external service and cookie that loads.
How well is your website secured?
The test takes a quick look at your website from the outside and checks HTTPS, the certificate, security headers, cookie settings and how up to date the detectable software is: WordPress with plugins, Next.js (for example on Vercel), Astro, jQuery, Bootstrap and Drupal.
Email check: Does your email arrive, and is your domain safe?
The check reads your domain’s DNS records and shows whether your email can be recognised as genuine or ends up in spam, whether someone can forge email in your name and whether similarly spelled domains are registered.
Spam check: Is this email genuine or a scam?
Paste a suspicious email into the box, in any language.