JavaScript required. SecurePDF AI processes files in a hardened, isolated worker — the upload, progress, and download UI all run client-side over a JS-driven channel. Please enable JavaScript in your browser and reload this page to continue.

Accessibility Statement

SecurePDF AI is committed to making our PDF tools usable by everyone, including people who rely on assistive technologies. This statement describes the accessibility standards we follow, the platforms we support, known issues we are tracking, and how to reach us when something does not work for you.

Last updated: 2026-05-17

1. Standards Conformance¶

SecurePDF AI targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. WCAG 2.1 AA is the standard cited by the U.S. Section 508 Refresh, the EU Web Accessibility Directive (Directive 2016/2102), and EN 301 549. In practice, this means we aim to provide:

Perceivable content: sufficient color contrast (at least 4.5:1 for body text, 3:1 for large text and meaningful UI components), text alternatives for non-text content, and a layout that adapts to 400% zoom without loss of functionality.
Operable interface: full keyboard navigation, a visible focus indicator on every interactive element, no keyboard traps, and no content that flashes more than three times per second.
Understandable behavior: consistent navigation, clear form labels and error messages, and predictable interaction patterns across tools.
Robust markup: semantic HTML landmarks, valid ARIA attributes, and component patterns that work with current and future user agents.

We test against these criteria as part of our development workflow. Conformance is an ongoing process; we treat accessibility regressions as bugs and prioritize them alongside other defects.

2. Compatibility¶

SecurePDF AI is designed to work with the latest two major versions of the following browsers:

Google Chrome (desktop and Android)
Mozilla Firefox
Apple Safari (macOS and iOS)
Microsoft Edge

We test our interface with the following assistive technologies in combination with the browsers above:

NVDA (Windows, Firefox and Chrome)
JAWS (Windows, Chrome)
VoiceOver (macOS Safari, iOS Safari)
TalkBack (Android Chrome)
Keyboard-only navigation on all supported browsers
Browser zoom and OS-level text scaling up to 400%

SecurePDF AI is not optimized for browsers more than two major versions behind current. If you must use an older browser, core file-processing functionality should still work, but some visual polish and keyboard shortcuts may not be available.

3. Known Issues¶

We are transparent about accessibility barriers we know about. The following items are tracked and prioritized for resolution:

PDF preview canvases: the in-browser PDF preview is rendered to a <canvas> element and is not directly readable by screen readers. Filenames, page counts, and processing status are exposed in accessible text alongside the preview, and all tool actions can be completed without relying on the preview.
Drag-and-drop reordering: the merge and reorder tools support pointer-based drag-and-drop. We provide keyboard equivalents (move-up and move-down buttons) for every reorder operation, but the drag affordance itself is mouse- and touch-oriented.
Generated output PDFs: SecurePDF AI processes the files you upload but does not modify their internal accessibility metadata. If the source PDF lacks tags, reading order, or alt text, those will still be missing in the output. Use a dedicated authoring tool if you need to add structural accessibility tags to a PDF.

This list is not exhaustive. If you encounter a barrier that is not listed here, please report it using the feedback channel below — we will add it to this list once confirmed.

4. Feedback¶

Accessibility feedback is treated as a first-class bug report. If you run into a barrier, have a suggestion for improvement, or need content in an alternative format, contact us:

Email: [email protected] with the subject line "Accessibility feedback."
Please include the page URL, the browser and assistive technology you were using (including versions), and a description of what happened versus what you expected.

We aim to acknowledge accessibility reports within 5 business days and to provide a resolution timeline within 10 business days. Where a fix is not immediately possible, we will offer an equivalent alternative.

5. Statement Date¶

This Accessibility Statement was prepared and last reviewed on 2026-05-17. It is reviewed at least annually and after any substantial change to the user interface. The most recent revision date is reflected at the top of this page.