[A11y_Bug]: Issue type counts should not be in tab order / clickable

[philljenkins]

Project

extension-checker

Browser

Chrome

Operating System

MacOS

Automated testing tool and ruleset

No response

Assistive technology

Keyboard

Description

The keyboard tab stops on the issue type/icon counts,
as if to say they are interactive, but they are not.
Pressing enter/space only shows the tooltip, confusing the keyboard user that there is some other action available because the tab stopped there. The tooltip should show when t receives keyboard focus, without needing to pres space/enter to show it. However, in this case, they shouldn't be in the tab order at all.

Steps to reproduce

1. Open Checker
2. Tab until focus arrives on 'issue type/icons' with counts

[marcjohlic]

Discussion with Marc, Tom, Mike, Josiah & Marnie - decision is to just remove the Definition ToolTip completely from these icons as we already have affordances for these in the QuickGuide, User Guide, and Issues Panel.

Action: Remove Definition ToolTip from these icons.

This can be worked on in conjunction with #1830 toobar reflow issue

[philljenkins]

@drjoho
JAWS 2024 currently reads the controls as follows, which is not correct.
Not using the tab key to navigate, but using the right arrow keys to reads the UI:
after scanning AltoroMutual
...

• "Keyboard Checker Mode button - to activate press enter"
• "Violation button collapsed - to activate press enter"
• pressing Enter, JAWS says "expanded" and nothing else
• continuing with right arrow key, JAWS will read the numbers one at a time, and then spell out "Violations" one letter at a time.
• continuing instead with down arrow key, JAWS will correctly read the "blank", then "Violations" as a word, not character by character, but then reads (incorrectly) the number followed by a bunch of other numbers, control names, and states (collapsed).

I can check with JAWS again when you have a new PR/Action artifact. I did this testing with the latest PR 1820.

[drjoho]

Deemed fixed in new UI