Product scope
DocAccessible is a web application for checking, rebuilding, reviewing, publishing, and exchanging documents. Automated output can reflow a source PDF and may not preserve its exact design. Exact-layout PDF remediation is a separate human service offered at $5 per accepted source page for projects of 501 pages or more.
Current evaluation status
We are building a criterion-by-criterion evidence set. Until that work and the necessary manual assistive-technology evaluation are complete, product-wide conformance is not yet fully assessed. Automated results are useful evidence, but they are not a substitute for a formal accessibility evaluation.
Evaluation DA-A11Y-2026-09-02 returned 0 axe-core violations in the 398 tested route and interface states. It also recorded 20,087 contrast node occurrences across 357 result records for human review. Those contrast results are neither violations nor passes.
| Area | Current evidence | Status |
|---|---|---|
| Public website and public workflows | axe-core 4.12.1 across 160 deterministic public URLs, 3 seeded public states, and 3 dark-mode and reduced-motion preference states in desktop Chromium and Chromium with Playwright iPhone 13 emulation | Automated sweep completed; manual evaluation pending |
| Authentication and core workspace flows | Fixture-backed browser checks across 18 workspace routes and 15 administrator states in both published Chromium environments, plus separate selected workflow checks | Automated sweep completed; manual evaluation pending |
| Hosted HTML output | Semantic output checks and representative automated browser checks | Requires document-level review |
| Complete WCAG 2.2 A and AA criteria | Criterion-by-criterion manual evaluation has not been completed | Not yet fully assessed |
| Revised Section 508 and EN 301 549 | A formal standards mapping has not been completed | Not yet evaluated |
How procurement teams should use this page
Treat this as a transparent readiness statement. Do not use it as proof of full conformance or as a signed ACR. If your procurement requires a VPAT, tell us the edition, applicable standards, product scope, deployment context, and due date through the procurement contact form. We will confirm what evidence is available and whether a formal assessment can be scoped. Availability and timing are confirmed in writing rather than promised on this page.
Evaluation methods needed for a formal report
- Automated testing across representative public and authenticated templates.
- Keyboard-only testing at supported viewport sizes and zoom levels.
- Screen-reader testing with documented browser and assistive-technology combinations.
- Manual review of content, focus management, status messages, errors, and complex interactions.
- Criterion-by-criterion findings, evidence, exceptions, and product-version scope.
Related information
Read the accessibility statement for the current target, test coverage, limitations, and barrier-report process. The official VPAT template and terminology are maintained by the Information Technology Industry Council.