Skip to content

Test your website now

Free, no card. We read only public pages.

Run free audit →

Compliance · Low severity

Accessibility Statement Missing: Check Scope and Publish Accurate Information

Review missing accessibility information. Identify the applicable regime, publish evidence-based details, and separate link recognition from actual access.

Published · Updated

What the check tests

Check
comp.accessibility-statement - Accessibility statement published
Passes when
The site should link an accessibility statement describing conformance and how to report barriers.
Scope
graded once per site
Severity
Low
Fix effort
medium - a working day
Impact when fixed
low

In one paragraph

Accessibility statement missing means the scan did not recognise a link to an accessibility-information resource. Determine which duties apply to the organisation and service, then publish accurate accessible information and a usable feedback route. Public-sector statements and information required for covered private services have different legal frameworks. A link match does not certify accessibility, statement completeness, or the applicability of a legal exemption.

Why it matters

The EU Web Accessibility Directive requires covered public-sector bodies to publish and regularly update accessibility statements, with prescribed information and a feedback mechanism. Its scope and exceptions matter; not every organisation with a public website is automatically a covered public-sector body.

The European Accessibility Act addresses specified products and services. Covered service providers have accessibility-information duties, including information under Annex V, rather than simply inheriting the public-sector statement template. Its application and transitional provisions need review under national implementation.

The directive exempts microenterprises providing services from its relevant requirements, but that does not exempt every small organisation from all accessibility law or make product obligations identical. Do not infer legal scope from a page's design, scanner grade, or generic employee count alone.

How WebAuditOS evaluates this finding

The supplied site-wide rule matches observed link text or addresses containing accessib or specified Czech accessibility terms, using its documented rendered-link fallback. A match passes; no match with readable coverage warns at low severity; missing client-render coverage can be ungraded.

A service page or someone else's statement can pass, while legitimate local-language wording can be missed. It does not retrieve the statement to assess its truth, model, dates, feedback process, or the actual service's accessibility.

How to fix it

  1. Identify the operator, services, markets, and applicable national framework. Separate public-sector requirements from duties for services covered by the European Accessibility Act or another law.
  2. Use the relevant required format and content where applicable. Do not copy a public-sector template into a commercial service without checking that it answers the correct obligations.
  3. Publish the scope, assessment basis, known barriers, applicable alternatives, and feedback route accurately. Distinguish tested facts from plans and do not claim full conformance from an automated scan alone.
  4. For covered service information, explain the service and how relevant requirements are met in the appropriate accessible documentation, including the terms or equivalent document where required. Review national detail and exemptions with appropriate expertise.
  5. Provide a route to report barriers and obtain help. Test that messages reach an owner and that the interface itself is usable by the audience expected to rely on it.
  6. Make the resource discoverable through clear navigation. An example is:
<a href="/accessibility">Accessibility information</a>

Use a real maintained destination and meaningful localised wording rather than a placeholder built only for the detector.

  1. Review after material changes and at the cadence required by the applicable regime. Keep dates, stated scope, alternatives, and contact responsibilities current.
  2. Rescan link recognition and separately evaluate the service and statement. A missing pattern is not a legal verdict, and a pass cannot confirm a valid exemption or required content.

What the fix can break

An unsupported conformance claim can mislead people who depend on it. Use measured, reviewed wording and a truthful list of limitations.

A generic template may omit required national feedback or enforcement details, or assert an exemption that does not apply. Verify scope before publishing.

Do not hide known barriers to make the statement sound stronger. Useful transparency and actual remediation should remain aligned.

Questions

Does every private website need the public-sector template?

No. Identify the relevant service and legal regime rather than applying one document universally.

Does a microenterprise exemption settle every duty?

No. Its scope is specific, and other laws or product obligations may still need assessment.

No. This rule only recognises a link pattern.

Review privacy information, the automation limits guide, and the website audit checklist.

Standards and sources

  • EN 301 549
  • European Accessibility Act

In the report

Test this on your own site

Every scan runs comp.accessibility-statement on every page it crawls, on every plan. The finding carries this id, so a line in a report can be matched to the explanation above - and the free scan needs no account.