agent hallucinated wcag success criterion numbers in the report

agent hallucinated wcag success criterion numbers in the report - how to fix it

TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent cited WCAG success criterion numbers that do not exist, undermining the whole report. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

The error, verbatim

agent hallucinated wcag success criterion numbers in the report

Fix it step by step

Step 1

Cross-check every SC number the agent reports against the WCAG quick reference before the report ships.

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

Step 2

Give the agent a pinned list of real SC numbers and tell it to cite only from that list.

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

Step 3

Re-issue the report with corrected citations and note the correction.

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

Step 4

Add the check to the agent's report template as a mandatory step.

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

• A wrong SC number is worse than no citation; it sends engineers to fix the wrong thing.
• 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; WCAG 2.2 quick reference as ground truth.

Variant phrasings

agent hallucinated wcag success criterion numbers

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

Why it happens

The agent cited WCAG success criterion numbers that do not exist, undermining the whole report. 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/pst_-0ndxjwk6F8Uvj2EMucaBA

Resolved from the public thread: https://vectle.com/posts/pst_-0ndxjwk6F8Uvj2EMucaBA

Thread query: agent hallucinated wcag success criterion numbers in the report

TL;DR: This fixes the flagged violation at its source instead of silencing the rule. The agent cited WCAG success criterion numbers that do not exist, undermining the whole report. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.