Closed Bug 1363881 Opened 7 years ago Closed 7 years ago

JAWS Screenreader does not read output when navigated with arrow keys

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Version:
55 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: u554753, Unassigned)

References

(Blocks 2 open bugs)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
JAWS Version: 18.0.2738

Steps to Reproduce:
1. Open http://www.wikipedia.org/ or relevant website
2. Navigate to an article 
3. Press tab key and observe behavior
4. Press arrow keys and observe behavior of the screenreader


This happens regardless of whether or not e10s is active.
Might be related to Bug 1006185.
Is this a regression? Or is this a result of testing of e10s support for a11y?

Either way, I expect this is a core bug, not a frontend one.
Component: Disability Access → Disability Access APIs
Flags: needinfo?(gwimberly)
Product: Firefox → Core
e10s support for a11y. Misclicked the component.
Flags: needinfo?(gwimberly)
Bug 1353554 is preventing me from testing this further.
Depends on: 1353554
Flags: needinfo?(jmathies)
Flags: needinfo?(jmathies)
Flags: needinfo?(gwimberly)
This seems to work in e10s and non-e10s mode.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(gwimberly)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.