Tools
These are almost all the rules that are tested involving forms. Most of them require mouse and keyboard interactions and data addition.
Important Make sure you really understand the success criteria because some rules are testing just one specific aspect of an input.
Rule number | Rule | How to test |
---|---|---|
1.3.1 | Info and relationships | Code and visual assessment + Screen reader |
1.3.5 | Identify input purpose | Code assessment |
2.5.3 | Label in name | Tabbing + Screen reader |
3.2.2 | On input | Mouse + keyboard interaction |
3.3.1 | Error identification | Interaction + screen reader |
3.3.2 | Labels or instructions | Code and visual assessment |
3.3.3 | Error suggestion | Interaction |
Go through your page visually, using a screen reader and using a makeshift style sheet. Check each version to see if the information and relationships on the page change between presentations. It should not change, the page should be presented the same way every time.
This rule works together with the rules 3.3.2 Labels or instructions and 4.1.2 Name, role, value
Go through your code (specially forms) and make sure your inputs have the correct type, name and follow the rules for autocomplete. This ensures the inputs can be properly filled by user agents if the user has difficulties filling forms.
Tab through your content and check if the labels in your page have the same text as what is read out by the screen reader. Accessible names should include the label to easier navigation.
Interact with your form components (click and enter data) and make sure all effects that result from the interactions are expected and don't change the context for the user.
Interact with your form inputs and cause errors to check if the errors are announced, are properly identified and tied to the input.
Check your page for content that requires a label (like inputs and buttons) and make sure the labels are there.
This rule works together with the rules 1.3.1 Info and relantionships and 4.1.2 Name, role, value
Interact with your form component errors to ensure possible corrections are presented to the user.
This rule works together with 3.3.1 Error Identification
Continue to Basic element usage.
Is this page helpful?