Skip to content
Barrierefrei²

Success criterion 3.3.1

3.3.1 Error Identification

Level AUnderstandable

When the form tells you what went wrong.

1. What is the goal of this criterion?

Forms are like a first date – if something goes wrong, you want to know exactly what didn’t work. But imagine filling in an important form, clicking “Submit” and … nothing happens. Or worse: something is clearly wrong, but nobody tells you what.

People who rely on screen readers or can’t tell colours apart are literally left in the dark by purely visual error messages. So the goal of Success Criterion 3.3.1 is clear: when an error is detected automatically, the problem and its location must be described in text.

2. What exactly does it require?

Specifically, it’s about automatically detected input errors – situations in which the system notices that something isn’t right. It doesn’t matter whether the check happens in the browser or on the server after submission.

As soon as an error is detected, two things must happen:

  • Identify: the field in error is clearly named
  • Describe: the error is explained in understandable text

What counts as an input error?

  • Required fields left empty
  • Data in the wrong format (e.g. “max.mustermann” instead of “max@mustermann.de”)
  • Values outside the allowed range (e.g. a birth year of 2050)

Important: you’re welcome to use colours, icons and visual highlighting in addition – but text is mandatory. A red border on its own isn’t enough (see also Use of Color).

3. Why does it matter for accessibility?

Imagine sitting in a café filling in an online form and all you get is a red border around a field – with no explanation of what’s wrong. Frustrating, right? For people with disabilities, this can be a complete roadblock.

Text-based error messages support accessibility because they:

  • let blind and visually impaired people understand errors through their screen reader
  • help people with colour vision deficiency who can’t reliably perceive colour coding alone – around 8% of men and 0.5% of women of Northern European descent
  • support people with cognitive disabilities with clear language when correcting mistakes
  • take the pressure off everyone in difficult situations (poor lighting, stress, time pressure)

And last but not least: clear error messages reduce support requests and abandonment – a win for everyone.

4. How to meet the criterion

The quality of your error messages decides whether people reach their goal or give up in frustration. Here are the most proven practices:

Good error messages are …

  • specific: instead of “Invalid input”, say “The email address must contain an @ sign”
  • understandable: use plain language and avoid jargon
  • helpful: give concrete hints for fixing it (“Format: DD.MM.YYYY”) – that’s the core of Error Suggestion
  • findable: place them close to the affected field and/or list them at the top of the form with links to the fields

Technical implementation:

  • Use aria-invalid="true" on fields in error
  • Connect error messages with aria-describedby so they’re read out when the field receives focus
  • After submission, move focus to an error summary or the first field in error
  • For messages that appear dynamically without a focus change, live regions such as role="alert" work well (see Status Messages) – use them sparingly so messages aren’t read out twice

Proven pattern:

<label for="email">Email address (required)</label>
<input id="email" type="email" aria-invalid="true"
  aria-describedby="email-error">
<p id="email-error">
  Error: The email address is invalid. Example: max@example.com
</p>

Tools and resources:

  • Use validation libraries that output errors accessibly
  • Test with screen readers (NVDA, JAWS, VoiceOver)
  • Check how understandable your messages are with real users

5. Why this criterion matters for businesses

With Success Criterion 3.3.1, too, accessibility isn’t an end in itself – it brings tangible benefits for your business.

1. Reach a wider audience

According to the WHO, around 1.3 billion people worldwide live with a significant disability. Clear error messages help them – and everyone else too. That pays off directly at key moments such as orders or sign-ups.

2. Lighten the load on customer support

Understandable error messages reduce support requests. Instead of asking “Why isn’t the form working?”, people get the information they need to fix the problem themselves straight away. That saves time and money.

3. Fewer drop-offs

People who quickly understand and fix errors are less likely to give up. Every form that’s successfully submitted in the end is an enquiry or order won.

And then there’s the legal side: since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to many consumer-facing digital services, such as online shops and banking services. Germany implements it through the Barrierefreiheitsstärkungsgesetz (BFSG). The technical benchmark is the harmonised standard EN 301 549, which refers to WCAG 2.1 Level AA for web content – and 3.3.1 is part of that. Public sector bodies are covered separately by the Web Accessibility Directive (EU) 2016/2102. This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 3.3.1 Error Identification (Level A)

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

In short: if an input error is detected automatically, the affected field must be identified and the error described in text.

Official explanation from the W3C

The W3C explains every success criterion in depth – with intent, examples and techniques.

Understanding 3.3.1 (opens in a new tab)