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
Comment #2
proeungComment #3
mherchelComment #5
mherchelComment #6
xjmI 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.
Comment #7
rainbreaw commentedThis 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.