Heading

    Headings are used as the titles of each major section of a page in the interface. For example, card components generally use headings as their title.

    Examples

    Down Arrow

    Use for the title of each top-level page section.


    Best practices

    Headings should:

    • Clearly describe the section of interface they refer to
    • Highlight the most important concept or piece of information merchants need to know
    • Sit at the top of the section of interface they’re referring to

    Content guidelines

    Headings should follow the content guidelines for headings and subheadings.



    Accessibility

    See Material Design and development documentation about accessibility for Android:

    See Apple’s Human Interface Guidelines and API documentation about accessibility for iOS:

    A clear and consistent heading structure helps merchants who have difficulty with reading or language. It also helps screen reader users to navigate the page using keystrokes that are custom to their screen reader.

    Use the element prop to determine the specific HTML element that’s output for the heading. The component defaults to a level 2 heading (<h2>). Use a different value for the element prop if a different heading fits the context better.

    Learn more about writing helpful headings and subheadings.

    Do

    Use headings to support the hierarchy and structure of the page.

    Don’t

    Use headings for style alone.