Open
Bug 1700872
Opened 3 years ago
Updated 11 months ago
Search bar - skipped in Overflow menu if menu is opened via keyboard Arrows
Categories
(Firefox :: Search, defect, P5)
Tracking
()
NEW
Accessibility Severity | s3 |
People
(Reporter: cfogel, Unassigned)
Details
(Keywords: access)
Attachments
(1 file)
99.84 KB,
image/gif
|
Details |
Affected versions
- 88.0a1(2021-03-24), 88.0b1, 87.0;
Affected platforms
- Windows 10, macOS 10.15;
Steps to reproduce
- Launch Firefox, access the Customize page;
- Drag the Search bar and some buttons in the Overflow menu;
- Close the Customize page;
- With the TAB-key press it until reaching the toolbar buttons;
- Press the Right-arrow key to reach the Overflow menu;
- Press the Enter key to open the menu;
- Press the Down-arrow key to navigate inside the menu;
Expected result
- each element is selected, navigation goes as expected;
Actual result
- Search bar is skipped;
Regression range
- considered "good" the prior implementation which the SearchBox was selected but the focus was locked to actions inside it:
- First bad: 2019-04-15;
- Last "good": 2019-04-14
- Pushlog: URL;
Additional notes
- attached recording to best illustrate the issue;
- reproducible with Proton prefs both true/false;
- while this is a workaround from the previous variation, there would be an enhancement here on which IF the Search bar is empty [Down-Arrow] keyboard navigation to go through and select the next element from the menu; this as opposed to the current implementation in which with keyboard navigation the TAB key is needed to reach the Search box.
Reporter | ||
Updated•3 years ago
|
Has STR: --- → yes
Updated•3 years ago
|
Whiteboard: [access-s3]
Comment 1•2 years ago
|
||
The severity field for this bug is set to S4. However, the accessibility severity is higher, [access-s3].
:standard8, could you consider increasing the severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(standard8)
Updated•2 years ago
|
Severity: S4 → S3
Flags: needinfo?(standard8)
Updated•11 months ago
|
Accessibility Severity: --- → s3
Whiteboard: [access-s3]
You need to log in
before you can comment on or make changes to this bug.
Description
•