Accessibility
Arc product designers should design for the needs, environments, and capabilities of all of our users by advocating for accessibility best practices in design and development.
#Principles of Accessibility
- Perceivable: Information and user interface components must be presented to users in ways they can understand.
- Operable: User interface components and navigation must be usable.
- Understandable: Information and the operation of user interface must be understandable.
- Flexible: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
#Accessibility and the Design System
- Are contrast levels adequate for users who have one or more forms of disability with their vision? This is an example of the perceivable principle.
- Are indicators, labels, or other ways of conveying information able to do so without color? For example, a graphic with a specific color but no text label may not be interpreted correctly by users who have color blindness. This is an example of the understandable principle.
- Are all elements of the interface keyboard operable? Is the tab index clear, usually working left to right*? Are there any functions in the component or pattern which are not accessible via keyboard? This is an example of the *operable* principle.
- Do the developers have the information they need to provide ARIA labels which will allow assistive technology to work with the component or pattern? This is an example of the flexible and operable principles.
- Are various states in a component or pattern clear, available (doesn’t disappear quickly, or is often dismissed accidentally), and understandable by human beings? This is an example of the understandable principle.
*At the moment the design system doesn’t support right to left reading patterns. This is likely to change in the future, so if there is an opportunity to solve for additional reading patterns, consider capturing that.
Copyright 2021 Arc XP
Arc Design System