Skip to main contentCarbon Design System

UI shell header

Design annotations are needed for specific instances shown below, but for the standard UI shell header component, Carbon already incorporates accessibility.

Accessibility testing status

For every latest release, Carbon runs tests on all components to meet the accessibility requirements. These different statuses report the work that Carbon has done in the back end. These tests appear only when the components are stable.

Latest version: ^1.61.0 | Framework: React (@carbon/react)

ComponentAccessibility testStatusLink to source code
UI shellTest(s) that ensure the initial render state of a component is accessible.Passes all automated tests with no reported accessibility violations.GitHub link
Tests that ensure additional states of the component are accessible. This could be interactive states of a component or its multiple variants.Passes all automated tests with no reported accessibility violations.
Tests that ensure focus is properly managed, and all interactive functions of a component have a proper keyboard-accessible equivalent.Passes all automated tests with no reported accessibility violations.
This manual testing ensures that the visual information on the screen is properly conveyed and read correctly by screen readers such as JAWS, VoiceOver, and NVDA.A human has manually tested this component, e.g. screen reader testing.

What Carbon provides

The Carbon header bakes in keyboard interaction, including a skip-to-main-content mechanism. Carbon also supports assistive technologies such as screen readers by setting labeling and page structure.

Keyboard interaction

Each element in the header can be reached by the Tab key. A “Skip to main content” link appears when a keyboard user first tabs into the page. Links and icons are activated by Enter. Icons can also be activated by Space.

example of header keyboard interaction

Pressing the Tab key reveals a 'Skip to main' link and then moves between other header elements.

Regions

example of header keyboard interaction

Carbon applies a header region around the whole UI shell header.

Labeling

Carbon provides default names for each icon-only button in the header, and these names are revealed on hover or focus. Interactions for some header components are covered under other component topics such as search, notifications, and the UI shell right panel switcher.

annotation showing search, help, notification and app switcher icons

Carbon provides default names for its icon-only components and reveals them on hover or focus.

Design recommendations

For every product, there should be a one-time design exercise to annotate the UI shell keyboard interaction. This is an important step to carry out, since header functionality and component names vary significantly between products, even though they appear similar until interacted with. Annotating expected behavior increases consistent implementation. Where the product does not deviate from the standard Carbon implementation, it can merely be annotated that the behaviour matches what is in the ‘How Carbon works’ section.

Annotated header region stating 'Header functionality, roles and names match Carbon defaults'

Annotate the header, even if your design matches the default Carbon UI shell header behavior.

Once a product-specific header annotation exists, individual product pages only need to annotate the header if something differs.

Where the header deviates from the default Carbon behavior or labeling, it should be annotated. Such annotations could call out different labels for icons or indicate interaction changes such as keyboard navigation.

an annotation stating the search bar is persistently expanded

Annotate if the design modifies the default keyboard or component interaction.

Development considerations

Keep these considerations in mind if you are modifying Carbon or creating a custom component.

  • Carbon uses the HTML 5 header component instead of an ARIA landmark to set the region.
  • Carbon includes the “Skip to main content” link as the first item on the page with a tabindex="0", but hides it through CSS until it receives focus.