DocAccessible
Procurement

Accessibility conformance report status

Current DocAccessible accessibility evaluation status, tested areas, known limits, and the process for procurement accessibility reviews.

Updated July 14, 2026. Reviewed by the DocAccessible team under our editorial policy.

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, the accurate status for the product as a whole is not yet evaluated. Automated results are useful evidence, but they are not a substitute for a formal accessibility evaluation.

Evaluation coverage as of July 14, 2026
AreaCurrent evidenceStatus
Public marketing and guide pagesAutomated browser checks, keyboard checks, and responsive layout testsTesting in progress
Authentication and core workspace flowsBrowser workflow, labels, errors, focus, and keyboard regression checksTesting in progress
Hosted accessible HTMLSemantic output checks and representative browser reviewRequires document-level review
Complete WCAG 2.2 A and AA criteriaCriterion-by-criterion manual evaluation has not been completedNot yet evaluated
Revised Section 508 and EN 301 549A formal standards mapping has not been completedNot 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.