Accessibility statement

ADAComply PDF is a product built by people who care about accessibility, and that includes our own website. This page explains the standard we target for adacomplypdf.com, the limits we are working on, and how to reach us if you hit a barrier. Last updated May 31, 2026.

Our commitment

Vora Studios LLC, dba ADAComply PDF, is committed to making adacomplypdf.com and the ADAComply PDF web application usable by everyone, including people who use screen readers, keyboard-only navigation, screen magnifiers, voice control, or other assistive technology. We treat accessibility as a product requirement, not a compliance afterthought.

Standard we target

We target conformance with Web Content Accessibility Guidelines (WCAG) 2.1, Level AA on the public marketing site and the authenticated web application. WCAG is the accessibility standard referenced by the U.S. Department of Justice's Title II final rule, by Section 508 of the Rehabilitation Act, and by the European Accessibility Act. Conformance is ongoing work rather than a finished state, and parts of the experience may not yet fully meet that target.

What we do

Semantic HTML with proper heading structure, landmarks, and form labels
Keyboard operability for every interactive control
Visible focus styles that meet WCAG 2.1 non-text contrast requirements
Color contrast tuned against the WCAG AA threshold (4.5:1 for body text, 3:1 for large text and UI components)
Text alternatives for informative images and icons, with decorative images explicitly marked
Resizable text without loss of functionality up to 200 percent
Respect for user preferences such as prefers-reduced-motion and light/dark system themes where applicable
Accessibility review as part of our design and development process for new features

Known limitations

We know a few areas are not yet at our target and we are working on them. If you run into any of these, please let us know so we can prioritize the fix and offer an alternative in the meantime:

Some older blog posts and third-party embeds may not carry full alt text or captions.
A small number of data tables in analytics views do not yet have complete header-cell associations.
We are still refining the screen-reader announcements for job-progress updates in the document viewer.

Assistive technology we test with

We test the product with assistive technology, including the NVDA screen reader on Windows and VoiceOver on macOS and iOS, and with keyboard-only navigation in Chrome, Firefox, and Safari. Other combinations should work, and we want to hear about anywhere they do not.

Report a barrier

If you encounter content or a workflow on adacomplypdf.com that is not accessible, email [email protected] with:

The URL or page where the barrier occurred
A short description of what you were trying to do and what went wrong
Your operating system, browser, and any assistive technology you were using

We acknowledge accessibility reports within two (2) business days and aim to resolve or provide an interim workaround within ten (10) business days, depending on complexity. For urgent situations where a barrier is preventing you from accessing a document or completing a billing action, we will provide an accessible alternative (such as an email-based workflow or a staff-assisted export) while we work on the underlying fix.

Formal complaints

If you are not satisfied with our response, you can escalate to [email protected] with "Accessibility complaint" in the subject line. U.S. residents also have the right to file an accessibility complaint with the U.S. Department of Justice or, for education-related barriers, with the U.S. Department of Education's Office for Civil Rights. EU/EEA residents may contact the accessibility enforcement body in their country.

Ongoing improvement

We review this statement and the site against WCAG 2.1 AA at least once per quarter, and after any significant redesign. When we find gaps, we track them as accessibility bugs on the same footing as any other bug, not as a separate backlog.