Developer What component has
Keyboard support
| Key | Function |
|---|---|
Tab | Moves focus to the next focusable element. |
Shift + Tab | Moves focus to the previous focusable element. |
Enter | Submits the entered value. |
See detailed information about the keyboard support for the input fields in the Keyboard control guide.
Considerations for developers
- Keep it simple – not all browsers correctly expose multiple labels that are linked to the same form element.
- Use labels for every input and make the
for=""andid=""values match. IDs must be unique on each page, only one label can be associated to each unique form element. Make required fields obvious by using an indicator – asterisk, description text, etc. - Help text is crucial in ensuring accessibility of form fields. Fields with constraints should have visible instructions that are programmatically associated, such as through
aria-describedby. Include help text for all masked fields. - Fields with error validation should have
aria-describedbyto insure that the associated field level error message is read by assistive technology. If the error message has anid="my-error-message", then the input should havearia-describedby="my-error-message".
Find live examples in the A11y style guide.
Considerations for designers
- Focus must be visible.
- Don’t hide the input label on focus.
Resources
- A11y style guide describes core principles for the accessible inputs and textarea.
- Find live examples of accessible inputs with different types in DigitalA11y project.
Other recommendations
See more accessibility recommendations in the common Accessibility guide.