Public signal source overview
See how Accesserty separates certification, recognition, badge, award, and accessibility statement sources, including the boundary and limits of each source family.
Review source overview ::: Accessibility certifications, recognitions, awards, and badges Accessibility statements Accesserty ALLY User reports Machine scan summaries
Accesserty Public Accessibility Data
Accesserty organizes public accessibility statements, certification-like records, source summaries, regional counts, and dated data notes so public accessibility clues are easier to cite, inspect, and understand.
Why separate these signals?
Public Data is the reference layer behind Accesserty. It organizes public accessibility statements, certifications, recognitions, badges, and awards so they can be read by region, source, and data note.
Website accessibility is not a single score, and one visible accessibility badge, certification record, or accessibility statement cannot prove everything about a site. People encounter different kinds of information while searching, browsing, reporting barriers, and completing tasks.
Accesserty calls these pieces of information accessibility signals. Their value is that they make status easier to notice, trace, and discuss. They are not a full audit, accessibility certification issued by Accesserty, or legal compliance guarantee.
Signals Accesserty currently uses
Public web accessibility certification, recognition, website-category award, or accessibility badge records from governments, delegated authorities, or trusted organizations.
They show that a source published an accessibility-related public record for a website, service, or selected pages. Signal keeps the source, issuer, level, date, and original link traceable.
They may not cover a whole domain, every sub-service, every page, or later changes. Systems, levels, validity rules, and standard versions differ by region and organization.
Website accessibility statements published by sites, often describing standards, known limits, improvements, and feedback channels.
They show that a website publicly explains its accessibility status and contact path. For users, they provide an entry point for understanding and reporting barriers.
A statement is not third-party certification and does not guarantee ongoing maintenance. A clear statement with limits and feedback process is more meaningful than a broad promise.
A reviewed signal that a verified domain maintainer is actively maintaining accessibility.
It shows that a maintainer verified the domain through Pulse and passed Accesserty ALLY review. ALLY appears first because it is tied to ongoing report handling.
ALLY is not an accessibility certification or whole-site compliance guarantee. It may be revoked when report handling or maintenance no longer meets the expected standard.
Issue types and page context submitted by users who encounter accessibility or usability barriers.
They show that someone encountered a barrier in a real use context and left a concrete clue. Reports are sent to Accesserty first; verified maintainers can review and handle Signal reports for their domains in Console.
One report does not always identify the root cause, and it does not guarantee a response. Reports for unclaimed domains may not be made available to website owners or resolved; they are not formal legal complaints or official support requests to the website owner.
Automated checks in Pulse and DevCheck that surface machine-detectable WCAG A/AA and best-practice risks.
They can quickly identify missing labels, ARIA errors, some contrast problems, and structural issues, making it easier to decide where to inspect first.
Machine scans cannot judge all semantics, content quality, task completion, or assistive technology experience. They do not replace manual review, assistive technology testing, or legal compliance analysis.
How Signal orders these signals
Accesserty Signal orders search-result signals by traceability and maintenance relationship so weaker signals do not appear ahead of stronger ones.
- Accesserty ALLY: a reviewed active-maintenance signal for a verified domain.
- Certified / Recognized / Awarded: public accessibility certification, recognition, award, or badge records, labeled according to the source type.
- Accessibility Statement: a public accessibility statement published by the website.
- When no supported record is matched, Signal shows no badge. That does not prove the site is good or bad.
What these signals cannot prove
Signals make information more visible, but they should not be overread.
- They cannot prove that a whole website, every page, or every authenticated flow meets accessibility requirements.
- They cannot replace manual review, assistive technology testing, user research, or a full audit.
- They cannot guarantee legal compliance.
- No signal does not mean a site is inaccessible. It only means Accesserty did not match a supported public record.
Corrections, exclusions, and objections
If a domain, source, link, region, data type, or status in the public data looks wrong, outdated, duplicated, or unsuitable for inclusion, contact Accesserty.
Please include the domain, related source URL, a short explanation, and any publicly verifiable reference. Accesserty will review the public source and may correct, mark, exclude, or retain the record depending on the evidence.
Accesserty does not claim that a listed website is accessible, and absence from the data does not mean a website has done no accessibility work.
Public accessibility data hub
Accesserty’s data hub is not a website ranking or a compliance database. It organizes traceable public records into a few practical entry points so users, maintainers, and researchers can inspect sources, scope, and limits more clearly.
- Keep the original source traceable: each data path should lead back to an issuer, a website statement, or a methodology explanation.
- Explain scope before implying meaning: a record may cover selected pages, selected services, one year, or one testing method.
- Do not turn gaps into scores: not collected does not mean nothing was done; it only means Accesserty did not match a supported public signal.
Public signals by region
Browse region-level counts for collected accessibility statements, certifications, recognitions, badges, and awards, with representative website examples.
Browse regional summarySummary data downloads
Download region-level and source-level JSON / CSV summaries with generated dates, scope, and citation guidance.
View source summariesCertification, recognition, badge, and award sources
Review certification-like public sources currently supported by Accesserty, including standards, levels, date rules, and limits.
Review certification-like sourcesAccessibility statement sources
Review self-published or legally required accessibility statement sources, including official sources, daily-life three-layer collection strategy, and limits.
Review statement sourcesAccessibility statements and public explanations
Learn how to read self-published website accessibility statements: standards, scope, known limits, feedback channels, and update dates matter more than broad promises.
Read the statement guideRegional systems and collection methodology
Understand the different public traces regions may leave: certifications, statements, monitoring, complaints, procurement, or market-supervision records, and why they should not become rankings.
Understand regional data methodsHow to use these signals
Different people can start from different entry points.
- Use Accesserty Signal for search-result accessibility statements, certifications, and badges
For people who want to see public certifications, statements, and ALLY maintenance signals before opening a website.
- Review the public signal source overview
Separate certification, recognition, badge, award, and accessibility statement sources without calling every public record a certification.
- Review accessibility statement sources
Understand how Accesserty organizes official, public-sector, and daily-life website accessibility statement records.
- Verify a domain and receive reports with Pulse
For maintainers who want to verify a domain, review Signal reports for that domain, inspect interaction clues, and inspect page scan summaries.
- Learn how Accesserty handles website data
A plain-language explanation of what Pulse and Signal collect, what they do not collect, and how private data differs from public signals.
- Read the guide to public accessibility signals
Understand how badges, statements, ALLY, user reports, and machine scan summaries become traceable public clues.
- Learn how to read an accessibility statement
Look for standards, scope, known limits, feedback channels, and update dates instead of only broad promises.
- Check what to include before publishing an accessibility statement
Use examples and generators carefully by checking scope, standards, limits, feedback paths, and maintenance information.
- Understand why public records are not a permanent whole-site guarantee
Understand the scope, time, and system limits of public certifications, recognitions, awards, and badges.
- Learn about Accesserty ALLY
Understand how ALLY applications, review, and ongoing maintenance work.
Frequently asked questions
Does Certified or ALLY mean a site is fully accessible?
No. They are important signals, but they may cover selected pages, selected flows, or one point in time. A complete judgment still requires manual review, assistive technology testing, and ongoing maintenance.
Why does an accessibility statement count as a signal?
Because it provides traceable public communication and a feedback entry point. It is not certification, but it can still help users and maintainers understand what is claimed and how to report barriers.
What happens when a website has no matched signal?
Signal shows no badge. That only means no supported public record was matched by Accesserty; it does not prove whether the site is accessible.