Accessibility
What we aim for, how it is checked on every build, and where we know we still fall short.
This notice is incomplete: the operator's name, address and contact address are not configured for this deployment.
What we aim for
We aim to meet WCAG 2.2 level AA. Every tool is meant to be usable with a keyboard alone, at 200% zoom, and down to a 320-pixel-wide screen without sideways scrolling.
This is a statement of intent backed by tests, not a declaration of conformance. Nobody has audited this site against the standard.
How it is checked
Automated accessibility checks run on every build, across the home page, a local tool, a server tool, the sign-in and registration forms, the account page and a legal notice, in more than one language. A failure blocks the release.
The page previews in the editor, forms, signature and redaction tools can be driven with the arrow keys and Enter, so a placement does not require a mouse. Layout is checked at five widths from 320 pixels up.
Where we fall short, and how to tell us
Automated checks find perhaps a third of real problems. This site has not been tested with screen readers by the people who rely on them, and the drawing surface in the signature tool has no equivalent that does not involve pointing.
If something here is unusable for you, write to [email protected] and say what you were trying to do. We will fix what we can and tell you plainly when we cannot.