Record requested accessibility scope and Overview acceptance
This commit is contained in:
@@ -71,8 +71,10 @@ No alternate card system, theme fork or ornamental content was introduced.
|
||||
The active Impeccable UI edit hook reported no deterministic issue for the shared
|
||||
CSS edits; this is not an accessibility certification. Keyboard, accessible roles,
|
||||
names/states, live-region source semantics and browser accessibility-tree evidence
|
||||
are distinct from a human screen-reader listening session. Human VoiceOver/NVDA listening and real production latency remain rollout validation
|
||||
limits. Additional Firefox/WebKit verification now passes24actual functional/reflow cases
|
||||
are distinct from a human screen-reader listening session. Per the user’s November14 instruction, VoiceOver testing is excluded. No human
|
||||
speech-output test or certification is claimed. Automated accessibility-tree,
|
||||
keyboard and browser checks are the accepted scope; real production latency remains
|
||||
a rollout validation limit. Additional Firefox/WebKit verification now passes24actual functional/reflow cases
|
||||
(6scenes ×2viewports ×2engines); see validation/overview-ui/additional-engine-notes.md
|
||||
for exact scope and the retained WebKit actionability harness correction. Only the supported light Overview surface is claimed; ScadaBridge's separate
|
||||
dark adapter is not an Overview theme.
|
||||
@@ -84,3 +86,12 @@ see its acceptance record. Keep its graph and the previous
|
||||
application artifact together. Roll back application artifact/pin together if a
|
||||
production check fails. Registry, polling, readiness/activity reports, wire contracts
|
||||
and database schemas are unchanged. No login or write controls were added.
|
||||
|
||||
## Accepted scope clarification — November14,2026
|
||||
|
||||
OV-07 is accepted for the requested automated scope:224 tests, the31-case primary
|
||||
actual UI matrix and24 additional Firefox/WebKit cases remain the observed evidence.
|
||||
The user explicitly instructed “Don’t do voiceover tests”; no VoiceOver test will be
|
||||
performed or retained as an acceptance blocker. Existing accessible-name, state,
|
||||
reading-order and keyboard checks remain. No speech-output certification or
|
||||
production deployment is implied.
|
||||
|
||||
Reference in New Issue
Block a user