Skip to content

Remove noninteractive class from navigation

Austin Regnery requested to merge aregnery/drop-noninteractive-class into master

What does this MR do and why?

The noninteractive class was introduced to elements in the navigation in !128712 (merged) to make tooltips less cumbersome, but this fails an accessibility criterion. This is important because a mouse pointer size can be increased and block what is in the tooltip from view.

Understanding SC 1.4.13: Content on Hover or Focus (Level AA) Success Criterion (SC) Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

Dismissible
A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;

❌ Hoverable
If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;

Persistent
The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

Screenshots or screen recordings

Before After
Before__1_ After__1_

How to set up and validate locally

Hover over buttons in the navigation sidebar. The tooltips should be able to be interacted with.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Austin Regnery

Merge request reports