Accessibility · the European Accessibility Act

What an automatic check can see, and what it cannot.

Paste your address and we run an automatic accessibility pass over the page — contrast, text alternatives, structure, labels, focus order — and tell you what it found, in words you can hand to whoever maintains the site. Then we tell you the part most tools leave out: how much of the standard that pass actually covers.

This check is protected by reCAPTCHA; Google’s privacy policy and terms of service apply. It runs when you press the button, and on no other page of this site.

The law, in four sentences

The European Accessibility Act has applied since 28 June 2025.

Directive (EU) 2019/882 sets accessibility requirements for a list of products and services sold in the European Union — among them e-commerce, banking, transport and e-books. Each member state wrote it into its own law, and the technical reference those laws point at is the European standard EN 301 549, which in turn points at the Web Content Accessibility Guidelines at level AA.

Whether it reaches your business depends on what you sell, how large you are and which countries you sell into; micro-enterprises are treated differently for services, and the detail differs per member state. That is a question for a lawyer who knows your situation, and this page is not going to pretend otherwise. What it can do is show you what is measurably wrong with your page today.

  • Directive (EU) 2019/882, applying since 28 June 2025
  • EN 301 549 is the technical standard the laws point at
  • WCAG 2.2 level AA is the reference for web content
  • Whether it applies to you is a legal question, not a technical one

The honest part

No automatic tool can tell you that a page is accessible.

An automatic pass is very good at a particular kind of question: is there a text alternative, is this contrast ratio high enough, does this control have a name, is the heading order broken. Those are the ones a machine can answer, and where it says something is wrong it is usually right.

It cannot answer the rest. Whether the description of a photograph is the right description. Whether a page still makes sense read aloud from top to bottom. Whether somebody using only a keyboard can finish what they came to do. Whether an error message explains what went wrong. Those need a person, and on many pages they are where the real problems live.

So this check gives you a score, the things it found, and a plain sentence about its own limits beside every result. Anyone offering to make your site accessible with a script you paste into it is selling you something else.

  • What a machine can check, checked properly
  • What a machine cannot check, named rather than glossed over
  • No certificate, no badge, no claim about whether you meet a law

What we will and will not say about your site

After the check

Every page ReWynder builds has to pass before you see it.

When ReWynder rebuilds a site, accessibility is not a pass at the end — it is a gate in the middle. Each page is rendered and put through the same automatic checks, plus a performance and SEO budget, and a page that falls below the accessibility bar does not reach you as something to approve: it goes back to be fixed, or it is flagged for a person.

That is the bar, not a promise about a score. The same limits apply to us: an automatic pass covers part of the standard for our pages exactly as it does for yours, and the part that needs a person still needs a person.

  • Rendered, then checked — every page, before it is shown to you
  • A page under the bar is fixed or flagged, never quietly approved
  • The same caveat applies to our own pages

How the build gate works

Where this comes from

The documents behind the paragraphs above, so you can read them yourself rather than take our word for any of it.

Questions about accessibility

Does a clean result mean my site meets the standard?

No, and we will not say it does. An automatic pass covers part of WCAG 2.2 AA. A page can come back with nothing found and still be unusable with a screen reader or a keyboard, because the questions that would catch that are not ones a machine can ask. A clean result means the machine-checkable part looks right, which is a good place to start and not a conclusion.

Can you certify my site?

No. Nobody can certify a website with an automated tool, and we do not issue badges. What we can give you is a measurement you can act on, a list of what was found, and a clear statement of what the measurement does not cover.

Is an accessibility overlay a solution?

We do not offer one and we would not recommend one. An overlay is a script that changes a page in the visitor’s browser; it cannot fix markup that carries the wrong meaning, and people who rely on assistive technology have been vocal about the results. Fixing the page is the thing that works.

Does this check the whole site?

One page — the one at the address you gave. Accessibility problems usually come from a template rather than from a page, so one page tells you a lot; it does not tell you everything. A full pass over every page happens during a rebuild.

What does ReWynder do about the part a machine cannot check?

We build to the standard by construction — real headings, real labels, focus order, contrast from the design tokens up — and we check every page automatically before you see it. Where a human judgement is needed we say that it is needed rather than reporting it as passed.

My site is not in the European Union. Is this still useful?

Yes. The findings are about the page, not about a jurisdiction: a picture with no description is a picture with no description anywhere. Several countries outside the EU point at the same WCAG levels in their own rules.

Fix the page, not the symptom.

ReWynder rebuilds the site to the standard instead of patching it in the browser — and every page goes through the same checks before you are asked to approve it.

ReWynder is not open to customers yet — both buttons lead to the waiting list today, and we write the moment you can start.