Closed
Bug 1846586
Opened 2 years ago
Closed 2 years ago
[Win] Each link on the FirefoxView-Next is focused and announced as 3 different links by NVDA
Categories
(Firefox :: Firefox View, defect, P3)
Tracking
()
RESOLVED
FIXED
| Accessibility Severity | s3 |
People
(Reporter: ayeddi, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: access, Whiteboard: [fidefe-firefox-view])
Attachments
(1 file)
|
139.12 KB,
image/png
|
Details |
set browser.tabs.firefox-view-next to true and ensure a screen reader (i.e. NVDA) is running
STR:
- With NVDA running, navigate to
View allusing the keyboard (Tab) - Navigate through the list of links in the browsing mode (by pressing
Down Arrowonly / bug 1846572)
Expected:
- Each link is focused and announced as one unified entity:
{title}, {URL}, {time}, link
Actual:
- The default screen reader arrow navigation reads each column within each link individually:
{title}, link>{URL}, link>{time}, linkwhich makes them sound like 3 different links, instead of one unified link.- This creates additional cognitive load for a user especially when arrow navigation in browsing mode is the only way to access controls within the list.
This issue may be resolved when keyboard navigation with the screen reader is fixed in bug 1846572
| Reporter | ||
Updated•2 years ago
|
Summary: [Win] When returning to FirefoxView-Next tab with NVDA, the keyboard focus is different from the programmatic focus → [Win] Each link on the FirefoxView-Next is focused and announced as 3 different links by NVDA
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P3
Updated•2 years ago
|
Whiteboard: [fidefe-firefox-view]
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Hi Anna, are you still seeing this issue or has it been fixed by bug 1846572?
Flags: needinfo?(ayeddi)
Comment 2•2 years ago
|
||
Kelly took a look at this bug and was unable to reproduce on Windows.
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(ayeddi)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•