Know exactly where your website fails accessibility law — and what to fix first.
Europlabs audits websites and mobile apps against the European Accessibility Act, WCAG 2.2 level AA and EN 301 549. You get a prioritised, developer-ready report in 10 working days — not a 200-page PDF nobody reads.
- Fixed price, quoted before we start
- Manual testing, not just automated scans
- 14-day refund policy
Illustrative example of the scoring layout used in our reports. Every finding is tied to a specific success criterion, a screenshot and a suggested code-level fix.
Since June 2025, accessibility is not optional in the EU
The European Accessibility Act (Directive 2019/882) applies to e-commerce, banking, transport, e-books and telecoms services sold to consumers in the EU. National enforcement bodies can require remediation, and non-compliant services can be ordered off the market.
Automated tools miss most of it
Scanners reliably detect roughly a third of WCAG failures. Keyboard traps, broken focus order, meaningless alt text and unusable custom components need a human tester — and those are the issues that actually block users.
Findings without priorities stall
A raw list of 400 violations gets filed and forgotten. We rank every issue by user impact, legal exposure and engineering effort, so your team knows which fifteen fixes clear most of the risk.
Statements have to be truthful
An accessibility statement that overstates conformance is its own compliance problem. We document what actually conforms, what does not, and the remediation timetable behind it.
Three ways we work with product teams
Accessibility audit
Full manual and automated review of your site or app against WCAG 2.2 AA, with screenshots, severity ratings and code-level remediation notes.
Audit details →EAA compliance programme
Scoping against Directive 2019/882 and EN 301 549, a documented conformance position, and the accessibility statement your legal team can stand behind.
Programme details →Cookie & consent review
Technical audit of your consent banner, tag firing order and cookie inventory against GDPR and the ePrivacy Directive.
Review details →Ten working days, four steps
-
Scope call — 45 minutes
We agree the page templates, user journeys and platforms in scope, then send a fixed-price quote. No work starts before you approve it in writing.
-
Testing — days 1 to 6
Automated scanning across every in-scope template, then manual testing with keyboard only, screen readers (NVDA, VoiceOver), 400% zoom and reduced motion.
-
Report — days 7 to 9
Every finding mapped to a WCAG 2.2 success criterion, with the failing element, a screenshot, user impact and a concrete suggested fix.
-
Walkthrough — day 10
A live session with your engineers to work through the priority list and answer implementation questions. Recording and issue export included.
Deliverables, in plain terms
Findings report
- Executive summary — conformance position in one page, for non-technical stakeholders.
- Issue register — each finding with WCAG reference, severity, affected templates and screenshots.
- Remediation plan — issues sequenced by impact against effort.
- Retest baseline — the exact steps we will re-run to verify your fixes.
Working artefacts
- Issue export — CSV or Jira-ready import so tickets exist the same day.
- Draft accessibility statement — structured to the EU model statement.
- Recorded walkthrough — yours to keep and share internally.
- Free clarification window — 30 days of follow-up questions by email.
Not sure what is in scope?
Send us the URL. We will tell you which templates matter, what a realistic scope looks like, and what it would cost — at no charge.