GC Design System Components
Home Start to use Page templates overview Basic page Components overview Breadcrumbs Button Card Checkboxes Container Date input Date modified Details Error message Error summary Fieldset File uploader Footer Grid Header Heading Icon Input Language toggle Link Notice Pagination Radios Screenreader-only Search Select Side navigation Signature Stepper Text Textarea Theme and topic menu Top navigation CSS shortcuts overview Reset styles Responsive layout State Box sizing Container sizing Display Overflow Position Visibility Font Font family Font size Font style Font weight Line height Link colour Link size Link text decoration List style Text align Text colour Text overflow Text transform Word break Margin Padding Align content Align items Align self Flex Flex direction Flex grow Flex shrink Flex wrap Gap Grid columns Grid rows Justify content Justify items Justify self Order Place content Place items Place self Background colour Border colour Border radius Border style Border width Icon names Icon size Image Cursor Pointer events Transition Styles overview Design tokens Colour tokens Spacing tokens Typography tokens Contact us Get involved Find a demo

Error message
<gcds-error-message>

Also called: error, inline error.

An error message is a description of a problem blocking a user goal.

  • GitHub
  • Figma

Error message component preview

Build an error message

Use an error message for each response constraint of a component, when that component is required.

All GC Design System components already come with default error handling for required form components.

Coding and accessibility for error messages

Use error messages to support accessible task success

  • Make sure a person can immediately access the form controls associated with the label the error message is attached to.
  • Make your error message specific to avoid a user getting the same error message again after they thought they fixed the error.
  • Avoid introducing additional steps. Let a person know exactly what to do to fix the error so they can take action and resubmit or revalidate without having to do extra work.
  • Provide one or two solutions for fixing the error, not a multi-step process.

Follow a predictable format for error messages

Provide simple, fast guidance that's in context and interrupts the flow of action as minimally as possible:

  • Clearly identifies and points to the error.
  • Defines the error without making the user's actions the source of the problem.
  • Includes a call to action that's specific and actionable.

A person who receives an error message needs to:

  • Find the error and be able to access it.
  • Know what to do to fix it.
  • Be able to make the changes.
  • Resubmit or revalidate without having to fill out the whole form again.

Get your code

Generate an instance of the component you need by selecting its code properties.

  1. Explore by choosing different code values to generate the instance you want.

  2. Get the code and pull it into your environment.

  3. Add any copy you need to the component (like text for a label).

Note: The code builder uses English for all code elements, which follows standard practice.

Help us improve

Have questions or a request? Give feedback on our contact form.

Something's wrong? Raise it through GitHub with an account. You'll have access to the team's direct responses, progress made on your issue, and issues raised by others.

Give feedback Report an issue on GitHub
2024-02-21