Checklist – Components
Alerts and Messaging
| Test | Priority | Automated test? |
|---|
| Are error states highly visible and specific? | High | None |
| Is a banner or dialog displaying when required fields are not complete? | High | Partial |
| Is the page title updated to indicate the error state when required fields are not completed? | High | None |
| Are error alert messages marked with role=”alertdialog” | High | None |
| Do error dialogs display as modals? | High | Partial |
| Are Aria Alerts or Live Regions being used to identify errors? | High | None |
| Does focus go to the error message in the banner or dialog automatically? | High | Partial |
| Test | Priority | Automated test? |
|---|
| Are all buttons properly enabled or disabled? | High | None |
| Test | Priority | Automated test? |
|---|
| Is field validation in place for each field? | High | Partial |
| Is form validation in place on submission? | High | Partial |
| Are invalid fields marked as invalid using aria-invalid? | High | Partial |
| Do fields only validate when the user is finished entering the value? | High | Partial |
Additional resources
How to Provide Accessible Form Error Identification by Jonathan Avila at Level Access.
