SAP Fiori has five semantic colors that are associated with the following predefined value states:

• Bad / error
• Warning / critical
• Good / positive
• Neutral
• Information

SAP Fiori has five generic indication colors that are intended only for industry-specific use cases. You can associate these colors with a specific meaning in a given industry context (for example, to reflect industry standards).

Each application must clearly communicate the meaning of each color. In addition to using a color, you must also provide a text, such as an object status. All colors require a corresponding descriptive text for accessibility purposes.

The indication color palette is only supported for tables and for the object status.

Only use a semantic color if you need to convey the meaning defined for that color. This section looks at each semantic color in turn, and offers guidance on when to use each one.

Bad / Error

This color is used for errors, or to indicate a bad or negative status or consequence.

Use the bad/error semantic color if:

• Something bad has happened, or is about to happen. The issue requires the user’s attention. Until the issue is resolved, the user can’t carry on working.
• You want to indicate that a value has caused an error.
• The user needs to be prevented from finalizing the current mode or page.
• The user input failed a validation, and the problem must be fixed before the user can continue.
• A message contains information about an error.

Do not use the bad/error semantic color if:

• A status or event is fine. Use the good/positive color instead.
• The user input was validated successfully. Use the neutral color instead.
• The user input was validated and only minor problems occurred. The user can still finalize the current mode or page. Use the warning/critical color instead.
• You are using form field validation, and the surrounding page (or part of it) is in display mode.

An object has been damaged. The negative object status is used.

An error was identified while validating the entry for a checkbox. The checkbox has an error value state.

An error occurred while saving a draft. An error message box is used.

This color indicates a critical situation or warning.

Use the warning/critical semantic color if:

• You want to highlight a critical status.
• A minor problem has occurred. The user can carry on working, but might run into an error later on.
• The current mode or page can be finalized, but doing so might lead to an error later on.
• The user input was validated and a minor problem occurred. The user can continue without fixing the problem, but might run into an error later on.
• A message contains information about a warning.

Do not use the warning/critical semantic color if:

• The user input was validated successfully. Use the neutral color instead.
• The user input was validated and a major problem occurred. The user must fix the problem before finalizing the current mode or page. Use the bad/error color instead.
• You are using form field validation, and the surrounding page (or part of it) is in display mode.

The stock level for a product is low. The critical object status is used.

The user’s input could lead to an error later on. The input field has a warning value state.

The user tries to leave a page without saving. A warning message box is used.

This color stands for a good, positive situation, or for successful completion of a task.

Use the good/positive semantic color if:

• You want to highlight a good or positive status.
• A message contains information about a process that was finalized without any issues. Users will need this information later on (for example, values that need to be copied to another app).

Do not use the good/positive semantic color if:

• A process completed successfully and a short notification is enough. In this case, use a message toast instead.
• You are using form field validation, and the surrounding page (or part of it) is in display mode.

A product is available. The positive object status is used.

You want to indicate that the user’s input was successful. The input field has a success value state.

A success message needs to be acknowledged by the user. A success message box is used.

This color is used for a neutral state.

Use the neutral semantic color if:

• You want to indicate a neutral object status.
• There is no reason to use another value state.
• A message contains non-critical, additional information for users.

Do not use the neutral semantic color if:

• The user input was validated and a problem occurred. Depending on the severity, use the warning or error state instead.
• You want to highlight a positive or good thing. Use the good/positive color instead.
• A message contains information about a warning or error.
• You want to highlight a control.

You want the user to acknowledge a message, but no further action is required. Use the neutral information message box.

This color is used for an information state.

Use the information semantic color if:

• You want to draw attention to a control for an important purpose, such as visualizing the recommendations from intelligent systems in input fields.
• You want to highlight newly added items, such as a new table row.

Do not use the information semantic color if:

• The user input was validated and a problem occurred. Depending on the severity, use the warning or error state instead.
• You want to highlight something positive. Use the good/positive color instead.
• You want to highlight an information text. The blue text color is explicitly reserved for links.

The first row has just been added to the table. This is highlighted using the information color.

The input field is highlighted to draw attention to a system recommendation.