Problem/Motivation

When a form validation is displayed it has a "prohibition" icon to the left of the validation error text.

Claro:

page top error block in the Claro theme

Default Admin:

page top error block in the Default Admin theme

Olivero:

page top error block in the Olivero theme

The UX team commented in #2848507-212: Indicate that grouping elements have child element errors for ux and a11y (emphasis mine):

The association one has looking at a prohibition sign is not necessarily that of an error. Aside that, it also has to be noted that /admin/reports/status is using a different kind of icon for the error state - the iconography should be consistent across the entire admin UI, otherwise it creates ambiguity and increases the cognitive load.

@mherchel expressed a similar thought.

Steps to reproduce

1. Set Default Admin as the administration theme.
2. Go to `/admin/config/system/site-information`.
3. Clear the required `Site name` field.
4. Submit the form.
5. Observe the icon in the form validation error message.
6. Go to `/admin/reports/status` and compare the error iconography used there.

Observed result

The form validation error uses a prohibition-sign icon, which can be confused with a blocked or unavailable action rather than an error.

Expected result

Error-state icons should clearly communicate errors and be consistent with error iconography elsewhere in the admin UI.

Proposed resolution

Per @andrewmacpherson, they must all have distinct shapes.

UX team's suggestion:

The easiest fix for the error state, instead of using the prohibition sign is to simply use the "x" icon used on the status reports page for error admin messages and errors on parent elements as well.

That may work great for Claro.

For Default Admin, though:

  1. We can't simply switch to the icon on the status report, because it already uses the same prohibition sign on that page:
  2. The error summary block also has an "X" close button on the right. It seems that an "X" icon on the left would cause confusion in this case.

Also, this issue originally created with this concern:

An X icon usually denotes being able to click something to get rid of it.

Some suggestions

  1. For the error icon, use a red circle containing an exclamation point:
  2. Or, use a red octagon containing an exclamation point, and change Default Admin's warning icon to a triangle containing an exclamation point.

Remaining tasks

  1. UX review
  2. Decide on icon scheme(s).
  3. Implement the changes.

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

CatsFromStonehenge created an issue. See original summary.

cilefen’s picture

Issue tags: -form validation, -icons +Usability
andrewmacpherson’s picture

We already use an exclamation mark for another message level.

  • Cross in circle (red): Error.
  • Exclamation mark in triangle (yellow): Warning.
  • Tick (green): Status OK.

These icons are not limited to form validation, or even to message boxes. They are also used by the Status Report, Available Updates, and Recent Log Messages pages.

If we make any changes, we should consider the entire set. For accessibility, they must all have distinct shapes.

CatsFromStonehenge’s picture

Good idea about looking at the entire set Andrew. It almost needs a working group to bash on through with that. Cheers, Mike.

sarmiliboyz’s picture

Version: 8.2.x-dev » 8.4.x-dev

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +stale-issue-cleanup

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

kentr’s picture

This issue came up in the UX meeting in the discussion of #2848507: Indicate that grouping elements have child element errors for ux and a11y, and they underscored the need for consistency as well as a better "error" icon for that issue.

If I understand correctly the general concept is still relevant, but the details have changed.

Invalid form fields don't have any icon next to them.

In Default Admin, Claro and Olivero, the error blocks at the top of the page use a cross out icon.

page top error block in the Claro theme

page top error block in the Default Admin theme

page top error block in the Olivero theme

The status page still uses a red circle with a white "X" in Claro. In Default Admin, it uses the cross out icon.

Suggestion for a new error icon

Red circle containing an exclamation mark. It's distinguished from a warning icon by the shape and color.

Here's a very rough example modified from an existing icon in core. IMO outline icons would be better for some uses.

red circle containing white exclamation point

kentr’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Active
Issue tags: +Needs usability review, +Needs issue summary update
StatusFileSize
new41.43 KB
new43.81 KB

Going out on a limb and reopening. The UX team commented in #2848507-212: Indicate that grouping elements have child element errors for ux and a11y (emphasis mine):

The group was in line with the comment in#189. The association one has looking at a prohibition sign is not necessarily that of an error. Aside that, it also has to be noted that /admin/reports/status is using a different kind of icon for the error state - the iconography should be consistent across the entire admin UI, otherwise it creates ambiguity and increases the cognitive load.

The iconography used across the Drupal admin interface for errors, warnings and informational states on /admin/reports/status, admin messages, and on for example errors on this issue should be consistent. The easiest fix for the error state, instead of using the prohibition sign is to simply use the "x" icon used on the status reports page for error admin messages and errors on parent elements as well.

But, the problem is that the prohibition sign in the error summary block at the top of the page is preexisting. I'm not sure that we can decide to change it in #2848507: Indicate that grouping elements have child element errors for ux and a11y.

Also, for Default Admin, we can't just switch to the icon used on the status report page. As noted in #20 Default Admin uses the prohibition / cross out icon on that page.

Screenshot:

This looks like the proper issue for sorting all of that out.

Suggested exclamation point inside a circle again, solid and outline versions, in Claro's input error red color (hex color #dc2323):

SVG code for the outline version:

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="20" height="20">
  <circle cx="8" cy="8" r="7" fill="none" stroke="#dc2323" stroke-width="2" />
  <path fill="none" stroke="#dc2323" stroke-width="2" d="M8 4v6m0 1v2" />
</svg>

I think that SVG code is public domain. It's a modified version of https://publicdomainvectors.org/en/free-clipart/Small-warning-icon/59595..., and the site says:

Public domain
Vector images provided via download on publicdomainvectors.org are bound to Creative Commons Deed CC0.

You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission.

Although absolutely not required, a link back to Public domain vectors is always welcome.

kentr’s picture

mgifford’s picture

Issue summary: View changes
mgifford’s picture