Validation errors are exposed programmatically
AGENTIC_ERRORS_ANNOUNCED
When a submission fails, an agent needs to read why. An error styled red with no role and no aria-live is invisible - the agent sees a form that silently did nothing.
- Free, no signupNo account, no card
- No AI in the score986 deterministic rules
- Nothing publishedYour scans stay yours
- Answers in secondsQuick scan, no browser
How this rule is weighted
- Importance
- 5 / 10
- How much this matters relative to other rules.
- Confidence
- EMERGING
- Plausible and actively discussed, not yet well evidenced.
- Severity
- info
- How the finding is presented when it fails.
- Scoring
- Excluded
- Reported in the report, never penalised.
Impact is importance multiplied by the confidence tier’s weight — SPECIFICATION 1.0, RESEARCH 0.7, EMERGING 0.3, EXPERIMENTAL 0.1. Two rules backed by the same class of evidence therefore always carry the same weight, which is what makes the score reproducible rather than hand-tuned.
Questions about this rule
- Does AGENTIC_ERRORS_ANNOUNCED affect my score?
- No. It is a detection rule: it runs, appears in your report and never penalises you. "Validation errors are exposed programmatically" is information about the page rather than a defect - most pages are not expected to satisfy it.
- What does EMERGING confidence mean?
- Plausible and actively discussed, not yet well evidenced. Confidence is a declared tier rather than a per-rule number, so every rule backed by the same class of evidence carries the same weight - which is what makes the score reproducible instead of hand-tuned.
- How do I check AGENTIC_ERRORS_ANNOUNCED on my own site?
- Paste your URL into the box above and it runs only this rule, usually in a couple of seconds. It is also included in the AI Agent Readiness checker and in a full scan.
Tags
- agentic
- transact
- detection
Related AI Agent Readiness rules
- Every control has an accessible nameAn agent selects a control by its name - 'click Add to cart'. A control with no name can only be described positionally, which breaks the moment your layout changes.AGENTIC_BUTTONS_HAVE_NAMES
- Form fields are labelledAn agent filling a form matches your labels to what it was asked to enter. An unlabelled field is one it must guess at - and a wrong guess in a checkout is worse than a refusal.AGENTIC_INPUTS_LABELLED
- Interactive controls are real buttonsAgents locate controls through the accessibility tree, where a <div class="btn"> is not a control at all. This is the single most common reason an agent gets stuck on an otherwise ordinary page.AGENTIC_REAL_BUTTONS
- Navigation uses real linksAn agent follows href attributes. A div with a click handler is invisible to it - and unreachable without executing your JavaScript and guessing what the handler does.AGENTIC_REAL_LINKS
- A main content region is declaredAn agent orienting on an unfamiliar page looks for the main landmark first. Without one it has to guess which of forty divs holds the content, and it frequently guesses the navigation.AGENTIC_MAIN_CONTENT_MARKED
- Click handlers are not attached to generic elementsA div with onclick has no role, no accessible name and no keyboard behaviour. An agent cannot find it, and a keyboard user cannot reach it.AGENTIC_NO_DIV_CLICK_HANDLERS