Troubleshooting
Common Scan Issues & Resolutions
Most failed scans happen because a firewall/WAF blocks headless cloud IPs or an app requires authentication cookies before rendering protected views.
How to
Resolving blocked scans
1
If your staging site is protected by Cloudflare Bot Fight Mode or IP allowlists, scan a Vercel/Netlify preview URL or temporarily allow the request User-Agent.
2
Verify the target URL returns HTTP 200 without infinite client-side redirect loops.
3
Confirm routes are reachable within the default navigation timeout before launching a 25-route crawl.
Why a criterion displays 'Not Evaluated'
That WCAG requirement has no reliable automated DOM assertion in Axe-core (e.g., logical reading order nuance or video caption quality) and requires manual team QA.