DEV Community

RegBase
RegBase

Posted on

The European Accessibility Act Is a Working Problem: Fix Scope First, Then Audit, Then Statement, Then Tracker

Since 28 June 2025, the European Accessibility Act (EAA, Directive (EU) 2019/882) applies through national transpositions. If your team sells covered products or services into the EU, the practical requirement is not "be accessible" as a vibe. It is: be able to show what you did.

That reframing matters. The Act is not a quiz you pass once; it is a working problem with an evidence trail. Here is how to run it in the right order — and what breaks when you run it in the wrong one.

1. Your concrete problem, before any work starts

Three questions decide everything downstream:

Does the Act cover your offer at all? The Directive defines what is in scope in its Article 2 covered lists — products on one side, services on the other. Your offer either lands on those lists or it does not. You need a written answer per offer, not a feeling.

In which member states? The Act reaches you through national transpositions. Each EU country transposes the Directive into its own national law, and the national transposition in each country governs. "We're compliant with the EU" is not an answer; "here is our position under the transposition in country X" is.

What evidence do you keep? You have to be able to show what you did. That means scope decisions, audit findings, statements published, and fixes shipped all need to leave a trail. If your process produces no artifacts, you have nothing to show.

2. The order of work

The sequence below is deliberate. Each step consumes the output of the previous one.

Step 1: Fix scope first

Check your offer against the Article 2 covered lists. Two scope facts to get exactly right:

  • If you are a microenterprise providing services, you are exempt under Article 4(5).
  • If you deal with covered products, microenterprise status does not exempt you.

Note the asymmetry. The microenterprise exemption exists for services, not for products. Teams get this wrong in both directions: some exempt themselves when they should not, others do the full work when they are exempt. Fix scope in writing, per offer, before anything else.

Step 2: Run a compliance checklist

Once scope is fixed, turn the applicable requirements into a checklist you can work through offer by offer. A checklist is how a directive becomes tickets. It also doubles as evidence: a completed checklist with dates is a record of what you checked.

Step 3: Do a WCAG 2.2 self-audit

For the digital parts of your offer, audit against WCAG 2.2 yourself. A self-audit is not a certification; it is a structured pass over your actual product with findings recorded. What matters is that the findings exist on paper, with enough detail that someone else can reproduce them.

Step 4: Publish an accessibility statement

The statement describes the accessibility state of your offer — and it should be written from your audit results, not from optimism. An accurate statement that says "here is what works, here is what does not yet" is stronger and safer than a confident claim nobody can back up.

Step 5: Run a remediation tracker

Every audit finding becomes an entry in a tracker with an owner and a date. A finding without an owner is a wish. The tracker is what turns "we know about this" into "this is owned, dated, and moving" — and it is the document that shows the sequence: found, assigned, fixed, verified.

3. What goes wrong when the order is reversed

Auditing before scope is fixed. If you start with the audit, you audit blind. You may spend effort on parts of the offer that are not covered at all, or skip parts that are. Worse, the microenterprise rule lives at the scope step: if you never fix scope, you never check whether Article 4(5) exempts you — so your entire downstream effort may be aimed at an offer that was out of scope, or aimed at nothing while an in-scope product ships unaudited.

Publishing a statement with no audit behind it. A statement is a claim about your product's state. Published without an audit, it is a claim with nothing behind it. If anyone — a customer, a market-surveillance authority — looks at the statement and asks "what is this based on?", the honest answer has to exist. An unsupported statement is not a shortcut; it is the first artifact that gets examined.

4. The worked example

The sequence above is worked through concretely in the EAA Core Pack, $99, one zip, seven files: an applicability checker, a scope guide, a compliance checklist, accessibility statement templates, a WCAG 2.2 self-audit worksheet, and a remediation tracker that turns findings into owned, dated fixes.

https://lexusdev.gumroad.com/l/voodxa

The pack is general guidance, not legal advice. The national transposition in each EU country governs, and market-surveillance authorities make the final call. Verify against the current harmonised standard, EN 301 549, before relying on anything here.

Top comments (0)