docs(a11y): record postponed screen-reader acceptance

This commit is contained in:
cesnimda
2026-10-10 21:31:23 +02:00
parent 82f8c37a28
commit b369b24b73
4 changed files with 12 additions and 0 deletions
+2
View File
@@ -2,6 +2,8 @@
## Current P5-15-02 — Responsive/accessibility audit successor
**Owner update —2026-10-10:** screen-reader operator testing will be revisited later. It is logged as **NOT COMPLETE / NOT VERIFIED** in the [manual packet](p5-15-02/MANUAL_ACCEPTANCE.md#owner-scheduling-decision--2026-10-10), with mandatory acceptance retained. This scheduling decision does not change the audit NO-GO, production NO-GO or57-group preservation totals.
[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 [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.