Skip to content
PDFSamurai

Accessibility

Accessibility Statement.

Last updated · 3 November 2025

PDFSamurai is committed to making its website usable by everyone, including people who rely on assistive technology. This statement sets out where we are today and how to tell us about problems you encounter.

1. Conformance target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at the AA level. The site is built from scratch with semantic HTML, sufficient colour contrast, visible focus indicators, keyboard-first interaction, and respect for the user's reduced-motion preferences.

2. What you can expect

  • Skip-to-content link on every page.
  • Logical heading order (one h1, structured h2/h3 sections).
  • Buttons and links labelled by their visible text, with descriptive aria-labels where the visible text is decorative.
  • Form fields with associated labels and visible focus rings.
  • Drag-and-drop areas with a keyboard fallback (click to pick).
  • Reduced motion respected via the prefers-reduced-motion media query.
  • Dark mode that meets the same contrast standards as light mode.

3. Known limitations

We are aware of the following areas where we are still improving:

  • Some embedded third-party scripts (e.g. AdSense, where enabled) may inject content with their own accessibility characteristics, which we cannot fully control.
  • Drag reordering in the merge tool is functional with keyboard arrow buttons, but a screen-reader-optimised reorder flow is in progress.

4. Reporting issues

If you find a page or feature you cannot use, please tell us. We treat accessibility reports as priority bugs. Email support@pdfsamurai.co.uk with a description and, if possible, the page you were on and the assistive technology you were using.

5. Enforcement

In the UK, accessibility for public-sector websites is regulated by the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. PDFSamurai is a private service and not formally bound by those regulations, but we hold ourselves to the same WCAG 2.2 AA target voluntarily.