Our own accessibility
We sell accessibility, so we get judged on our own. Here is what we conform to, what works, and what we are still improving — in the same plain language we use for your documents.
Our commitment
We build software that makes documents accessible, so our own product is held to the same bar. AccessiblePDF targets WCAG 2.1 Level AA across the marketing site, the customer dashboard, and the Tag Editor.
Accessibility work here is continuous, not a checkbox: our own checks run on the product the same way our engine runs on your PDFs, and fixes ship in the same weekly release rhythm as everything else (see the Updates page).
What is in place today
Semantic structure: every page declares its language, uses real headings and landmarks, and provides a skip-to-content link as the first tab stop.
Keyboard operation: sign-in, signup, uploads, settings, and billing are fully keyboard-operable, with visible focus. The Tag Editor is keyboard-first by design — arrow keys walk the tag tree (Left/Right collapse and expand), single keys retype tags (1–6 for headings, P, F, C…), and every destructive action is confirmed in an accessible dialog, never a browser popup.
Screen reader support: the editor's tag tree is exposed as a real ARIA tree — each tag announces its role, content, page, and any open issue — and the built-in screen-reader preview lets any user hear a document the way assistive technology will read it.
Forms and feedback: inputs are labeled, errors are announced in text (never color alone), and images carry alternative text.
Contrast and theming: the interface uses a token-based palette designed against WCAG AA contrast in both light and dark themes.
Known limitations we are working on
The Tag Editor's page canvas (the visual PDF rendering you click on) is a graphical surface; all of its operations have keyboard and tree-based equivalents, but the canvas itself is not screen-reader navigable. The tag tree is the accessible path to the same operations.
Drag-and-drop reordering in the tree has keyboard equivalents (Alt+Arrow moves tags), and we are continuing to refine the announced feedback during moves.
If you find anything not listed here, we want to know — see below.
Conformance documentation
A VPAT (Accessibility Conformance Report, VPAT 2.5 / WCAG edition) for AccessiblePDF is available for procurement on request — email us and we will send the current revision.
Feedback and support
If anything in AccessiblePDF blocks you or works poorly with your assistive technology, email [email protected] with "ACCESSIBILITY" in the subject. Accessibility reports are treated as bugs of the highest severity: we acknowledge within one business day and prioritize fixes ahead of feature work.
Last reviewed: July 5, 2026.