Production control note
How is Placeproof designed for accessible use?
The development build uses semantic landmarks, labelled native controls, keyboard-operable dialogs and menus, visible focus, live status, reflow, reduced-motion and forced-colour handling, and automated WCAG-oriented scans across public and private surfaces.
Core actions are not pointer-only
Guests can be assigned through labelled selects; navigation, editing, proof freezing, comparison, downloads, and restore use native controls. Preserve the owner’s authoritative source outside the browser project and label every assumption that remains unverified.
Dense data reflows
The production rail becomes a room selector on small screens, guest rows shed nonessential columns, and tables remain in the document reading order. Review the result as production evidence, not as a recommendation or professional approval; the responsible people remain accountable for the decision.
Manual testing remains a launch gate
Automated scans do not replace screen-reader, keyboard-only, zoom, forced-colour, reduced-motion, mobile, print-preview, and representative-user sessions. Carry this limitation into the proof and handoff so a fresh recipient knows what changed, what was checked, and what still requires human confirmation.