Skip to main content :::
:::

Accessibility Statement Sources

Accesserty Signal organizes public accessibility statements published by websites. These statements are traceable public explanation channels, not certifications, badges, scores, or Accesserty endorsements.

What this dataset does

Accessibility statement sources help users know, before or during a visit, whether a website has left a traceable explanation of accessibility status, limits, and feedback paths.

  • Collect self-published accessibility statements, accessibility declarations, accessibility pages, or equivalent public explanations.
  • Keep statement URL, domain, source type, country, daily-life category, verification date, and relevant notes available.
  • Treat statements as public signals, not third-party audit results or whole-site compliance proof.

Current source directions

Statement data comes from official or public-sector sources and from Accesserty daily-life research. The list below describes the main directions supported or researched in the product data architecture. It is not a complete global database or a quality ranking.

Official, public-sector, or regulatory statement sources

  • Italy AGID accessibility statement data
  • Luxembourg Observatoire de l’accessibilité
  • Netherlands DigiToegankelijk statement data
  • Portugal Observatório Português da Acessibilidade Web
  • Belgium federal accessibility audit / statement sources
  • France FAF / RGAA-related public data
  • Norway uustatus accessibility statement sources
  • Denmark WAS / public-sector accessibility statement sources
  • Poland digital accessibility monitoring data
  • Sweden public-sector accessibility statement sources
  • Australia and United Kingdom public-sector candidate sources
  • Estonia TTJA-related public-sector statement sources

Daily-life website statement sources

  • United States, Japan, Ireland, and Singapore
  • Australia, Canada, Germany, Spain, and the United Kingdom
  • These sources follow a three-layer strategy: start with high-impact daily-life websites, then important services and large organizations, then distributed but still useful sites.

Daily-life three-layer collection strategy

When Accesserty manually strengthens daily-life statement coverage, easy discovery is not the only criterion. The priority is whether people are likely to depend on those websites in real life.

  1. Layer 1: high-frequency, necessary, or high-impact daily services such as finance, transport, healthcare, government, telecom, utilities, retail, education, and employment.
  2. Layer 2: important but more distributed services and large organizations such as insurance, housing, public services, travel, media, platforms, and large membership services.
  3. Layer 3: still useful but more distributed websites used to close category gaps; stop when the hit rate clearly declines.

How to read an accessibility statement

A statement is not the conclusion. It should be read as an entry point, and the important question is whether it helps users understand status and report barriers.

  • Standard: whether it names WCAG, EN 301 549, local rules, or another clear basis.
  • Scope: whether it covers the whole site, selected services, apps, PDFs, authenticated flows, or unclear areas.
  • Known limits: whether it honestly lists areas that are not yet accessible or still being improved.
  • Feedback path: whether it gives a usable contact method or complaint route.
  • Update date: whether the statement appears to be maintained.

Where these records appear in Signal

Signal shows known accessibility statements when it does not match ALLY or certification-like public records. This order avoids placing self-published statements ahead of stronger public certification-like records.

  1. Accesserty ALLY: show the reviewed active-maintenance signal first.
  2. Certified / Recognized / Awarded: then show certification, recognition, badge, or award records.
  3. Accessibility Statement: if those are not found, show the statement records described on this page.
  4. When no supported record matches, Signal shows no badge and does not fall back to a machine score.

Limits to understand

Statements can improve transparency, but they should not be over-read.

  • A statement is not third-party certification or a full audit.
  • A statement may be outdated, too short, missing scope, or missing a usable feedback channel.
  • Different services, authenticated flows, or third-party components under the same domain may have different accessibility states.
  • No collected statement does not mean the website has done no accessibility work; it only means Accesserty did not match a supported public statement.

Related entry points