Accessibility Statement

EditPDF AI is a tool people use for real work — resumes, contracts, forms, coursework. It should be usable by everyone, including people who use a screen reader, navigate by keyboard alone, rely on high-contrast or reduced-motion settings, or use voice control. We target WCAG 2.1 Level AA as our baseline and review new features against it, but we do not claim full conformance today — this statement is meant to be an honest account of where we are, not a guarantee.

• A visible "Skip to content" link at the top of every page for keyboard and screen-reader users, so the primary navigation never has to be tabbed through to reach the page content.
• Semantic HTML landmarks — header, nav, main, footer — and heading levels that follow document structure rather than visual size alone.
• Keyboard-operable navigation: the tool-category menu opens with Enter or Arrow-Down, closes with Escape, and returns focus to the button that opened it; the mobile menu traps focus while open and restores it on close.
• aria-expanded, aria-controls, and aria-current are set correctly on interactive nav elements so assistive technology reports the real state, not just the visual one.
• Status messages during processing (uploading, converting, loading the editor) are exposed through aria-live regions, not just a visual spinner.
• prefers-reduced-motion is respected: decorative animation (the homepage hero, scroll-triggered reveals, the mobile shortcut bar) is disabled or replaced with a static equivalent when a visitor has reduced motion turned on.
• Interactive controls meet a minimum touch/click target size on mobile layouts.

An internal audit found color-contrast issues on some of our tool pages — mainly small muted labels and decorative accent text on the PDF editor, the AI form filler, and a few other tool workspaces. These are real, currently unresolved gaps, not hypothetical ones, and they are next in line for a dedicated visual pass rather than a point fix, since contrast changes need to be checked against the rest of each page's design system.

If you rely on assistive technology and hit something that blocks you — not just something that looks slightly off — please tell us. We would rather hear about a real barrier from someone using it than find it in an audit months later.

Some tool pages embed PDF rendering and processing libraries (for previewing and editing documents in your browser) that we do not author ourselves. We choose and configure these libraries deliberately, but we cannot guarantee every internal control they render meets the same standard as the rest of the site. Where we're aware of a specific limitation in a third-party component, we note it in this statement as we find it.

If you experience an accessibility barrier anywhere on EditPDF AI, we want to hear about it — specifically:

• What page or tool you were using
• What assistive technology or settings you were using (screen reader, browser, OS, zoom level, etc.)
• What happened, and what you expected to happen instead

Email us at support@editpdfai.com and we'll follow up directly. We can't promise a fixed timeline for every report, but every one gets read by a person, not routed to a form.

We'll update this page as our accessibility work progresses — both to record fixes and to add gaps we find that aren't listed yet. The date at the top reflects the last real change.