Accessibility / route health
A measured view of the production surface — where every route is accounted for, every shared pattern is visible, and the next fix is easy to find.
One shared pattern explains the dominant warning. One route deserves its own structural pass.
The same shared-footer issue reproduced on every audited route.
This route-specific issue was isolated to /crystalcore-os.
Use a persistent non-colour cue and the canonical ivory token across all routes.
Inspect heading order independently; the footer patch will not affect this finding.
Route register
| Route / cohort | Coverage | Accessibility | Finding | Status |
|---|---|---|---|---|
| All audited routes | 57 prerendered routes | 0.95–0.96 | Shared footer link distinction | Healthy |
| /atlas-ten | Named focus route | 0.95–0.96 | Shared footer link distinction | Healthy |
| /crystalcore-os | Named follow-up route | 0.95 | Shared footer link distinction · heading-order | Review |
◈ The register shows named focus routes plus the full audited cohort. Every route returned HTTP 200.
Audit notes
This dashboard reflects the supplied route-audit report, not a live telemetry stream. It preserves the distinction between measured findings and recommended remediation.
57 of 57 concrete prerendered routes returned HTTP 200.
Every route included the shared footer component.
Accessibility audits completed after a lower-concurrency retry.