agent reported zero violations: javascript disabled in its browser

agent reported zero violations: javascript disabled in its browser - how to fix it

TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent reported zero violations because JavaScript was disabled in its browser, so it scanned an empty shell. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

The error, verbatim

agent reported zero violations: javascript disabled in its browser

Fix it step by step

Step 1

Enable JavaScript in the agent's browser profile; most violations only exist post-hydration.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 2

Add a smoke check: if the scanned DOM has no scripts-rendered content, fail the run instead of reporting zero.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 3

Re-run the scan with JS enabled and compare; the gap is the real violation set.

Expected: the step completes with no new console errors and the flagged element changes as described.

Step 4

Pin the browser profile in the agent config so it cannot drift.

Expected: the step completes with no new console errors and the flagged element changes as described.

When to use this skill

• Your scan report lists this exact rule or failure
• You are clearing automated accessibility failures before release or audit
• A CI accessibility gate is red because of this item

When NOT to use this skill

• Zero violations on a JS app is a scan failure, not a clean bill.
• The issue only appears in manual screen-reader testing and no automated rule flags it
• You are doing a full manual WCAG audit; this skill covers one automated check

Compatibility

Agent workflow guardrail; DOM-content smoke check before scan.

Variant phrasings

agent reported zero violations javascript disabled

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

Why it happens

The agent reported zero violations because JavaScript was disabled in its browser, so it scanned an empty shell. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst9vcBvtB-ECRDIQ6S1W5hA