Problem/Motivation

This is a followup for #2848507: Indicate that grouping elements have child element errors for ux and a11y to make the changes specifically in Default Admin.

It's postponed on #3582351: [Meta] Clean up CSS and #2848507: Indicate that grouping elements have child element errors for ux and a11y.

Child elements in grouping elements like (meta) details and vertical tabs are invisible to the user when the grouping element is closed or not-focused respectively.
To improve the user experience and accessibility we should indicate when there are errors 'inside'.
Currently it is hard for the user to find the actual problematic field when the (child) field itself is invisible.

Steps to reproduce

Proposed resolution

The work in #2848507: Indicate that grouping elements have child element errors for ux and a11y might be usable here with only slight modifications. However, it will likely need UX input that will also apply to Default Admin.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

kentr created an issue. See original summary.

kentr’s picture

Title: [PP-1] Indicate that grouping elements have child element errors for ux and a11y » [PP-2] Indicate that grouping elements have child element errors for ux and a11y
Issue summary: View changes

This might be do-able now that #3599680: Consolidate, merge, and refactor Gin's CSS variable's into Admin theme's original variables. has landed.

However, it should now wait on #2848507: Indicate that grouping elements have child element errors for ux and a11y, because that work might be usable here with only slight modifications and it will likely need UX input that will also apply to Default Admin.

kentr’s picture

because that work might be usable here with only slight modifications and it will likely need UX input that will also apply to Default Admin.

Err, and also because there are changes outside of the theme.