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.

Testing & Remediation

How to test: Open your website in a browser of your choice and navigate to the pages where components exist that accept user input. Enter deliberately wrong values for the fields and submit the form. For each component with erroneous data, ensure that the error is identified in text. How to remediate: There are a number of techniques that can be deployed to remediate issues related to this Success Criterion: For forms that contain mandatory fields:
  • Provide text descriptions to identify required fields that were not completed
  • Use aria-invalid to indicate an error field
  • Providing client-side validation & alert
For forms/functionality where info provided by the user is required to be in a specific data format or of certain values:
  • Use aria-alertdialog to identify errors
  • Use aria role=alert to identify errors
  • Use aria-invalid to indicate an error field
  • Client-side validation & alerts

Questions and Answers

How do I know if my websites structure is layed out correctly?

Your site should have the correct semantic elements (header, main, footer, article, etc) in the order that they are intended to be read. This means that sometimes this isn't the order that makes styling the page the easiest. You must also ensure that all your heading levels are hit in the order. This means that you should not skip from an h1 to an h4, and so on.

How long does the accessibliity process take?

This question depends on a number of factors including size of site, desired level of conformance, your developer's understanding of accessibility techniques, etc. Accessible Web is here to help. Reach out and we can discuss your site specifically.