components
Checkbox
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 checkbox 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.
Behaviour
- Users can select one or more options from a selection.
- It should include a label that clearly indicates their purpose.
- They have to be grouped under a specific option. In order to help screen reader users, use the proper mark up to group and label checkboxes. If there is a single check don’t use tags to group checkboxes.
- If we are interacting using a mouse or equivalent, the selectable area should be not only the boxes but also their text labels.
Keyboard interaction and Screen-reader experience
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 checkboxes that are disabled must be indicated by programming. These disabled checkboxes do not receive keyboard or screen reader focus.
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.