Accessible design not only helps users with disabilities; it provides better user experiences for everyone. All Carbon components follow the IBM Accessibility Checklist which is based on WCAG AA, Section 508, and European standards. Carbon’s patterns are perceivable, operable, and understandable to users, even when using a screen reader or other assistive technology.
However, how you use Carbon also affects the accessibility of a product. Read this page to learn about accessibility in general. Then, while you’re working, use the role-specific Carbon accessibility guidelines to help you make products that anyone can use.
For a product to be considered accessible, it should:
- Give every user the same benefits, regardless of ability
- Adapt to any user in any context
Disabilities can be thought of as a mismatch between one’s ability and one’s environment, and can be broken into three main types:
|Situational||A person with typical vision might struggle to view their screen in a bright environment. Or, a person sitting in a library may be unable to watch a video with the audio turned on.|
|Temporary||A person with a broken wrist may not be able to type but will regain the ability when healed.|
|Long-lasting||This is what people typically think of when they hear “disability.”|
- May use a screen reader to experience interfaces
- May rely on Braille output
- Cannot be expected to use a pointer or mouse for input
- Is visual information translated effectively into text? Can the image be understood through its metadata alone?
- When possible, test all designs through a screen reader.
- As audio-only interfaces gain popularity through devices like AI assistants, users are expecting more and more from the audio representations of experiences.
Low vision can include partial sight in one or both eyes and can range from mild to severe. It affects approximately 4% of the world’s population.
- May use screen readers, screen magnifiers, high-contrast modes, and/or monochrome displays
- May have their browser font size adjusted to a larger setting
- May not use adaptive technology at all
- Maximize the readability and visual clarity of content.
- Consider how relative proximity of information changes when a page is magnified.
- Follow keyboard guidelines and test with a screen reader to ensure the page is read to the user in a logical order.
- To get a better understanding of the various low-vision disabilities, we recommend using the NoCoffee Chrome plugin to preview websites.
- Users without disabilities sometimes need to view screens in poor lighting conditions. For example, imagine using a screen outside on a bright day. A higher-contrast design will make the screen more usable for everyone.
- Vision worsens gradually starting around age 40, and good contrast helps this very large demographic use your interface.
Color-blindness affects 8% of all men and 0.4% of women.
- Will not be able to differentiate between some colors on an interface
- Rely on non-color information to use an interface
- Run your design through a color-blind simulator. If the design doesn’t work, try another approach. If you’re working in Sketch, we recommend the Stark plugin.
- May rely on captioning and other alternative representations of audio
- Find alternatives to conveying information exclusively with sound.
- Transcribe and caption all videos and animations that have meaningful audio.
- All users can benefit from closed captioning. Imagine using your device in a loud environment or, alternatively, in a quiet environment when it wouldn’t be appropriate to turn your sound on.
- May rely on keyboards, track balls, voice recognition, and other assistive technologies to interact with an interface
- May not be able to use a keyboard, mouse, or other pointer
- Design for good keyboard interaction, making sure all actions are keyboard accessible and efficient.
- Learn how to navigate using a keyboard and spend some time navigating the web, email, and digital products using only the keyboard.
- Many users prefer to navigate interfaces with a keyboard and no mouse for efficiency. Good keyboard navigation can help everyone be more productive.
These users offer a broad spectrum of concerns for design. Functional cognitive disabilities can include difficulty with:
- Problem solving
- Reading, linguistic, and verbal comprehension
- Math comprehension
- Visual comprehension
- May have limited working memory and need information to remain visible throughout the completion of a task
- May experience seizures when exposed to flashing content (epilepsy)
- Designers should understand the danger of complex language, non-stopping or flashing animations and fundamental cognitive usability heuristics.
- Design in as linear a fashion as possible and focus on design heuristics that have to do with cognitive load and memory.
- Best practices for cognitive disabilities benefit all users. Busy environments can tax your cognitive load. Aging adults may also experience a decline in cognitive abilities. Placing a low cognitive load on users reduces mistakes and improves effectiveness, regardless of their abilities.
- World Wide Web Consortium (W3C)‘s Web Accessibility Initiative (WAI) is an effort to improve the accessibility of the World Wide Web for people of all abilities.
- Web Accessibility Initiative (WAI) contributors create and maintain Web Content Accessibility Guidelines (WCAG), which is the global accessibility standard.