components
Input Dropdown
v.1.0.0 | SaturnAccessibility is a crucial consideration when designing and developing components, as it ensures that all users, regardless of their abilities or limitations, can interact effectively with your project. In this section, we will explore how our inputDropdown has been developed with accessibility in mind, ensuring that all users have a smooth and meaningful experience.
The following mencioned props and recommendations are optional, althougt at Kubit strongly recommend their use to meet accessibility standars.
Text
Options within the dropdown should be distinctive, short and concise. Do not use dropdowns to display complex information and do not include links as options. Avoid using very long names in the options within the dropdown. That will facilitate understandability and perceivability. In addition, do not use the same word or phrase at the beginning of a set of options to make them distinct easily.
Helper texts and error messages must clearly indicate the information. In error messages, when possible, include information about how to correct them.
Icon
Error icon needs an accessible text label, such as "Error". The icon will be indicated as decorative when the message itself indicates to the user that it is an error message. Other decorative icons should be hidden for screen reader users.
Screenreader and Keyboard interactions
To support screen reader users, this component should include WAI ARIA attributes (the alt and aria specific props) to have a correct semantic markup. Screen reader and keyboard users should be able to operate with all the interactive elements.
The fields that are disabled must be indicated by programming. These disabled fields do not receive keyboard or screen reader focus. When an input has an error and/or help text, it is necessary to associate these texts to the input so that the screen reader user is informed. If there is an error in the mbInput, this error information has to be announced to screen reader users.
Required fields identified with an asterisk may not always being announce for screen reader users. Use semantic markup in order to screen readers could identify required fields.
Dropdown mobile
In the mobile version, the input usually acts as a button that opens a modal. In this specific case, a series of adaptations must be made to guarantee the total accessibility of the component:
- The dropdown must be labelled as a button.
- The screen reader should be informed that the dropdown options open in a modal.
- Once the modal is displayed, the keyboard or screen reader focus must be positioned over the first enabled option.
- The screen reader user should be informed of the selected option.
- If the user selects an option, the modal should be closed and the focus should return to the dropdown.
- The screen reader must interpret the description of the dropdown, the selected option, the instruction that the options open in a modal and its button role.
Visual design
Color contrast
- For text labels in links needs a color contrast of at least 4'5:1 for regular text and 3:1 for large scale (18pt) or bold text (14pt).
- For the rest of elements and the focus indicator at least of 3:1 color contrast ratio is needed.
Target Size
The area for clicking and tapping buttons must be large enough. The recommended size of the target for pointer inputs is at least 24x24px and 44x44px for best readability.
Related components
Check other components specific accesibility recommendations:
