Skip to main content :::
:::

Why “Not Found” Does Not Mean “Not Accessible” When Collecting Public Accessibility Signals

Public accessibility signals provide clues, but not finding a statement, certification, or maintenance signal does not mean a site has done nothing. Finding one also does not mean the whole site has no barriers.


Summary

  • Accesserty collects public, traceable signals. It is not a website ranking system or a complete accessibility judgment.
  • Statements may live on a parent-company page, subdomains or paths may have different scopes, and not finding a footer link does not mean no statement exists.
  • Certifications, statements, ALLY, user reports, and machine scan summaries are all clues. Signal is designed to show clues, not make final judgments about websites.

Public signals are clues, not verdicts

Accesserty collects accessibility certifications, accessibility statements, ALLY records, user reports, and some machine scan summaries. These records share one property: they can be traced to a public source, a verified maintainer, or a concrete usage context.

But public signals are not a complete accessibility judgment. They do not replace manual review, assistive technology testing, user research, or legal conformance decisions. A more accurate description is that they help people find clues worth checking.

Why “not found” does not mean “nothing exists”

Public data collection always has boundaries. Even when a site has accessibility work in place, the signal may not be placed somewhere users or software can easily find.

  • An accessibility statement may live on a parent-company, group, or main brand page instead of each product domain.
  • Some sites place statements in the footer; others place them in help centers, legal pages, privacy pages, or external form services.
  • Not finding a footer link does not mean there is no statement. Not finding it in a sitemap does not mean it does not exist.
  • A subdomain may belong to the same service, or it may represent a different product or external system.
  • A path under the same domain is often more likely to belong to the same site, but large platforms, government portals, and multi-tenant services can still be exceptions.
  • Robots settings, JavaScript rendering, regional redirects, login walls, and site redesigns can all affect discovery.

Why “found” does not mean “the whole site has no barriers”

Finding a public signal is useful because it gives people something traceable. But that signal still needs to be interpreted carefully.

  • A certification may cover specific pages, services, versions, or points in time.
  • An accessibility statement is usually a public explanation from the site owner, not necessarily a third-party test result.
  • ALLY means a maintainer is willing to maintain reporting and response practices. It does not mean the site has no issues.
  • A user report reflects a concrete context. It should not be used to conclude that the entire site is unusable.
  • A machine scan summary only sees some machine-detectable issues. It cannot decide whether the full flow is usable.

Domain, subdomain, and path scope

Website scope cannot always be determined from a URL alone. That is why Accesserty handles display rules conservatively.

Signal does not automatically apply a parent-domain statement to every subdomain, because a subdomain may represent a different product, system, team, or third-party service. For paths under the same domain, Signal is more willing to treat them as the same site area, but it still warns that coverage may vary by page or service.

In other words, Signal shows that a traceable signal exists near this domain or path. It does not claim that the signal covers every page, flow, or sub-service.

Why Signal does not rank websites as good or bad

Ranking websites as good or bad looks simple, but it can create false conclusions. Accessibility is not a single score, and it cannot be represented only by a badge, statement, or scan result.

For users, the more useful questions are: does this site publish a statement? Is there a traceable public record? Is someone willing to receive reports? Have concrete barriers been reported? These details can support the next decision, but they should not become a ranking.

Accesserty Signal is designed to place clues where they are easier to notice so users and maintainers can find the next step. It is not designed to label websites with incomplete data.

Accesserty’s data principles

These limits are not a weakness; they are boundaries that need to be stated clearly. Accesserty uses the following principles to keep the data trustworthy.

  • Show only traceable sources, verified maintainers, or concrete report clues.
  • Do not infer internal processes or actual maintenance status that the site has not made public.
  • Do not treat “not found” as “nothing was done.”
  • Do not treat “found” as “fully conformant.”
  • Do not convert public signals into good/bad website rankings.
  • When data is uncertain, display conservatively, add scope notes, or do not display it yet.

Related pages