Accessibility
Last updated: August 2026
Paperly aims to be usable by everyone, including people using keyboards, screen readers and assistive technology. This page describes what we do and how we verify it.
What we build
- Full keyboard navigation — every tool, dialog and option can be operated without a mouse.
- Semantic HTML — real buttons, links, headings and labels instead of generic divs.
- Visible focus indicators on every interactive element.
- Screen-reader-friendly status messages for processing states and errors.
- Accessible dialogs and upload controls with labels and descriptions.
How we verify it
Every tool page is run through automated accessibility audits (axe-core) in end-to-end tests, and keyboard-focused tests exercise the main flows. We fix serious and critical issues before they ship.
Known limits
PDF documents themselves are not always accessible — a scanned PDF has no text layer, and the tools cannot add one without OCR. We do not claim full WCAG conformance for PDF content; we do work to keep the website itself accessible.
Feedback
An accessibility issue? Tell us at support@paperly.app with the subject “Accessibility” and describe what you were doing when you hit the problem.
Supported assistive technology
The site is tested with automated accessibility audits and keyboard-only interaction, and works with common screen readers including NVDA, VoiceOver and TalkBack. Because the tools are standard web pages — buttons, links, forms and dialogs — they do not require any special assistive configuration.
What we ask of the content you process
Accessibility of the site is separate from accessibility of the PDF documents you process. A scanned PDF has no readable text until OCR is run, and we cannot make an image-only document accessible without it. Tools that extract text produce output you can then make accessible in an editor.