Accessibility
Find the accessibility approach and a direct way to report a barrier.
Paperlane is built to be usable with a keyboard, a screen reader, or a pointer device, and to remain usable at larger text sizes and higher-contrast display settings. This page describes that approach and how to report a gap.
Our approach#
The interface is designed for full keyboard navigation with a visible focus indicator, semantic headings and landmarks, and readable color contrast in both light and dark themes.
Longer-running operations (large file conversions, batch jobs) announce their progress and completion through accessible status updates rather than relying on a purely visual progress bar.
Known limitations#
Some third-party file previews (for example embedded PDF rendering in a browser's native viewer) inherit accessibility limitations from that underlying viewer rather than from Paperlane's own markup.
Standards we target#
We aim to meet WCAG 2.1 AA for the app shell and each tool's primary workflow. This is a target we actively work toward rather than a claim of full conformance across every screen.
Report a barrier#
If a control, workflow, or page is difficult to use with your assistive technology, please report the exact route, the assistive technology and browser you were using, and what you expected to happen. That level of detail lets us reproduce and fix the issue directly, and you can send it through the Contact page.