You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Navigate with the keyboard to the "+ New URI" button, and activate it
Same, but with the "+ New custom field" button
Expected Result
Once the "+ New URI" button is activated, the new input field appears. Focus is moved programmatically to the new input field.
Same for "+ New custom field" - two new inputs (Name and Value) appear. Focus is moved programmatically to the "Name" field.
Actual Result
The new input(s) appear, but focus remains on the "+ New URI" / "+ New custom field" button. No hint is given to screen reader users that anything actually happened. As the new fields are inserted before the "+ ..." buttons, a user has to navigate in reverse (Shift+Tab) to reach them (assuming they know that anything actually happened).
Screenshots or Videos
bitwarden-desktop-add-new-focus-order.mp4
Video: Windows/NVDA, triggering the "+ New URI" button, no announcement is made, then having to Shift+Tab to reach the new field. Same for the "+ New custom field" - here even more annoying, as when using Shift+Tab the user first encounters the Value field, so they need to reverse-navigate once more to reach the Name field.
Additional Context
Once these "+ ..." buttons are triggered, move .focus() to the first newly shown input. This will then also take care of announcing to screen readers that something actually happened, as the new input will be announced.
Operating System
Windows
Operating System Version
11
Installation method
Direct Download (from bitwarden.com)
Build Version
2024.12.1
Issue Tracking Info
I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Thank you for your report. I have flagged this to the Engineering department; please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.
Steps To Reproduce
Expected Result
Once the "+ New URI" button is activated, the new input field appears. Focus is moved programmatically to the new input field.
Same for "+ New custom field" - two new inputs (Name and Value) appear. Focus is moved programmatically to the "Name" field.
Actual Result
The new input(s) appear, but focus remains on the "+ New URI" / "+ New custom field" button. No hint is given to screen reader users that anything actually happened. As the new fields are inserted before the "+ ..." buttons, a user has to navigate in reverse (
Shift+Tab
) to reach them (assuming they know that anything actually happened).Screenshots or Videos
bitwarden-desktop-add-new-focus-order.mp4
Video: Windows/NVDA, triggering the "+ New URI" button, no announcement is made, then having to
Shift+Tab
to reach the new field. Same for the "+ New custom field" - here even more annoying, as when usingShift+Tab
the user first encounters the Value field, so they need to reverse-navigate once more to reach the Name field.Additional Context
Once these "+ ..." buttons are triggered, move
.focus()
to the first newly shown input. This will then also take care of announcing to screen readers that something actually happened, as the new input will be announced.Operating System
Windows
Operating System Version
11
Installation method
Direct Download (from bitwarden.com)
Build Version
2024.12.1
Issue Tracking Info
The text was updated successfully, but these errors were encountered: