Problem/Motivation

This is a brain dump of problems seen with the Default Admin forms sidebar, such as on the node edit form. They need to be triaged and fleshed out into separate issues with details.

Tested on main as of commit 03e37d380df (Mon Aug 24 17:05:17 2026 +0100).

I didn't check for existing issues in the Gin queue or compare with the Gin theme.

  1. #3619153: Admin theme's collapsed / hidden sidebar should be operable without JavaScript
  2. #3619154: Accessibility fixes for Admin theme's toggle control
  3. #3619155: Admin theme's toggle button disappears on hover/focus in forced colors
  4. #3619156: Investigate and fix tab order issues on Admin theme's sidebar toggle
  5. Also folded into #3619154: Accessibility fixes for Admin theme's toggle control
  6. Also folded into #3619154: Accessibility fixes for Admin theme's toggle control
  7. #3619127: Forms sidebar doesn't work with error links from Inline Form Errors module
  8. Also folded into #3619154: Accessibility fixes for Admin theme's toggle control

Comments

kentr created an issue. See original summary.

kentr’s picture

Issue summary: View changes
kentr’s picture

Title: [meta] Forms sidebar accessibility issues » [Meta] Forms sidebar accessibility issues
Category: Bug report » Plan
kentr’s picture

Issue summary: View changes
kentr’s picture

Issue summary: View changes
mgifford’s picture

This is great. Thanks @KentR.

It will definitely need to be broken into sub-issues, which hopefully @mherchel can take on.

We looked at it this morning, and there are definitely some legacy Gin issues that we need to clean up.

Some of these issues can be solved by using the PopOver API rather than custom JS.

We had some challenges testing Inline Form Errors in the sidebar, as I think we need a custom module to put custom fields into the sidebar.

Some of this is a best practice and not technically a WCAG failure. That's fine, still good to do for usability.

Noting that the behavior is different in mobile than desktop is interesting. It is a modal in mobile.

Escape is currently used to minimize the left sidebar, possibly hitting escape again could minimize the right sidebar (or if the left sidebar is already minimized, it minimizes the right one).

kentr’s picture

To see the problem with IFE, follow STR #5 in #2848507: Indicate that grouping elements have child element errors for ux and a11y (For "accordion" style details elements on the node edit form), but with Default Admin and a narrower viewport so that the sidebar is closed / hidden.

Edit: IOW, no need for a custom module...

I'm planning to work on the IFE problem next since I'm working on the related sidebar problems in #3604037: [PP-1] Indicate that grouping elements have child element errors for UX and a11y.

mherchel’s picture

Assigned: Unassigned » mherchel

Will break these out later today or tonight

kentr’s picture

Issue summary: View changes

I went ahead and created the issue related to IFE since I know the STR and am working with the sidebar ATM: #3619127: Forms sidebar doesn't work with error links from Inline Form Errors module.

kentr’s picture

Issue summary: View changes

Added another:

Similar to the toggle control, the close button shouldn't be rendered as a link with role="button".

kentr’s picture

Issue summary: View changes
kentr’s picture

By accident I think figured out why the tab sequence inside the sidebar is off.

There's a form container named default_admin_sidebar that contains the close button and the Published (aka status) field.

But the element that contains all of the elements in the sidebar is actually the advanced container. This default_admin_sidebar container is inside the advanced container.

So, the Revision log message field precedes the close button in the DOM.

In the DOM, the sidebar is id="edit-advanced" and this inner element with the close button is id="edit-default-admin-sidebar".

mherchel’s picture

Issue summary: View changes

Did a little splitting. Will work on it more tomorrow.

mherchel’s picture

Issue summary: View changes
mherchel’s picture

Status: Active » Closed (outdated)

Going to close this out as its all split up now. We can use #3576488: [meta] Admin theme: path to beta and stable to track these.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.