Listening field note
How is Passagekeep designed for accessible use?
The application uses semantic landmarks, labelled native controls, keyboard-operable menus and dialogs, visible focus, status announcements, reflow, reduced-motion handling, forced-colour support, and automated WCAG-oriented scans.
No pointer-only core workflow
Transcript selection, passage editing, filtering, edition freezing, and downloads use standard buttons, links, forms, and dialogs. Write the decision in plain language and retain the original source separately so the index can be audited against something outside the browser project.
Responsive reading order
The workroom collapses its listening rack and room rail without changing semantic order, and exact transcript text remains available as selectable text. Review the result as a retrieval aid rather than a conclusion. Human-authored fields must remain visibly distinct from exact source-derived text.
Human launch testing is still required
Automated scans do not replace screen-reader, zoom, keyboard-only, forced-colour, reduced-motion, and real-device sessions with representative users. Carry the limitation into the frozen edition and passive handoff so a recipient can understand what was checked, what was not checked, and what remains their responsibility.