Help Center
Practical answers for working confidently in voiqq.
Product support
Help Center resources
Find task-focused guidance for projects, findings, teams, reports, imports, and account management.
- Create a Custom LibraryDefine your own testing standard in the Custom Program, add reusable default findings, and select the saved Custom Library for future projects.
- Custom Libraries DefaultsCreate, edit, and safely use reusable Custom Libraries findings in your local Default Findings Engine.
- MobSF Auto-populateNormalize authorized MobSF results into a Mobile Application Security project.
- OWASP AISVS DefaultsCreate, edit, and safely use reusable OWASP AISVS findings in your local Default Findings Engine.
- OWASP ASVS DefaultsCreate, edit, and safely use reusable OWASP ASVS findings in your local Default Findings Engine.
- OWASP MASVS DefaultsCreate, edit, and safely use reusable OWASP MASVS findings in your local Default Findings Engine.
- SOC 2 Availability DefaultsCreate, edit, and safely use reusable SOC 2 Availability findings in your local Default Findings Engine.
- SOC 2 Confidentiality DefaultsCreate, edit, and safely use reusable SOC 2 Confidentiality findings in your local Default Findings Engine.
- SOC 2 Privacy DefaultsCreate, edit, and safely use reusable SOC 2 Privacy findings in your local Default Findings Engine.
- SOC 2 Processing Integrity DefaultsCreate, edit, and safely use reusable SOC 2 Processing Integrity findings in your local Default Findings Engine.
- SOC 2 Security DefaultsCreate, edit, and safely use reusable SOC 2 Security findings in your local Default Findings Engine.
- WCAG 2.0 DefaultsCreate, edit, and safely use reusable WCAG 2.0 findings in your local Default Findings Engine.
- WCAG 2.1 DefaultsCreate, edit, and safely use reusable WCAG 2.1 findings in your local Default Findings Engine.
- WCAG 2.2 DefaultsCreate, edit, and safely use reusable WCAG 2.2 findings in your local Default Findings Engine.
- Getting StartedCreate an account, enter your workspace, and understand the first project workflow.
- Create ProjectsChoose a team, program, library, scope, and project metrics.
- Log FindingsCreate, edit, assign, comment on, validate, duplicate, and delete findings.
- Teams and PermissionsInvite colleagues, choose the right workspace role, remove access, and keep public project links separate from team membership.
- Import SpreadsheetsTurn XLSX, CSV, or public Google Sheets into normal voiqq projects.
- Change Interface LanguageChange navigation, controls, errors, guidance, Help, and Docs without translating or altering project evidence.
- Multilingual Spreadsheet ImportsImport structured findings in any of voiqq's 39 supported languages while preserving source evidence and canonical report mappings.
- Generate a Multilingual ReportChoose from 39 professional report languages, review the localized draft, and export without changing the source project.
- Review Column MatchingConfirm deterministic and AI-assisted mappings before spreadsheet rows become findings, controls, evidence requests, or additional data.
- Accessibility Auto-populateInstall the extension, scan authorized pages, and validate normalized WCAG candidates.
- ZAP Auto-populateNormalize authorized OWASP ZAP results into a Web Application Security project.
- garak Auto-populateNormalize authorized garak probe results into an AI Application Security project.
- Edit TablesChoose which fields appear, rename labels, add project fields, and keep each project easy to review.
- Field VisibilityUse Compact, Full, and Details Panel choices without losing important project information.
- Organize Finding DrawerKeep the most useful finding details first and move less frequent information out of the way.
- Save Table TemplatesReuse a trusted project layout without copying findings, names, scope, or standards settings.
- Rearrange Project WorkspacePut columns, findings, drawer fields, and drawer panels in the order your team uses.
- Evidence and CommentsAdd authorized images, videos, external links, attachments, and collaboration comments.
- Share ProjectsConfigure private or anyone-with-link access for one project.
- Professional PortfolioPublish a professional portfolio using only projects whose normal Anyone with link access is enabled.
- Reports and ExportsGenerate spreadsheets and program-specific professional report snapshots.
- Plans and BillingStart a payment-backed trial, manage a Paddle subscription, cancel, or request a refund.
- Privacy and AccountManage legal acknowledgements, cookie choices, communications, exports, privacy cases, and permanent account deletion.
- Headings in a Clear OrderHeadings divide content into sections.
- Links With a Clear PurposeLink words should explain where the link goes or what it opens.
- Instructions Everyone Can FollowInstructions should name the thing a person needs to choose.
- Text in Another LanguageReading software uses a page or document's language setting to pronounce words.
- Descriptions for Meaningful ImagesAn image that provides information needs a text alternative, often called alt text.
- Images Used Only for DecorationA decorative image adds no information or action.
- Accurate Captions and TranscriptsCaptions show a video's speech and important sounds as text at the right time.
- Visual Information in VideosImportant information shown in a video should be understandable without seeing the screen.
- Control Over Moving ContentMoving content can distract people or change before they finish reading.
- Text That Stands Out From Its BackgroundContrast is the difference between text and its background.
- Clear Buttons, Icons, and ChartsThe visual parts needed to identify controls or understand graphics generally need at least 3:1 contrast against adjacent colors.
- Content That Fits Small Screens and ZoomText and controls should remain usable when the screen is narrow or the page is enlarged.
- Links and Buttons That Work Without a MousePeople must be able to reach and use controls with a keyboard.
- Buttons and Image Links With Useful NamesA control needs a name explaining its action, available to reading software.
- Form Fields With Clear BordersPeople need to see where to enter an answer or select an option.
- A Clear Label for Every Form FieldA label explains what belongs in a field.
- Labels That Stay Visible While TypingPlaceholder text is the hint inside an empty field.
- Required Fields Are Clearly MarkedPeople should know which answers are required before submitting.
- Explain the Required-Field AsteriskAn asterisk (*) can mark required fields, but explain its meaning before the form begins.
- Fields That Support AutofillCommon personal details should have the correct purpose identified for the browser.
- Errors That Explain What to CorrectAn error message should identify the problem and help the person correct it.
- Errors That Are Easy to FindAfter submission fails, people should be directed to what needs correcting.
- Clear Submission and Status MessagesStatus messages tell people whether an action worked, failed, or is still running.
- Tables With Clear Row and Column HeadingsTable headings explain the values beneath or beside them.
- Real Bullet and Numbered ListsA list should be identified as a list in the page or document, so reading software recognizes its items.
- Tables That Remain Readable on a PhoneA narrow screen should not hide table information.
- Useful Names for Downloads and EmbedsNames should explain what a document or embedded item contains.
- Downloads People Can Read and UseDownloads need accessible content too.
- What a Maintenance Sign-off MeansA maintenance review covers newly added or changed content after the original audit.