Existing website
Receive a prioritised register of barriers, recommended fixes and evidence from an agreed test sample.
Public-sector websites covered by the EU Web Accessibility Directive must meet accessibility requirements, publish and maintain an accessibility statement, provide a way to report accessibility barriers and explain how to use the relevant enforcement procedure. For most websites, conformity is assessed against the applicable requirements in EN 301 549 v3.2.1. This includes WCAG 2.1 Level AA and additional requirements. Coverage, exemptions and enforcement depend on the law implementing the Directive in your country, which we confirm before proposing the work.
Receive a prioritised register of barriers, recommended fixes and evidence from an agreed test sample.
Set measurable accessibility requirements, check progress during delivery and test them before supplier acceptance.
Replacing or substantially redesigning an existing site? We can combine a baseline audit with procurement requirements and staged acceptance checks.
Help me choose a scopeA WCAG 2.1 AA review alone is not a complete EN 301 549 assessment. We test the applicable web requirements in the harmonised standard and record the exact scope used. We provide technical accessibility advice, not legal advice.
You work with one lead reviewer from scoping through handover. Before work starts, the proposal fixes the sample, method, deliverables, exclusions, timetable and price. Reports and meetings are available in Dutch or English. The same reviewer scopes the work, tests the site and explains the findings to your team or supplier, so decisions do not pass through an account-management layer.
We select the journeys, pages and shared components that matter most, together with the browser and assistive-technology combinations. Documents, authenticated areas and third-party tools are included only when named in the proposal.
We manually test the selected journeys and shared components with keyboard navigation, zoom and reflow, screen readers and code inspection. Automated checks support the review but do not replace manual testing. The proposal names the browser and assistive-technology combinations.
You receive an issue register, a concise assessment report and a findings meeting with the lead reviewer. Each issue includes reproduction steps, evidence, user impact, affected pages or components, the relevant standard reference, priority and a recommended fix. The report records the test date, sample, method and results. It can inform the accessibility statement, but the reported results apply only to the agreed sample and do not certify the entire service.
If requested, we support your team or supplier while they fix the issues, then retest selected items and record whether they have been resolved.
We review an existing specification or turn EN 301 549 into tender language, required supplier evidence and testable acceptance criteria. For example: which journeys must pass keyboard and screen-reader testing, which document types are included and what must be resolved before acceptance.
We track findings and supplier responses at agreed design and development stages. Suppliers can discuss findings directly with the reviewer.
We independently test the agreed journeys and criteria. The report distinguishes passed requirements, unresolved failures and verified fixes, giving your organisation evidence for its acceptance decision.
A user must be able to complete the permit application using keyboard-only navigation and the agreed screen-reader combination. No unresolved high-priority failure may remain in this journey at acceptance.
Review my procurement documentsStandards testing identifies failures against agreed requirements. Research with disabled users answers a different question: how well people can complete real tasks. It is not included by default, but we can help define it for critical or complex services.
We can review or draft the technical content of your accessibility statement using the applicable national model. Your organisation remains responsible for approving, publishing and maintaining it. The European Commission’s model says its accuracy should be reviewed regularly and at least once a year; national rules may be more specific.
If you are still gathering the basic information, the free helper can create a first draft structure. Treat it as a starting point; the final statement should reflect real findings, known limitations and the applicable national requirements.
Use the statement helperHow the Directive, EN 301 549 and WCAG relate to each other.
Read the European Commission guideThe official text covering scope, accessibility statements, feedback and enforcement.
Read the DirectiveThe required statement structure and recommendation to review it at least annually.
Read the implementing decisionLegal and standards references checked on 6 October 2026.
Send the website URL or procurement documents, country, target date and priority journeys. Within two business days, we either send a fixed-scope proposal or tell you exactly what information is still needed.