‘Error Identification’ requires websites to identify and describe input errors for users.


Users of all kinds will make mistakes when using your website, so it’s important to clearly identify and describe errors. Input errors include users not providing required information as well as providing informating that doesn’t meet validation criteria.

Be as specific as possible when highlighting an error, so a user has the best chance of fixing their mistake and continuing. This means doing more than adding a red box around a missed field for example.

How to Pass ‘Error Identification’

  • Identify and explain to the user any mistakes that you can detect automatically.
  • Add error explanation close to the error, showing what is wrong and how to fix it.

‘Error Identification’ Tips

  • If a form requires input in a certain format, show and describe the required format.
  • If a mandatory field is empty, highlight the field and explain what’s required.
  • Build forms to be forgiving, accepting variations on the formats you prefer.
  • Don’t ask for too much information, just what you need.
  • Be specific. Use clear, concise instruction and form field labels.
  • Highlight mistakes in forms with colours and symbols.
  • Don’t clear a form if a user makes a mistake. Save the information and allow the user to edit their error and continue.
  • Provide extra help by giving your contact details on all pages (the header or footer are great) and especially near forms.

See Also

Free Developer Resources

Join over 3,700 subscribers on my weekly web accessibility email and get free developer resources like WCAG Checklists and special offers.

Powered by ConvertKit

Over 600 developers like you have learned more about the Web Content Accessibility Guidelines with my guidebook.

Learn more >

About Author

I'm Luke, I started Wuhcag in 2012 to help people like you get to grips with web accessibility. Check out my book, 'How to Meet the WCAG 2.0'.

3 comments on “Error Identification (Level A – 3.3.1 )

    Richard says:

    And for improved usability – reduce the potential for errors by being as flexible as you can in accepting input. For example:
    – allow users to put spaces in a phone number if they want to, but don’t enforce it (same for a sixteen digit credit card number)
    – if you ask for a postcode for searching for e.g. a nearby store, then don’t insist on a full postcode, the first part could well be enough for the user to make an informed decision about location.
    – minimise the amount of required information. If a user is signing up to something you can always ask for more details later.
    – by all means validate things like email addresses, but with caution, because the rules for what constitutes a valid email name are quite complex. More than once my .eu email address has been rejected by a form as an unrecognised TLD (Top level Domain) name.


    I go to see every day some sites and websites to read content, except this weblog presents feature
    based writing.


Leave Comment