Problem/Motivation

This is a follow-up issue from the discussion that was bought up in #3186349: Major accessibility problems with Olivero header show/hide feature.

From @andrewmacpherson

The issue of whether an "X" close-icon was mentioned in #9 as a possible follow-up. We decided to leave it for now, since it's highly bikeshed-able. Now that 2 accessibility maintainers have noted it, I think we should have that follow-up for sure, so I'll create that. I think it could be better as an in/out chevron-arrow, similar to the >> and << used by some application sidebars (like GitLab).

Comments

proeung created an issue. See original summary.

proeung’s picture

mherchel’s picture

Title: Header menu "X" close-icon usability issue » Potential header menu "X" close-icon usability issue in Olivero
Issue tags: -Accessibility +UX

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.

mherchel’s picture

Priority: Normal » Minor
xjm’s picture

Priority: Minor » Normal
Issue tags: -UX +Accessibility, +Usability

I don't think demoting this to "minor" is correct. For any issue raised by a topic maintainer (usability or accessibility), I actually would default to major as they are related to core gates. What is the justification for downgrading this to minor?

Re-promoting to at least "normal". See the issue priority definitions for an example of what constitutes a minor bug. I am okay with using minor for things that will not be supported in 10.0 (IE11, QuickEdit), but not for actual bugs, especially bugs raised by apparently not only one but two different accessibility topic maintainers.

rainbreaw’s picture

This is not a blocker. We will leave it as "normal" priority.

What we would like as accessibility maintainers is usability testing to make sure that this is understood by users with a range of cognitive abilities.

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.

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.