What this solves
Manual auditors can spend substantial time transferring repeatable DOM-based axe-core results into a project, while raw scanner output is too noisy and incomplete to serve as a professional audit on its own.
How voiqq helps
The local voiqq browser extension runs axe-core in authorized browser tabs, normalizes supported results, applies the project WCAG version and level, refreshes deterministic duplicates, and leaves every candidate Pending for auditor validation.
Before you begin
- The voiqq Chrome extension installed and connected
- An Accessibility project with the correct WCAG version and level
- Authorization to test every submitted URL
- A stable signed-in browser session for protected pages
Step-by-step
- Open Auto-populate in the Accessibility project
- Download or connect the extension if prompted
- Paste one URL per line or upload a CSV URL list
- Start the scan and keep the browser available
- Review new, refreshed, cleared, and failed-page results
- Validate mapping, severity, evidence, remediation, and status
Check your result
- Candidates are marked Automated and Pending
- Checkpoints do not exceed the project WCAG version or level
- Rescans refresh matching evidence instead of duplicating it
- Manual findings remain unchanged