What a Website Accessibility Statement Must Publish — Security & GDPR article by Rui Codex

A website accessibility statement should name the organisation and the site it covers, state the conformance status against a named standard such as WCAG 2.1 Level AA, list known accessibility gaps with their workarounds, give a contact route for accessibility problems, and state the date of the last review.

Key takeaways

  • A statement is a public claim, so every sentence in it must be something you can test or explain.
  • Name the standard and level you measured against, and say which parts of the site are in scope.
  • Disclose known gaps and the workaround for each, rather than hiding them behind a full conformance claim.
  • Give a working feedback route and a review date, and update both when the site changes.

Two EU texts shape most accessibility statements. Directive (EU) 2016/2102 requires public sector bodies to publish a statement on the accessibility of their websites and mobile apps, and its text sets out what that statement must contain, including a feedback mechanism and a link to the enforcement procedure. Directive (EU) 2016/2102 on the accessibility of websites and mobile applications of public sector bodies

The European Accessibility Act, Directive (EU) 2019/882, applies from 28 June 2025 and covers products and services such as e-commerce. A private business should check its sector and services against the scope provisions of Directive (EU) 2019/882 on accessibility requirements for products and services before deciding what applies.

This article is general information and not legal or tax advice. Rui Codex offers technical implementation support for accessibility work, but it does not provide legal, tax or compliance advice, audits or certification.

What sections should the statement contain?

A useful statement has five parts: scope, conformance status, known gaps, feedback route and review date. Each part answers a question that a visitor, a customer or a regulator would ask first.

Conformance is usually measured against the Web Content Accessibility Guidelines 2.1 published by the W3C. The statement should name the version and the level, such as Level AA, so a reader knows which success criteria the claim covers.

Scope

List the domains, subdomains, apps and document types the statement covers. Say explicitly whether PDFs, embedded booking widgets, chat tools and payment pages are inside or outside the claim, because visitors reach them from the main site.

Known gaps and workarounds

Name each known failure in plain language, state which users it affects and give a workaround, such as a phone number or an alternative form. A gap listed honestly is more useful to a reader than a sentence claiming the site is fully accessible.

Feedback route and review date

Give one named channel for accessibility problems, such as an email address or a contact form, and say who reads it. Add the date of the last review so the reader can judge whether the page still describes the site.

Use this checklist before publishing:

  • Named website or app, with its domains and whether each is in scope
  • Standard and level used, with a link to the guideline text
  • Conformance status chosen from the three options in the table below
  • Known gaps, the affected user groups and the workaround for each
  • Feedback channel, response owner and the date of the last review
Tip: Write the scope section before the status. If you cannot list what is in scope, you cannot honestly claim conformance for it.

How should you state conformance honestly?

Choose one of three statuses and back it with a test you can describe. The status must match the results of the tests for the scope you declared, not the intent behind a planned redesign.

StatusWhen it fitsWhat the statement must add
Fully conformsEvery criterion in the declared scope passed the tests you ranThe test method, who ran the tests and the review date
Partially conformsSome criteria fail, and the failures are listedEach failing criterion, the affected users and the workaround
Does not conformCore tasks fail, or no testing has been done yetAn honest account of the gap and a plan you can keep

A full conformance claim reads well but is the easiest to disprove, because one missed control falsifies it. Partial conformance takes more words but survives a reader who tests the site with a screen reader. Automated scanners can test only some WCAG criteria, so a clean scan is not evidence of full conformance on its own; manual checks with a keyboard and a screen reader are still needed.

Where do accessibility statements fail?

Statements fail when they claim more than the testing supports, when the scope leaves out the pages people actually use, or when the contact route does not reach anyone. Each failure has a mechanism that can be prevented.

A template copied from another website is the most common cause. The copied claim names a standard, a level and a status that were never tested on your own pages, so the statement describes someone else's site. Third-party widgets cause a second failure: a booking or chat tool loads on your pages but is left out of scope, so a visitor blocked by it has no route to report the problem. A third failure is staleness, where a redesign goes live and the review date stays at the original launch.

Hypothetical examples of weak accessibility statements

Here are two hypothetical scenarios:

Scenario one. An online shop publishes a full conformance claim, but its checkout uses a payment provider's embedded form that nobody tested. The statement should either declare the checkout out of scope or list the embedded form as a known gap with a workaround, such as a contact route for placing orders.

Scenario two. A consultancy's statement gives a contact form, but messages go to a shared mailbox with no named owner. A visitor reports a problem and receives no reply, so the feedback route exists on paper only. The fix is a named owner and a documented response process, written into the statement.

How do you keep the statement accurate?

Keep it accurate by assigning one owner, re-testing after each major change and updating the review date every time. The statement is only as current as the last test, so its owner should sit inside the release process rather than handle a yearly reminder.

Re-testing has a cost: each release adds manual checks, and a team that skips them will drift away from its statement. Changing the statement without changing the site is worse, because the claim then records intent rather than fact. Fixing a shared template or component can also repair many pages at once, which makes the next review cheaper.

Rui Codex offers technical implementation support through its web development services, including fixes to templates and components that a statement depends on. Custom interfaces for internal tools fall under custom software development. For the data and privacy side of the same site, the security, GDPR and compliance guides cover related ground.

Tip: Put the statement's review date in the same release checklist as your tests, so that one cannot change without the other.

Frequently Asked Questions

Does every business website need an accessibility statement?

Not every business website is required to publish one, because the obligation depends on the sector, the services offered and the country. Check the scope provisions of Directive (EU) 2019/882 and the rules in your national law before deciding. Publishing a statement voluntarily is still useful, because it gives visitors a feedback route and a plain account of what works.

Which WCAG level should a statement name?

A statement should name the level you actually tested. Level AA is a common target, but a statement that says AA while only checking Level A is inaccurate. Name the version as well, because WCAG 2.1 and WCAG 2.2 contain different success criteria.

How often should the statement be reviewed?

Review the statement whenever a change affects the tested pages, and also at a regular interval set by the owner. The review date must reflect the most recent test, not the date of the first version. A fixed interval is a sensible floor when the site changes often, provided each review involves real testing.

Can a developer write the accessibility statement alone?

A developer can supply the test results, the list of known gaps and the technical workarounds, but the statement is a published claim that the organisation owns. Someone with authority over the site should approve the scope and status before publication. Splitting the work this way keeps the technical facts accurate and makes the owner accountable for the claim.

Conclusion

An accessibility statement is a short public document with a long duty: it must describe the site as it is, not as the team hopes it will become. Publish the scope, the standard and level, the honest status, the known gaps with workarounds, a working feedback route and a review date. Written this way, the statement gives visitors something they can act on and gives the owner a clear list of what to fix next. Each part can be checked, and each check keeps the statement true after publication. If your team needs help turning the gaps in a statement into tested fixes, request a project consultation through the Rui Codex contact page or email info@ruicodex.com to discuss your project.

Sources

Tags: accessibility statement WCAG 2.1 web accessibility European Accessibility Act public sector websites conformance status website compliance web development

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request