Skip to main content

Back to Guidelines

What is Error Identification?

Errors should be clearly identified with text and visual cues.

Errors should be clearly identified with text and visual cues.

Keyboard and screen reader users.
People who need predictable interactions.
Users who benefit from visible focus and clear labels.

Good vs Bad Examples

Use the tabs to compare the accessible pattern with the example to avoid.

Good Example

Form error clearly identifies the invalid field.

html

<div />

Why this is correct (developer logic):

Provides an accessible and predictable interaction.
Works better for keyboard and assistive technology users.
Matches the intended WCAG requirement for this page.

Implementation Checklist

Progress0 / 5 completed (0%)

Keep the interaction predictable and easy to understand.
Test with keyboard and screen reader navigation.
Make sure focus is visible and easy to track.
Avoid hidden, unexpected, or unnecessary repetition.
Confirm the example meets the intended accessibility requirement.

Knowledge Check

Answer Yes or No to test your understanding of error identification.

Score: 0 / 3 · Answered: 0 / 3

Does the good example demonstrate error identification correctly?

Is the bad example acceptable for error identification?

Should this pattern be checked with keyboard and screen reader testing?