Accessibility statement

This website (www.docomatic.ai) targets WCAG 2.2 Level AA.

We assess it as partially conformant: most content fully meets WCAG 2.2 AA, but the items listed under Known issues do not yet. We prefer stating that honestly over claiming a full conformance we have not verified.

We target WCAG 2.2 for this website because it is the current W3C Recommendation. The documents DocoMatic remediates are verified against WCAG 2.1 Level AA and PDF/UA-1, because those are the versions the ADA Title II rule and the PDF standard cite. The site is held to the newer version; the documents are held to the version the law names. See what WCAG 2.1 AA means for documents.

We have not yet published an Accessibility Conformance Report (VPAT/ACR) for the DocoMatic application. A working draft of our own evaluation is available, but it is not a final report. Its known issues are listed below; the final report will be offered on our security page once it exists.

• Automated axe-core checks run in CI against the home page in every locale (English, French, Spanish) and against a representative set of page templates in English; a failing check blocks the deploy.
• Lighthouse accessibility audits run on every change with enforced budgets.
• Keyboard-only navigation and reduced-motion behavior are covered by automated tests; animation never hides content and is disabled entirely when reduced motion is requested.
• Planned: quarterly manual audits with assistive-technology users (screen reader, magnification, and voice control), with results published in this statement.

Sections that fade in as you scroll are present in the page from the first paint: the server sends every section fully visible, the fade is applied only after the page has loaded and only to sections not yet on screen, and nothing is ever removed from the accessibility tree. With reduced motion requested, or without JavaScript, there is no fade at all.

The issues we currently know about and have not yet fixed. This list is updated as issues are found and resolved.

• The DocoMatic application

  Current issues in the DocoMatic Workbench, and the defects fixed before its draft date, are recorded in the conformance report draft with the success criterion for each; this statement does not keep a second list. The two application defects an earlier version of this statement listed here — background content not made inert behind menus and dialogs, and completed jobs not announced to screen readers — were fixed and retested on September 16, 2026 and appear there under "Fixed before this draft". Report any barrier in the application to the address below.

• Machine-translated French and Spanish copy

  French (Canada) and Spanish (US) content is currently machine-translated and pending professional review; wording and screen-reader pronunciation may be imperfect in those locales.

• Sampled testing of generated pages

  Automated checks cover a representative set of page templates and only a sample of programmatically generated pages; pages outside that set may contain issues we have not caught.

• Conformance report not yet published

  Our Data Processing Agreement (version 1.0) is published as a web page, and our security questionnaire answers are available on request through the contact page. The application's Accessibility Conformance Report (VPAT/ACR) is not published yet; only a working draft exists. Procurement documents we publish are in accessible formats (HTML or tagged PDF).

Recently fixed

Website issues found by our September 2026 review and fixed since this statement was first published, each with the date its fix shipped. An item moves here only once the fix was verified on the built site.

• September 19, 2026 · The main navigation menu could not be opened from the keyboard, and its triggers were links marked as menus rather than buttons, so screen readers announced them incorrectly. Each section is now a plain link beside a real button that opens the panel, with Escape to close (WCAG 2.1.1, 4.1.2).
• September 19, 2026 · On the deadline finder, a radio group and its hidden native controls had no accessible name, and required fields on it and the contact form were not marked required for assistive technology (WCAG 3.3.2, 4.1.2).
• September 18, 2026 · The question-and-answer sections on the product pages nested a heading inside another heading, which broke the reading order they presented to a screen reader; each question is now exactly one heading (WCAG 1.3.1).

If you encounter an accessibility barrier anywhere on this site, email [email protected]. We respond within 2 business days, and we will provide the content you needed in an accessible form while we fix the underlying issue.

The two-business-day acknowledgement is a published commitment: Service Levels and Support, section 6.7.

Accessibility complaints follow the same channel and are escalated to the engineering owner of this site. We do not use accessibility overlays; issues are fixed in the source.

If our first reply does not resolve the barrier, reply to it and ask for the report to be escalated; it is then handled by the engineering owner of this site. The contact page lists the other ways to reach us.

• WCAG 2.2 (Level AA) — the standard this website targets.
• PDF/UA (ISO 14289) — the standard our remediated documents are verified against, alongside WCAG for document content.
• WAI-ARIA Authoring Practices — for the behavior of interactive components such as menus and disclosures.