A multilingual Accessibility Conformance Report must preserve the same WCAG scope and conclusions in every language. voiqq generates English, Dutch, French, German, Spanish, Italian, and Polish VPAT or ACR documents from one reviewed Accessibility project. The report language changes document presentation; it does not create a second set of findings or a second conformance engine.
Project information used by the engine
- Accessibility Library and selected WCAG version
- Target conformance level A, AA, or AAA
- Canonical success-criterion mappings
- Finding summary, description, affected elements, actual result, severity, status, validation, and affected pages
- Product, vendor, auditor, contact, methods, report date, scope, logo, notes, and disclaimer reviewed in Preliminary Review
Generation sequence
- Open the Accessibility project and choose Generate VPAT / ACR.
- Select the WCAG report version offered for the project and choose Target conformance level.
- Choose a value under Report language.
- Complete Preliminary Review, including the required Product Logo.
- Generate Conformance Preview and inspect mappings, warnings, conformance values, remarks, related findings, and manual edits.
- Choose Export DOCX. The server copies the exact matching template and writes a new snapshot and download.
Template selection is exact
Template selection uses language, WCAG 2.0, 2.1, or 2.2, and Level A, AA, or AAA. The renderer locates criterion rows and mapped metadata inside the selected DOCX. It preserves the source layout as closely as the template permits, inserts the uploaded logo, and reports a warning when a field or row cannot be located. It does not silently substitute an English file or a different WCAG version.
Conformance remains deterministic
Not Applicable, Not Evaluated, Supports, Partially Supports, and Does Not Support come from project scope, evaluation state, active finding severity, and resolved or validated status. AI and translation providers do not choose those values. Manual overrides belong only to the export snapshot and do not edit the original findings.
Remarks in the selected language
Remarks combine reviewed findings for each success criterion and use summary, description, affected elements, actual result, pages, severity, and status as controlled context. Drafting removes selectors, class names, raw tracker language, and unsupported claims. If AI is unavailable, the deterministic remarks library writes criterion-aware professional text. A fluent accessibility reviewer remains responsible for the final wording.
Version and level boundaries
A WCAG 2.0 report excludes criteria introduced in 2.1 and 2.2. A WCAG 2.1 report excludes criteria introduced in 2.2. The target level includes only criteria at or below A, AA, or AAA as selected. A newer criterion is excluded, not marked Not Applicable. Not Applicable is reserved for an in-scope criterion that genuinely does not apply to the evaluated product.
Review before distribution
- Confirm that the product logo is clear and has the expected placement.
- Check product name, optional version, vendor, client contact, and auditor contact.
- Confirm selected methods, dates, scope, target level, and disclaimer.
- Compare conformance values with open, resolved, and validated findings.
- Read every translated remark for technical and linguistic accuracy.
- Open the DOCX in Microsoft Word and inspect fonts, centered conformance values, row mapping, links, and page breaks.