Category: Forms and Inputs
Tests that verify the proper use of forms and inputs (buttons, selects, etc.)
| 5 | 1.1.1 Non-text Content (A) | CAPTCHAs must be identified with alternative text |
|---|---|---|
| 6 | 1.1.1 Non-text Content (A) | CAPTCHAs which require user input offer at least two different modalities (e.g. visual and auditory) |
| 18 | 1.3.1 Info and Relationships (A) | Form inputs must have labels which are readable (programmatically determinable) by assistive technology. |
| 19 | 1.3.1 Info and Relationships (A) | Form input groupings (i.e., related radio buttons, related checkboxes, related text inputs like First/Last name) are grouped semantically. |
| 29 | 1.3.5 Identify Input Purpose (AA) | The purpose of any form input about the user is identified in code when the purpose is defined in HTML. |
| 61 | 2.4.6 Headings and Labels (AA) | Labels describe the purpose of the inputs they are associated with. |
| 66 | 2.5.3 Label in Name (A) | For user interface components with labels that include text or images of text, the accessible name contains the text that is presented visually. |
| 78 | 3.3.1 Error Identification (A) | Whenever an input error is detected through validation, the user is informed of the error, and what was incorrect in the input. |
| 79 | 3.3.2 Labels or Instructions (A) | Visible labels or instructions are available for all inputs and input groupings. |
| 80 | 3.3.2 Labels or Instructions (A) | Labels describe any required fields or required formatting requirements. (e.g. If a MM/DD/YYYY format is required) |
| 81 | 3.3.3 Error Suggestion (AA) | If an input error was detected due to a blank input on a required field, the user is informed of the fields which were left blank in the error message. |
| 82 | 3.3.3 Error Suggestion (AA) | If an input error was detected due to an input that did not follow required formatting, the user is informed of the proper formatting in the error message. |
| 83 | 3.3.3 Error Suggestion (AA) | If an input error was detected that was outside of the allowable range of values, the user is informed of the proper range in the error message. |
| 84 | 3.3.4 Error Prevention (Legal, Financial, Data) (AA) | Any legal or financial data input must be reversible, validated for input errors, or include a mechanism for reviewing, confirming, or correcting information before submission. |
| 85 | 3.3.7 Redundant Entry (A) | Users are not required to refill the same information in the same process unless it is available as a selection, is essential, is ensuring security, or the original information is no longer valid. |
| 86 | 3.3.8 Accessible Authentication (AA) | Login processes must not solely rely on cognitive tests. All steps in a login process must support some method that does not rely on memory or knowledge. |