browserpdf
← All tools

Accessibility Statement

Last updated: July 12, 2026

We want BrowserPDF to be usable by as many people as possible, including people using assistive technology. This statement describes what's actually been done, and where we know it falls short, rather than claiming a level of compliance we haven't independently verified.

Standard we aim for

We use the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as our target. This statement reflects an ongoing, good-faith effort built into the site's markup and styling; it is not a certified audit.

What's in place

  • Semantic HTML throughout: proper heading hierarchy, landmark regions (header, main, footer), and native form controls (real checkboxes and buttons, not custom widgets faking them) wherever practical.
  • Keyboard access. Every interactive element, including the drag-and-drop upload zones, can be operated from the keyboard (Tab to focus, Enter/Space to activate), with visible focus outlines.
  • ARIA labeling on controls whose purpose isn't obvious from visible text alone, such as the upload zones, page-selection tiles, and icon-only buttons.
  • Color and motion. Both light and dark themes are designed for reasonable contrast, and animations are minimized for users with prefers-reduced-motion enabled.
  • Error and status messaging uses role="alert" so screen readers announce problems as they happen, not just silently on screen.

Known limitations

  • The Split tool's page thumbnails are rendered as canvas images for visual page selection; a screen reader cannot see the page content itself, only the "Page N" label. Selecting by page number rather than content is a real limitation for non-visual use of that tool.
  • Generated Markdown output quality in the PDF to Markdown tool depends on heuristics and OCR accuracy, not an accessibility feature, but worth noting if you're relying on it for downstream accessible content.
  • This statement is not the result of a professional accessibility audit. If you rely on assistive technology and hit a barrier we haven't listed here, please tell us.

Feedback

If you encounter an accessibility barrier anywhere on this site, let us know at info@browserpdf.app and we'll look into it.