Skip to main content

An official website of the United States government

Here's how you know

An official website of the United States government

Here's how you know

Theme:

Design system switcher

Version:

Design system switcher

Theme:

Design system switcher

Version:

Design system switcher

Hint

Hint text is used in combination with a Label to provide extra instructions or context for form fields.

Examples

Loading

Code

React

See Storybook for React guidance of this component.

Web Component

See Storybook for Web Component guidance of this component.

Style customization

The following CSS variables can be overridden to customize Form components:

CSS variables for form
VariableDefault Core Theme Value

Guidance

  • Hints are built in to all design-system form fields but can be used on their own to create custom fields.
  • Use hint text for supporting contextual help that is always visible.
  • Hint text should sit between a form label and the input.
  • Use lower visual style (i.e., lighter gray than the form label or the input option) so it won't compete for users' attention with the field label.
  • Use hint text to indicate which inputs are optional when there are more required fields than optional.
  • Hint text can also appear after an input box when the text is being used to show the value someone should be entering in the field (e.g., income amount input box displays text after the input box to highlight the amount should be "monthly income".)

Content

  • Use when appropriate to support a field label.
  • Describe how to best answer the question/form label.
  • Use the fewest words possible (i.e. don't use "please").
  • Use sentence case.
  • End with a period.
  • Be consistent with phrase and sentence structure.

Accessibility testing

General observations

  • Hint text should be outside of the label element.
  • Hints should be linked to their corresponding input fields via an aria-describedby attribute on the input.
  • Hint text should meet size and contrast requirements.

Screen reader testing

  • When the input field gets focus, its label should be read first and then its hint after a slight delay.

Learn More

Component maturity

For more information about how we tested and validated our work for each checklist item, read our component maturity documentation.

Accessibility

  • Color

    Meets AA color contrast standards for accessibility and color blindness.
    Complete
  • Forced Colors Mode (FCM)

    While using FCM the components text is legible and improves readability.
    Complete
  • WCAG 2.1 Level AA Conformance

    All Axe checks for WCAG AA compliance have passed.
    Complete
  • Screen readers

    VoiceOver, NVDA, and JAWS screen readers provide concise communication and interaction.
    Complete
  • Keyboard navigation

    Component is fully navigable with a keyboard.
    Not applicable

Code

  • Storybook

    Component has stories to cover all defined props.
    Complete
  • Responsive

    Component designed to work in all responsive breakpoints.
    Complete
  • Spanish translations

    Includes Spanish translations for default text content.
    Complete

Tokens

  • Code

    Tokens implemented in code.
    Complete
  • Design

    Tokens implemented in the Sketch.
    Complete