Legal and Policy
Accessibility
Accessibility defines one part of the legal, disclosure, or policy surface behind public CITAQ routes.
Accessibility defines one part of the legal, disclosure, or policy surface behind public CITAQ routes.
These routes exist to answer specific questions cleanly, support search and AI discovery, and push readers into the most relevant adjacent systems.
Key Points
What matters on this route
Accessibility defines one part of the legal, disclosure, or policy surface behind public CITAQ routes.
Accessibility owns its own schema treatment instead of relying on a homepage-wide structured-data bundle.
This route should link laterally to related docs, trust pages, solutions, or resources depending on its topic.
Focused knowledge pages strengthen the discovery graph and reduce ambiguity around the CITAQ model.
Route Detail
How this page fits into the CITAQ system
Accessibility defines one part of the legal, disclosure, or policy surface behind public CITAQ routes.
CITAQ needs discrete public knowledge routes because verification, trust, evidence, legal boundaries, and implementation are not the same subject.
Each knowledge route should act as a bridge into the adjacent public systems instead of behaving like a dead-end article.
Connected Routes
Keep moving through the route graph
Use the trust hub to connect legal boundaries back to public verification meaning.
The verification disclaimer remains the core point-in-time trust boundary route.
Use the docs system for policy explanations and supporting reference material.
Evergreen resources can simplify the surrounding concepts for non-legal audiences.
Next Step
Move back into the trust system after reviewing the policy boundary.
These legal routes exist to constrain and clarify the public trust architecture, not to stand apart from it.
Return to Trust Center