Accessibility
Accessibility statement
We build Sannor to be operable by keyboard and assistive technology. This page describes what is in place today and where we are still working — we do not claim a formal WCAG audit we have not completed.
Our goal
We aim for the substance of WCAG 2.2 AA — sufficient contrast, semantic controls, labelled form fields, and predictable keyboard order — and treat it as the bar for new interactive surfaces. We have not yet completed a formal third-party conformance audit.
Keyboard and non-gesture operation
The review queue is fully keyboard-driven (Approve / Revise / Discard shortcuts plus arrow-key navigation). The content calendar supports drag-and-drop but also offers a keyboard ‘Move to date’ control, so rescheduling never depends on a pointer gesture. The Content Studio editor exposes its inline AI editing through focusable buttons and a text field, not just selection gestures.
Focus and dialogs
Modal dialogs — preview-before-publish, discard, and mark-for-revision — move focus into the dialog on open, keep Tab within it while open, close on Escape, and return focus to the control that opened them.
Status announcements
Asynchronous results — approving or sending back a draft, posting a comment, rescheduling with conflicts, and analytics answers — are surfaced through ARIA live regions and alert roles so screen-reader users hear them. Loading and error states carry text or an icon, not colour alone.
Ongoing work
Accessibility is reviewed surface by surface as we build, with keyboard and screen-reader passes before release. Coverage is not uniform across every older screen yet. If you hit a barrier, contact our support team and we will prioritise a fix.