# Screen reader and programmatic verification record for sample 3 Date: October 4, 2026. Additional evaluation performed after the cancelled physical VoiceOver setup. All data synthetic. ## Method and evidence boundaries Playwright 1.63.0 in isolated headless Chromium 153.0.8010.12 and WebKit 26.6; Guidepup Virtual Screen Reader 0.33.0, bundled with esbuild 0.28.2, running over the actual loaded browser DOM. No owner Chrome profile, VoiceOver, system authorization, or jsdom fixture was used. Browser instrumentation was injected using Playwright evaluation; the public CSP and application source were unchanged. WebKit Option+Tab reaches all controls without changing macOS/Safari preferences. `accessibility-tree-live--.yml`: Playwright ariaSnapshot, a computed semantic representation. `native-ax-live-chromium-.json`: additional Chromium CDP native AX tree. WebKit native platform AX was not captured. `accessibility-details-live-*.json`: accessible names and descriptions calculated by dom-accessibility-api, required/invalid/value/checked properties, actual focused element, live-region attributes and scoped headers. ariaSnapshot alone does not serialize every description/live property, so these complementary records are required. `virtual-sr-transcript-live--.txt`: actual per-phrase output from a complete virtual traversal of that state, ending at end of document. `*-event.txt`: continuous virtual-reader log across the application mutation; no manual move to the status region. `axe-vsr-live-*.json`: zero WCAG A/AA violations for every captured state. `sr-evidence-validation-live.json`: explicit assertions on the captured output. `../../virtual-sr-results-live.json`: complete run, 42 states across both engines. These are simulated speech phrases, not recorded VoiceOver/NVDA audio. The simulator in Chromium includes the raw noscript fallback despite scripting being active; the real Chromium AX and ARIA snapshots exclude that fallback. Some polite live mutations produce duplicate model phrases. These known simulator differences are retained unedited, not misrepresented as real-reader behavior. Exact physical-reader timing, suppression and duplication remain untested. ## Completed HTML scenarios — Chromium and WebKit Full semantic traversal preserves heading levels and meaningful sequence. Table captions, column headers, row headers and cell text are present in both browser snapshots and virtual output. Lists expose individual items and their positions. Native Chromium AX provides additional role/name/structure evidence. The guide preserves task order, genuine ordered lists, configuration tables and six placeholder names. All task heading levels, row/column headers and the configuration image alternative appear in virtual speech. Lists restart by section. Existing docx-a11y-audit.json and docx-structure.json retained unchanged; Word native checker and actual Word speech were not run. ## Completed PDF structure checks veraPDF 1.30.2 PDF/UA-1 retest: compliant, zero failed rules and checks (`verapdf-ua1-retest.xml`). `pdf-logical-reading-order.json` / `.txt` contain actual text decoded by pdfminer using PDF fonts, keyed to each page/MCID and emitted by pypdf in depth-first /StructTreeRoot /K order. This is not merely geometric page extraction. No nonempty marked text is missing from the structure tree, no MCID is referenced twice, no non-artifact text is unmarked, and no replacement decoding character occurred. Sequence was compared with authored content, including headings, list labels, table content and expiration/configuration instructions. Figure alternatives are included where present. The record has no informative image; the guide exports its configuration-pattern alternative. veraPDF emitted font-descriptor/glyph diagnostic warnings, but the full profile reports remain compliant and the independent Unicode extraction completed. These warnings do not prove reader-specific rendering/speech behavior. No PDF or DOCX binary was changed. ## ACR disposition and remaining scope 1.3.1, 1.3.2 and 4.1.2 changed from Partially Supports to Supports. Browser tree plus virtual phrases demonstrate HTML relationships, sequence and link names; PDF logical-order/tag and retained OOXML evidence establish the downloaded documents' structures. **26 Supports / 2 Partially Supports / 22 Not Applicable**. 2.1.1 and 2.4.1 remain Partially Supports solely for downloaded-document viewer behavior: a file parser and browser DOM simulator cannot exercise the actual PDF/Word reader's keyboard functionality or exposure of heading/bypass navigation. HTML behavior passes. No measured document defect is asserted. Actual accessible-reader keyboard and heading navigation can resolve these two remaining limitations. See ../../owner-voiceover-checklist.md for the optional manual follow-up.