responsibility: Code
Collection of success criterion where the responsibility falls under technical implementation and developer tasks.
3.3.1 Error Identification
Errors must be clearly indicated and described to the user.
3.3.2 Labels or Instructions
Provide enough help to prevent form errors—sometimes the label is enough, but hint text or instructions might also be needed.
3.3.3 Error Suggestion
Helpful suggestions should be provided to help users correct their errors.
3.3.4 Error Prevention (Legal, Financial, Data)
Important forms like a legal agreement or submitting financial information offer the opportunity to check the information entered before sending.
3.3.5 Help
Where a label can’t provide enough information to understand what’s being asked, there’s hint text or some other kind of explanation alongside.
3.3.6 Error Prevention (All)
After entering any information, the user is offered the opportunity to check it before sending.
3.3.7 Redundant Entry
Users should not have to re-enter previously provided information unless necessary.
3.3.8 Accessible Authentication (Minimum)
Authentication must be possible without cognitive challenges like memorization or solving puzzles, unless an alternative exists.
3.3.9 Accessible Authentication (Enhanced)
Authentication must be possible without any cognitive function test.
4.1.1 Parsing
The markup has been validated and there are no errors, such as duplicate ids, missing tags, and invalid child elements.
