Design annotations are needed for specific instances shown below, but for the standard button component, Carbon already incorporates accessibility.
Carbon bakes keyboard operation into its components, improving the experience of blind users and others who operate via the keyboard. Carbon incorporates many other accessibility considerations, some of which are described below.
Buttons can be reached by
Tab and selected with
Icon-only butttons, which do not persistently display a text label, expose their label on hover and focus. When icon-only buttons are used to open menus, they are treated as separate components in Carbon. See Dropdown and Overflow menu.
Design annotations are needed for the following instances.
When buttons do not have a persistently displayed label, they must be annotated with a label that will be exposed on hover or focus.
Keep these considerations in mind if you are modifying Carbon or creating a custom component:
- Where links have been ‘repurposed’ as a button, they need to be coded so the
Spacekey can also activate (since links are only activated by default by
- Toggle buttons can be accessibility supported by changing the value of
"false"or with a change of name that reflects a change in the icon shape (for example: “play” / “pause” )
- See the ARIA authoring practices for more considerations.