Accessibility Auto-populate accelerates repetitive DOM-based checks while preserving the manual audit workflow. It appends normalized candidates to a new or existing Accessibility project and never overwrites manually logged findings.
How the integration works
axe-core runs in the connected browser extension. voiqq applies project WCAG version and level rules, maps supported checkpoints, converts axe impact to voiqq severity, and marks imported candidates Automated with Pending validation.
What you need
- An Accessibility project configured for WCAG 2.0, 2.1, or 2.2 and Level A, AA, or AAA
- The voiqq browser extension installed and connected
- One URL per line or a CSV containing authorized page URLs
- A stable authenticated browser session when the assessed pages require sign-in
A practical workflow
- Open Auto-populate from the Accessibility project
- Choose the destination project and provide up to 50 URLs per batch
- Start the scan while the extension opens, scrolls, and evaluates each page
- Review new, refreshed, cleared, and failed-page results
- Validate checkpoints, severity, evidence, remediation, and lifecycle status
What enters the project
- Summary and rule-based actual result
- WCAG checkpoint mapping constrained to the project version and level
- Affected element context without exposing technical selectors in report prose
- Remediation guidance, reference URL, source metadata, and scan timestamp
- Rescan state used to refresh evidence and close cleared automated findings