Language affects two different parts of professional assessment work. The person using voiqq needs controls, instructions, errors, and navigation in a familiar language. The assessment itself may arrive in another language and must retain its original evidence. voiqq keeps those concerns separate. Your account language changes the application interface. A spreadsheet language describes an imported sheet so the mapper can understand its headings and workflow values. Changing one does not rewrite the other.
Two language settings with different jobs
- Interface language follows the signed-in user and is available on every plan. It translates voiqq navigation, controls, labels, guidance, status messages, Help, Docs, and other application copy.
- Spreadsheet language belongs to an imported sheet and then to the project created from it. It guides field matching, standard field labels, known workflow values, locale-aware dates, and supported exports.
- Original cell values, quoted evidence, URLs, code, selectors, product names, identifiers, comments, and finding descriptions remain as the reviewer entered or imported them.
- Canonical standard references such as WCAG 2.2, CC6.1, V7.3.1, MASVS-STORAGE-1, and AISVS identifiers are never translated into a different identifier.
How interface translation works
Choose Language in Account settings from all 39 interface language targets. A Platform Owner can use the same preference in the admin area. voiqq saves the choice to the signed-in profile and to that browser. Known interface labels change immediately. Missing system text is requested from voiqq in small same-origin batches, stored in a protected shared cache, and reused by Chrome, Edge, Firefox, Safari, and other current browsers. No experimental browser translation API or local language-pack download is required.
The document language and direction update with the preference so assistive technologies can use more appropriate pronunciation and reading order. Visible labels and equivalent accessible names follow the same translation. Keyboard order, focus behavior, validation, and permissions do not change. Project tables, imported grid rows, finding evidence, comments, code, URLs, and user-entered values are excluded from automatic interface translation.
How spreadsheet language works
Spreadsheet import currently recognizes English, Dutch, French, German, Spanish, Italian, and Polish. The importer evaluates the header row and a bounded sample of representative cells. It looks for professional terms, known workflow values, requirement shapes, dates, URLs, and Program-specific evidence. Each valid sheet receives its own detected language and confidence. This matters when one workbook contains, for example, a Dutch Accessibility sheet and an English SOC 2 sheet. The reviewer can correct the detected language on a paid workspace before importing.
Plan access and downgrade behavior
English spreadsheet import remains available on Free. Importing or manually selecting Dutch, French, German, Spanish, Italian, or Polish starts on Pro. The rule is checked in the import modal, the AI ambiguity-review route, and the final server import transaction. Existing multilingual projects remain accessible after a downgrade. A downgrade does not translate, delete, or hide their records; it pauses new non-English spreadsheet imports until the workspace upgrades again. The interface language remains available because it is not a paid entitlement.
Exports and professional review
Supported spreadsheet and PDF report furniture can use the project language: headings, standard field labels, known status values, severity, validation, and locale-aware dates. Source evidence remains unchanged. Official templates keep their required standard-owned structure. A reviewer should inspect every export before distribution, especially translated labels beside untranslated narrative evidence. Automatic language support helps organize work; it does not replace a fluent reviewer when wording affects a legal, contractual, or compliance conclusion.
Recommended quality check
- Set your personal interface language in Account settings and confirm navigation, dialogs, errors, and Help pages remain understandable.
- Import a copy of the source workbook and review the detected language for every included sheet.
- Confirm the Program, Library, version, target level, and other project requirements independently of the language.
- Open Review column matching and inspect Summary, requirement or control, status, validation, severity, owner or assignee, due date, affected target, evidence, and remediation.
- Create the project, compare first, middle, and last rows with the preserved source grid, and correct any uncertain mapping.
- Generate a draft export and verify standard labels, dates, canonical references, and unchanged source evidence before sharing it.