Accessibility: in preparation
Accessibility Conformance Report (draft)
A working draft of how the DocoMatic Workbench measures up against WCAG 2.2, Section 508 and EN 301 549, in the VPAT 2.5 format procurement teams expect. Each rating says what we tested and how, and anything short of full support is listed as a known issue.
Draft date: .Draft 0.1
Supersedes: none. The next revision follows testing with assistive technology.
This report is in preparation
This is not a published Accessibility Conformance Report. It is a working draft of our own evaluation of a pre-release version of the Workbench. It does not yet include testing with assistive technology or an independent review, and its ratings may change once that testing is done. When the final report is ready, we will offer it on our security page and it will replace this draft.
This report covers the DocoMatic Workbench only. Issues with the DocoMatic website are listed in our accessibility statement; the two lists are kept separate on purpose.
Since the draft date, the Workbench has gained an in-product Help page. Ratings 3.2.6 (Consistent Help) and 602.2 (Accessibility and Compatibility Features) therefore describe the earlier build and are due for re-evaluation; each of those rows carries the same note.
Product information
- Product
- DocoMatic Workbench, the web application customers use to upload, analyze, remediate and download documents
- Version
- Pre-release build (0.1), as deployed on the draft date
- Draft date
- September 16, 2026
- Description
- A browser-based application for public-sector organizations that checks documents for accessibility, remediates them to PDF/UA and WCAG, and produces verification reports. Available in English, Canadian French and US Spanish.
- Contact
- accessibility@docomatic.ai
- Scope
- The Workbench sign-in, sign-up, documents, document detail, upload, monitoring, integrations, entities and settings screens, in all three languages. Not covered: our internal staff console, our marketing website (see the accessibility statement), and our developer documentation site.
Summary
This draft rates 56 WCAG success criteria at Levels A and AA: those of WCAG 2.2, plus 4.1.1, which only earlier versions include. The Workbench supports 45 of them with no known defects and partially supports 3. The other 8 do not apply, mostly because the application contains no audio or video.
Our biggest gap is evidence, not code. We have not yet tested the Workbench with screen readers or speech-input software. Our ratings rest on automated testing, keyboard-only testing, measurement and code review. We state that plainly throughout this draft rather than implying a manual audit we have not done.
The marketing website has its own accessibility statement.
Every criterion row has a stable anchor, for example 1.4.3 Contrast (Minimum), so a procurement response can cite a link to one rating rather than attach this page.
Evaluation methods
So far we have evaluated the build deployed on the draft date using these methods:
- Automated testing with axe-core 4.10 on 22 Workbench screens, with every menu, list box and dialog opened, in English, French and Spanish. This includes axe's WCAG 2.2 target-size check, which is off by default. Result: no violations at any severity.
- An automated keyboard-only test of the core workflow (upload, open the document, choose a service level, remediate, download). It checks that every focus stop has a visible indicator, that focus follows document order, and that focus is never lost.
- Measurements axe does not make: contrast of form-control borders and focus indicators (at least 3:1), reflow at 320 CSS pixels, WCAG text-spacing overrides, and whether each control's accessible name contains its visible label.
- Code review of the user-interface components, which are built on Radix primitives. Automated tests also check that job progress and results are announced through live regions.
Not yet done: testing with screen readers (JAWS, NVDA, VoiceOver, TalkBack), screen magnifiers or speech-input software, and testing by people with disabilities. We plan to commission this before general availability. The final report will include the results.
Standards and guidelines
- Web Content Accessibility Guidelines (WCAG) 2.2, Levels A and AA. Level AAA is not assessed.
- Revised Section 508 standards, as published by the US Access Board (36 CFR Part 1194).
- EN 301 549 V3.2.1 (2021-03), Accessibility requirements for ICT products and services.
Terms
- Supports
- The functionality of the product meets the criterion without known defects, or meets it with equivalent facilitation.
- Partially supports
- Some functionality of the product does not meet the criterion.
- Does not support
- The majority of product functionality does not meet the criterion.
- Not applicable
- The criterion is not relevant to the product.
WCAG 2.2 Level A
Also applies to Section 508 (501.1 for software, 602.3 for support documentation) and EN 301 549 clauses 9, 10 and 11.
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Icons are decorative and hidden from assistive technology. Icon-only buttons have text names, and the brand mark is marked decorative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not applicable | The Workbench contains no audio or video. |
| 1.2.2 Captions (Prerecorded) | Not applicable | The Workbench contains no audio or video. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not applicable | The Workbench contains no audio or video. |
| 1.3.1 Info and Relationships | Supports | Headings, the navigation and main landmarks, lists, form labels and data tables with header cells are coded semantically. axe reports no issues, including its best-practice rules for heading order and landmarks. |
| 1.3.2 Meaningful Sequence | Supports | Reading order follows the visual order. Dialogs and menus are placed in the reading order when opened. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely on shape, size, position or sound. |
| 1.4.1 Use of Color | Supports | Document status, check results and errors are shown as text, with icons where helpful. Color is never the only cue. |
| 1.4.2 Audio Control | Not applicable | The Workbench plays no audio. |
| 2.1.1 Keyboard | Supports | All functionality works from the keyboard, confirmed by an automated keyboard-only test of the core workflow. The drag-and-drop upload area also has a keyboard-operable Browse button. |
| 2.1.2 No Keyboard Trap | Supports | Focus can always move away. Menus and dialogs close with Escape and return focus to the control that opened them. |
| 2.1.4 Character Key Shortcuts | Supports | The only shortcut (show or hide the sidebar) needs Ctrl or Command. |
| 2.2.1 Timing Adjustable | Supports | No task has a time limit. |
| 2.2.2 Pause, Stop, Hide | Partially supports | Nothing moves or blinks for more than five seconds. Document and alert statuses update automatically while jobs run, and there is no control to pause those updates. Updates stop when the jobs finish. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes. |
| 2.4.1 Bypass Blocks | Supports | A skip link moves focus to the main content, and navigation and main landmarks are provided. |
| 2.4.2 Page Titled | Supports | Each page title names the screen (taken from its main heading, including the document or domain name on detail screens) and the organization. |
| 2.4.3 Focus Order | Supports | Focus follows the visual order (tested automatically). It moves into dialogs and back when they close, and moves to the main content when you change screens. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text, or link text together with its table row, describes the destination. |
| 2.5.1 Pointer Gestures | Supports | No multipoint or path-based gestures are used. |
| 2.5.2 Pointer Cancellation | Supports | Controls act on release of the pointer, using standard buttons and links. |
| 2.5.3 Label in Name | Supports | Every control's accessible name contains its visible text. We checked this automatically across the Workbench screens. |
| 2.5.4 Motion Actuation | Not applicable | No functionality uses device motion. |
| 3.1.1 Language of Page | Supports | The page language is set to en-US, fr-CA or es-US to match the chosen language. |
| 3.2.1 On Focus | Supports | Moving focus never changes context. |
| 3.2.2 On Input | Supports | Changing a filter updates the list in place. Nothing opens or navigates without a deliberate action. |
| 3.2.6 Consistent Help | Not applicable | On the draft date, the Workbench included no help mechanism, so this criterion did not apply. Contact details are on our website.Due for re-evaluation: this rating describes the build before the in-product Help page was added. |
| 3.3.1 Error Identification | Supports | Errors are described in text next to the field or control that caused them. Fields are marked invalid and linked to their message, and failures are also announced. |
| 3.3.2 Labels or Instructions | Partially supports | Form fields have visible labels. The filter drop-downs above lists have accessible names but no visible label; their purpose is shown by the current value (for example, "All statuses"). |
| 3.3.7 Redundant Entry | Supports | Sign-up carries the organization and email you already entered into the account step, and does not ask for them again. |
| 4.1.1 Parsing (WCAG 2.0 and 2.1 only) | Supports | Removed in WCAG 2.2 and treated as always satisfied for HTML. We list it for Section 508 and EN 301 549, which reference earlier WCAG versions. |
| 4.1.2 Name, Role, Value | Supports | Controls are built on Radix primitives with correct roles, names and states. When a menu, list box or dialog is open, the page behind it is both hidden from assistive technology and made inert. |
WCAG 2.2 Level AA
Section 508 incorporates WCAG 2.0; the criteria added in WCAG 2.1 and 2.2 are rated here as well.
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not applicable | The Workbench contains no live audio. |
| 1.2.5 Audio Description (Prerecorded) | Not applicable | The Workbench contains no video. |
| 1.3.4 Orientation | Supports | Works in portrait and landscape orientation. |
| 1.3.5 Identify Input Purpose | Supports | Personal fields (name, email, organization, phone, passwords) declare their purpose, so browsers can autofill them. |
| 1.4.3 Contrast (Minimum) | Supports | Text meets 4.5:1 (3:1 for large text), confirmed by axe on every screen tested. The Workbench has a light theme only. |
| 1.4.4 Resize Text | Supports | Text can be zoomed to 200% without loss of content; the layout reflows (see 1.4.10). |
| 1.4.5 Images of Text | Supports | No images of text are used. |
| 1.4.10 Reflow | Supports | At 320 CSS pixels wide, no screen we tested scrolls in two directions. Data tables scroll sideways inside their own container, as the criterion allows. |
| 1.4.11 Non-text Contrast | Supports | Form-control borders measure 3.4:1 and focus indicators 3.5:1 against the page. A regression test guards both. |
| 1.4.12 Text Spacing | Supports | With WCAG's text-spacing overrides applied, no text is cut off. Long organization names are shortened with an ellipsis whatever the spacing, and appear in full in the organization menu. |
| 1.4.13 Content on Hover or Focus | Supports | Tooltips can be dismissed with Escape, can be hovered, and stay visible until dismissed or no longer needed. |
| 2.4.5 Multiple Ways | Supports | Screens can be reached from the sidebar navigation, from links in lists and dashboards, and documents can also be found with search. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible | Supports | Every focusable element shows a focus indicator. The keyboard test checks this at each stop. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | No sticky or fixed content covers the focused element. |
| 2.5.7 Dragging Movements | Supports | The only drag interaction, dropping files to upload, also has a Browse button. |
| 2.5.8 Target Size (Minimum) | Supports | Targets are at least 24 by 24 CSS pixels or adequately spaced, confirmed by axe's target-size rule. |
| 3.1.2 Language of Parts | Supports | Each page is entirely in one language. In the language menu, each option is marked with its own language. |
| 3.2.3 Consistent Navigation | Supports | The sidebar navigation is the same on every screen. |
| 3.2.4 Consistent Identification | Supports | Components with the same function are labelled the same way throughout. |
| 3.3.3 Error Suggestion | Supports | Error messages say how to fix the problem, such as the password rules, or choosing a lower service level when credits are short. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Partially supports | Deleting documents and team members, bulk actions and ownership transfers ask for confirmation. Starting a single remediation spends credits as soon as the button is pressed; the cost is shown next to the button, but there is no separate confirmation step. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | Sign-in uses email and password, supports password managers and pasting, and involves no puzzle or memory test. |
| 4.1.3 Status Messages | Supports | Upload results, analysis and remediation milestones, review outcomes, saves and bulk-action totals are announced through live regions without moving focus. Failures are announced assertively. |
Section 508, Chapter 3: Functional performance criteria
Equivalent to EN 301 549 clause 4.2.
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 302.1 Without Vision | Partially supports | Built for screen readers (semantic structure, accessible names, announced status changes), but not yet tested with a screen reader. |
| 302.2 With Limited Vision | Supports | Supports browser zoom, reflow at 320 CSS pixels, text spacing and minimum contrast. Not yet tested with screen magnifiers. |
| 302.3 Without Perception of Color | Supports | Information is never conveyed by color alone. |
| 302.4 Without Hearing | Supports | No functionality uses audio. |
| 302.5 With Limited Hearing | Supports | No functionality uses audio. |
| 302.6 Without Speech | Supports | No functionality needs speech. |
| 302.7 With Limited Manipulation | Supports | Everything works from the keyboard, targets meet minimum size, and no dragging is required. Not yet tested with speech-input software. |
| 302.8 With Limited Reach and Strength | Supports | No physical interaction beyond standard keyboard or pointer input is needed. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially supports | Plain-language messages, consistent layout, errors with suggested fixes, and no time limits. Starting a single remediation has no confirmation step (see 3.3.4). |
Section 508, Chapter 5: Software
The Workbench is web software and an authoring tool: it creates accessible PDF documents. Equivalent to EN 301 549 clause 11.
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 501.1 Scope: Incorporation of WCAG 2.0 AA | Supports | See the WCAG 2.2 tables above. |
| 502 Interoperability with Assistive Technology | Not applicable | Web software: accessibility is provided through the browser's accessibility APIs, as covered by WCAG. This criterion applies to platform software. |
| 503.2 User Preferences | Supports | Respects the browser's text size, zoom, language and reduced-motion settings. Loading animations stop when reduced motion is requested. |
| 503.3 Alternative User Interfaces | Not applicable | The Workbench provides no alternative user interface that works as assistive technology. |
| 503.4 User Controls for Captions and Audio Description | Not applicable | The Workbench contains no video. |
| 504.2 Content Creation or Editing | Supports | The Workbench's purpose is producing accessible documents. It checks uploads against PDF/UA and WCAG rules, remediates them, and reports what changed. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Partially supports | Level 1 remediation only adds tags and properties; we verified that it leaves pages visually identical. Level 2 and 3 rebuild document structure and may substitute fonts. Font substitutions are recorded in the change manifest but, as of this draft, not listed in the customer-facing report. |
| 504.2.2 PDF Export | Partially supports | Remediated PDFs are validated against PDF/UA-1 with veraPDF. Documents that fail are reported as not verified. The verification report PDF is checked the same way when a veraPDF validator is configured for the deployment; otherwise only DocoMatic's own analyzer checks it. |
| 504.3 Prompts | Supports | The analysis report lists each failed check and recommends a remediation level. Human review can be added for content that automation cannot settle. |
| 504.4 Templates | Not applicable | The Workbench does not offer document templates. |
Section 508, Chapter 6: Support documentation and services
Equivalent to EN 301 549 clause 12.
| Criterion | Conformance level | Remarks and explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features | Partially supports | This draft and our accessibility statement describe the Workbench's accessibility features. In-product help did not cover them on the draft date.Due for re-evaluation: this rating describes the build before the in-product Help page was added. |
| 602.3 Electronic Support Documentation | Partially supports | This draft and the accessibility statement are published as accessible web pages. Our developer documentation site has not yet been evaluated against WCAG 2.2 AA. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not applicable | We provide no non-electronic documentation. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Support answers accessibility questions at accessibility@docomatic.ai. |
| 603.3 Accommodation of Communication Needs | Supports | Support works in writing by email, in English, French or Spanish. |
EN 301 549 mapping
- Clause 4.2 (functional performance statements): see the Section 508 Chapter 3 table.
- Clauses 5 to 8 (generic requirements, two-way voice, video and hardware): not applicable, except 5.2 (activation of accessibility features) and 5.7 (key repeat), which the browser handles.
- Clauses 9 (web), 10 (non-web documents) and 11 (software): see the WCAG 2.2 tables. The Workbench is a web application.
- Clause 11.8 (authoring tools): see rows 504.2 to 504.4 of the Section 508 Chapter 5 table.
- Clause 12 (documentation and support services): see the Section 508 Chapter 6 table.
EN 301 549 is the standard behind the European Accessibility Act; our European Accessibility Act guide explains what it requires. How buyers read a report in this format is covered in our Section 508 guide.
Known issues
Everything below falls short of full support, or is not yet evidenced. We will update this list as each item is resolved.
Not yet tested with assistive technology
We have not tested with screen readers, magnifiers or speech input. Our ratings rest on automated, keyboard and measured testing plus code review, so problems that only real assistive technology reveals may remain. This affects 302.1, 302.2 and 302.7.
Live status updates cannot be paused
While your jobs are running, document and alert statuses refresh automatically, and there is no pause control (2.2.2). The updates stop once the jobs finish.
List filters have no visible label
The filter drop-downs have accessible names, but on screen their purpose is shown only by the selected value (3.3.2).
No confirmation before a single remediation spends credits
The cost appears next to the Remediate button, but pressing it spends credits straight away. Bulk remediation does ask for confirmation (3.3.4, 302.9).
Font substitutions not disclosed in the customer report
Level 2 and 3 remediation may substitute fonts. The change is recorded in the change manifest but not yet in the customer-facing report (504.2.1).
Report PDF validation depends on deployment
The verification report PDF is checked with veraPDF only when a veraPDF validator is configured (504.2.2).
Accessibility features not covered in product help
On the draft date the Workbench had no in-product help. Its accessibility features are described in this draft and in our accessibility statement (602.2).
Developer documentation not evaluated
Our developer documentation site is outside this draft's scope and has not been evaluated (602.3).
Staff console outside scope
DocoMatic's internal staff console is not a customer product and is not covered here. It is tested with the same automated checks and is available in English only.
Fixed before this draft
An internal audit on September 15, 2026 found these defects. All were fixed and retested before this draft:
- Open menus and list boxes hid the page from screen readers but left it focusable. The page behind any menu, list box or dialog is now also inert (4.1.2).
- Job progress and completion were not announced. Milestones, saves and failures are now announced (4.1.3).
- Failure messages offered no way to try again. Every failure state now has a retry, loading states have placeholders, and unknown addresses show a proper not-found page.
- Secondary text, form-control borders and focus indicators had too little contrast (1.4.3, 1.4.11).
- Three menu buttons and the connector buttons had accessible names that did not contain their visible text (2.5.3).
- Every screen had the same page title (2.4.2).
- Two targets were smaller than 24 CSS pixels and too close to their neighbors (2.5.8).
- Focus was lost when a remediation was submitted and did not move on screen changes, and the skip link's target could not take focus (2.4.3).
- The Integrations and Entities screens showed raw text keys instead of words in all three languages.
Feedback
If something in the Workbench does not work for you, or you need this draft in another format, email accessibility@docomatic.ai. We reply within two business days.
Two business days is the acknowledgement commitment published in Service Levels and Support, section 6.7.
We update this draft as testing progresses and whenever a rating changes. The draft date at the top shows when it last changed.