docs(a11y): triage inherited axe gaps and prepare operator acceptance

This commit is contained in:
cesnimda
2026-10-10 20:19:16 +02:00
parent cf847e9b25
commit 4faeb96faf
4 changed files with 15587 additions and 0 deletions
@@ -0,0 +1,13 @@
# P5-15-02 — Responsive and accessibility audit
Start `cf847e9b256d9aec733abf3f37c42852c9dd2421`, development `codex/ui-redesign-phase4`, 2026-10-10. Production `main` remains unchanged and **NO-GO**. This is an audit of the existing product, not remediation or completion of full Phase 5.
## Independently reviewable baseline/operator checkpoint
[Axe triage](AXE_TRIAGE.md) reconciles the authoritative inherited **267 scans / zero violations / 2,041 incomplete node occurrences** from actual R-03 output. [Manual acceptance](MANUAL_ACCEPTANCE.md) covers all 13 requested areas with operator/version/device, expected/observed announcements and explicit result fields. The owner reports a screen-reader operator available; actual workflow results remain pending and NOT VERIFIED. No physical touch or software-keyboard acceptance is inferred.
The binding sources are the [Phase 5 plan](../../PHASE5_PLAN.md), [parent acceptance programme](../README.md), [57 contracts](../PRESERVATION_ACCEPTANCE.md), [Phase 3 accessibility](../../../phase-3/ACCESSIBILITY_PLAN.md)/[responsive strategy](../../../phase-3/RESPONSIVE_STRATEGY.md), [Phase 4 acceptance](../../../phase-4/p4-06/README.md), P5-01–14 implementation evidence and all three functional repair records. Historic Phase 3 shell prose says below768; current shell uses1024. CV mode switches below900 independently of the1024 layout boundary; audit actual implementation and record that discrepancy rather than changing breakpoints.
Fresh keyboard/native viewport, explicit WCAG 2.2 target-size, genuine Chromium tab zoom, text-spacing and emulated-touch checks are being collected. Their results and acceptance decision are **not yet established by this baseline checkpoint**. Browser automation, DOM inspection and agent screenshot review are distinct from independent human/assistive-technology evidence. Collection success will not imply every measured product check passes.
P5-13 remains deferred/unqualified/Production-withheld: 0/366 qualification calls, zero human semantic reviews, no AI-review UI. Do not activate it or run provider/Docker work. F04, current production backup/tested restore, configuration/schema/secrets verification, rollback and deployment evidence remain open. Saved-search, Rules and AUTH-01 repairs, CV revision/source/frozen package and renderer geometry are preserved; no application changes are authorized by this record.