WCAG 3.3.1: Error Identification

If an input error is automatically detected, the item in error must be identified and the error described to the user in text.

Understandable Level A Serious Impact

Check if your website passes WCAG 3.3.1

Common Failures

Color-only error indicators, errors shown only as toast notifications, missing error messages on required fields.

How to Fix

Display clear, text-based error messages near the relevant form field. Do not rely solely on color to indicate errors. Use aria-describedby to associate errors with inputs.

How EAAPass Tests WCAG 3.3.1

EAAPass automatically tests WCAG 3.3.1 (Error Identification) using three engines simultaneously:

  • axe-core — Checks DOM elements against the 3.3.1 rule set
  • Google Lighthouse — Validates accessibility in the context of overall page quality
  • Pa11y — HTML_CodeSniffer integration for WCAG-specific testing
  • AI Validation — Claude AI reviews ambiguous results to eliminate false positives

Results are mapped to the Understandable POUR principle and scored based on severity and frequency.

Industries Most Affected by WCAG 3.3.1

Banking & Financial Services Insurance

Other WCAG 2.1 AA Criteria

WCAG 1.1.1 Non-text Content Perceivable WCAG 1.3.1 Info and Relationships Perceivable WCAG 1.4.3 Contrast (Minimum) Perceivable WCAG 2.1.1 Keyboard Operable WCAG 2.4.4 Link Purpose (In Context) Operable WCAG 3.1.1 Language of Page Understandable WCAG 4.1.2 Name, Role, Value Robust

Test WCAG 3.3.1 on your website

Free WCAG 2.1 AA audit covering all 50 success criteria. No signup required.

Run free audit