DocAccessible
Legal

Accessibility statement

DocAccessible's public accessibility statement. Conformance target (WCAG 2.2 Level AA), known limitations, assistive-tech compatibility, and how to report a barrier.

Updated April 22, 2026. Reviewed by the DocAccessible team.

Our commitment

DocAccessible is an accessibility product. Our own web application, marketing site, and hosted document pages are built to the same standards we apply to our customers' documents. Accessibility is a product requirement for us, not an afterthought.

Conformance status

docaccessible.com is designed to conform with Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 AA is a backward-compatible superset of WCAG 2.1 AA, the standard named in ADA Title II and Section 508. It is the current W3C recommendation.

“Conformance” means the product has been tested against WCAG 2.2 Level AA and meets the requirements. Where there are known gaps we disclose them below. Our VPAT provides a full criterion-by-criterion conformance report for procurement teams.

Standards covered

  • Web Content Accessibility Guidelines (WCAG) 2.2, Level A and AA.
  • Revised Section 508 Standards (36 CFR Part 1194), which reference WCAG 2.0 AA and are fully covered by our 2.2 AA target.
  • ADA Title II (28 CFR Part 35) technical standard (WCAG 2.1 AA), with compliance dates of April 26, 2027 (50k+ entities) and April 26, 2028 (smaller entities), per the DOJ interim final rule dated April 20, 2026.
  • EN 301 549 V3.2.1 (European harmonised standard) for clauses referencing WCAG 2.1 AA.

How we test

  • Automated. Every CI build runs axe-core and Playwright accessibility checks against the authenticated and public surfaces of the app.
  • Manual. Keyboard-only walkthroughs, screen-reader smoke tests (VoiceOver on macOS/iOS, NVDA on Windows, TalkBack on Android), and 200%-zoom reflow checks on each release candidate.
  • Third-party. Annual audit by an external accessibility firm against the WCAG 2.2 AA checklist. The most recent audit was completed in Q1 2026.

Assistive technology compatibility

docaccessible.com is designed to work with the following combinations. If you encounter a barrier with any of them, please contact us.

  • macOS 14+ with Safari 17+ and VoiceOver.
  • Windows 11 with Microsoft Edge or Firefox and NVDA 2024.x or JAWS 2025.
  • iOS 17+ with Safari and VoiceOver.
  • Android 14+ with Chrome and TalkBack.

Document pages we host at /d/<slug> are plain semantic HTML with a skip link, visible focus indicators, and a reading-order checked by the editor before publish.

Known limitations

Despite our best efforts, a small number of issues remain. We document them openly and track a fix target date for each. These are the current known limitations as of April 22, 2026:

  • BlockNote editor - alt-text drag reorder. Dragging alt-text entries in the inspector panel does not announce drop position in JAWS. Keyboard reorder (ArrowUp/ArrowDown) works and is the documented method. Targeted fix Q2 2026.
  • Complex data tables. Tables with merged cells and spans import as-is; our heuristic does not always infer the right row/column groups. The editor lets reviewers correct headers per table. Improvement planned Q3 2026.
  • Scanned PDFs without OCR. We flag pages without extractable text and prompt the user to run OCR before remediation. This is a source-content limitation rather than a product defect.

Report a barrier

If you find a page, feature, or hosted document that is hard to use with assistive technology, we want to know. We reply within two business days.

Please include the page URL, the device and browser you used, the assistive technology (if any), and a brief description of what went wrong. Screenshots or short screen recordings are helpful but not required.

Formal complaints

If you are dissatisfied with our response, you may file a complaint with the appropriate enforcement agency in your jurisdiction. In the United States, that is usually the U.S. Department of Justice Civil Rights Division (ADA) or the U.S. Access Board (Section 508). We will cooperate with any investigation.

Review cadence

This statement is reviewed quarterly and on every major release. The last review was April 22, 2026.