voiqq supports professional report output in all 39 supported languages. The language belongs to the report configuration, not to the workspace interface and not to the imported spreadsheet detector. A reviewer can work in one interface language, preserve evidence in another language, and prepare the approved report for a third audience.
Three language settings with separate jobs
- Interface language changes voiqq navigation and system controls across supported browsers.
- Spreadsheet language detection helps normalize supported imported headers into canonical fields while preserving the original grid.
- Report language changes the generated DOCX or PDF presentation and reviewed narrative for the selected professional deliverable.
Canonical decisions do not move with the language
Program, Library, standard version, target level, requirement IDs, project scope, finding status, validation, severity, assignment, evidence, deterministic conformance, coverage, and export usage remain canonical. The report engine localizes labels, known workflow terms, dates, approved criterion titles, deterministic fallback prose, and generated narrative. It does not use translation to decide whether a requirement passed.
Supported professional reports
- Accessibility: VPAT or Accessibility Conformance Report DOCX for WCAG 2.0, 2.1, or 2.2 at Level A, AA, or AAA when the plan supports that export.
- SOC 2: readiness PDF based on selected Trust Services Criteria, scope, evidence status, gaps, owners, and remediation.
- Web Application Security: OWASP ASVS assessment PDF with canonical requirements, mapped findings, and reviewed coverage.
- Mobile Application Security: OWASP MASVS assessment PDF with canonical controls, platform context, findings, and reviewed coverage.
- AI Application Security: OWASP AISVS assessment PDF with canonical requirements, AI-system scope, findings, and reviewed coverage.
- Custom Program: assessment PDF named for the selected Custom Library and built from its defined standards, findings, evidence, and reviewed coverage.
Language-specific VPAT templates
English, German, Spanish, French, Italian, Dutch, and Polish use bundled language-specific VPAT templates for each supported WCAG version and level. For the other 32 supported languages, voiqq uses the verified English VPAT template as the structural base and localizes its headings, criteria, conformance labels, product text, evaluation methods, and remarks during generation. Both paths preserve canonical WCAG identifiers and the selected version and level; neither creates a second assessment.
Localized readiness and security PDFs
The SOC 2, ASVS, MASVS, and AISVS report engines share a professional PDF foundation while retaining Program-specific scope, standards, coverage, and terminology. The selected language controls report furniture and generated narrative. Source evidence remains attributable to the project record.
Drafting, fallback, and review
The configured AI cascade may draft report prose from approved project facts. It cannot choose applicability, conformance, coverage, finding validity, certification, or a legal conclusion. When drafting providers fail, deterministic text keeps export available. The reviewer can edit allowed report fields before creating the immutable snapshot.
Plan access
English follows each plan's normal professional export allowance. Selection of any of the other 38 report languages is available on Pro, Team, Business, and Enterprise. Translated XLSX findings exports are available on Team and above. A downgrade leaves projects and saved files available while pausing newly ineligible exports.
Release checklist
- The recipient language is deliberate and has a fluent reviewer.
- Product, organization, auditor, and contact names remain accurate.
- Standard versions, levels, criteria, controls, and requirement identifiers are unchanged.
- Source quotations and evidence have not been silently altered.
- Conformance or coverage matches reviewed project status and validation.
- DOCX or PDF layout, links, logo, tables, and page breaks have been inspected in a suitable reader.
- The report makes no unsupported certification, compliance, attestation, or legal claim.
