docs(a11y): record final responsive acceptance failures and evidence
This commit is contained in:
@@ -4,7 +4,11 @@
|
||||
|
||||
[02 audit](p5-15-02/README.md), [native coverage](p5-15-02/TEST_COVERAGE.md), [findings](p5-15-02/DEFECTS.md), [reflow measurements](p5-15-02/RESPONSIVE_RESULTS.md) and [manual packet](p5-15-02/MANUAL_ACCEPTANCE.md) now supersede the prior “02 not started” statements. Application/API/renderer behavior is unchanged. Actual Chromium100/200/400 zoom is measured separately from touch emulation, screen-reader speech and physical-device/software-keyboard acceptance. Owner reports a reader operator available; actual results remain NOT VERIFIED until supplied.
|
||||
|
||||
**P5-15-02: NO-GO for P5-15-03** on confirmed P1 keyboard upload/import failure and the [native initial mobile CV/PDF mismatch](p5-15-02/evidence/mobile-preview-proof.json). Reduced-motion drawer return, source-editor404 and small report targets also need bounded disposition. [57-group matrix](PRESERVATION_ACCEPTANCE.md) now reconciles **0PASS/50PARTIAL/6FAIL/1DEFERRED/0BLOCKED/0NOT VERIFIED** while retaining every historical status column. Separate UI-rule warnings/manual gaps are not automatically failures. Complete regression/fidelity and final audit reconciliation are still being collected at this intermediate record; known failures are neither skipped nor expected-failing.
|
||||
**P5-15-02: NO-GO for P5-15-03** on confirmed P1 keyboard upload/import failure and [initial mobile CV content clipping](p5-15-02/evidence/mobile-preview-proof.json). That fixture's page count matches its PDF, but its visible content flow remains zero-width; no false page-count claim is made. Reduced-motion drawer return, source-editor404 and small report targets also need bounded disposition. [57-group matrix](PRESERVATION_ACCEPTANCE.md) now reconciles **0PASS/50PARTIAL/6FAIL/1DEFERRED/0BLOCKED/0NOT VERIFIED** while retaining every historical status column. Separate UI-rule warnings/manual gaps are not automatically failures. Known failures are neither skipped nor expected-failing.
|
||||
|
||||
Fresh complete results: **backend1,033 / frontend490 / main browser139pass+4fail across143cases**, plus the separately added native mobile/PDF diagnostic **0pass+1fail**; unique ordinary union **139pass+5fail=144**, not one144-case full execution. All134 inherited browser cases pass, including saved searches, Rules and AUTH-01. Separate diagnostics2, realHTTP2, sidecar49, focusedAI108, revision5/5, standard fidelity16/16(36=36), settings8/8(24=24), security/config9/6/1/3 and static/build/hygiene checks pass. The finite renderer corpus does not qualify the failed hidden mobile visible-page lifecycle. [Final evidence](p5-15-02/evidence/validation.json) preserves command/results and the ordinary failures.
|
||||
|
||||
Fresh **312axe scans** comprise267retained-rule scans(0reported violations,2,038incomplete nodes) and45all-enabled/target-size scans(47violation-node occurrences,374incompletes). [Per-rule triage](p5-15-02/AXE_TRIAGE.md#fresh-final-run) separates repeated nodes, best-practice warnings, confirmed native defects and required human review. Actual Chromium200/400zoom adds bounded geometry evidence; no spoken reader/physical-touch/software-keyboard acceptance is claimed. [CV Unsaved intermittence](p5-15-01/INTERMITTENT_FAILURES.md) remains OPEN. Completed logical checkpoints are individually committed/pushed; no application repairs are hidden in this audit.
|
||||
|
||||
P5-13 remains deferred/unqualified/Production-withheld0/366,0human semantic reviews, UI unimplemented. Production main remains unchanged/NO-GO; F04, current complete backup/tested restore, configuration/schema/secrets, rollback and deployed acceptance remain open. No automatic P5-15-03/04, P5-13, B07 or deployment follows from this audit.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user