Closed
Bug 1370712
Opened 7 years ago
Closed 7 years ago
Scroll bar functionality with touch screen is disabled when NVDA screenreader is active
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: u554753, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0 NVDA Version: 2017.2 Steps to Reproduce: 1. Go to http://oaa-accessibility.org/example/1 or any website with significant amount of content 2. Use the scroll bars with finger. Expected Result: Firefox Nightly functions/scrolls normally. Actual Result: Nothing happens. Closing NVDA screenreader restores lost functionality.
Comment 1•7 years ago
|
||
This is expected, because NVDA provides its own touch screenn support gestures so blind people can use it. Closing as INVALID.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
The scrolling works with the stylus, but not with finger on the Surface Pro 4. Are there any STR you can suggest to enable touch screen support gestures that we might be missing?
Status: RESOLVED → REOPENED
Flags: needinfo?(mzehe)
Resolution: INVALID → ---
status-firefox55:
--- → affected
status-firefox57:
--- → affected
Comment 3•7 years ago
|
||
Finger scrolling doesn't work with NVDA on Acer Aspire SW3-013 either.
Comment 4•7 years ago
|
||
As noted by Marco in comment 1: > This is expected, because NVDA provides its own touch screenn support gestures so blind people can use it. It's not possible for a blind user to use normal touch screen gestures, since tapping the screen would activate items without the user being able to inspect them. Thus, NVDA "takes over" the touch screen and provides its own gestures. This is expected behaviour and there is currently no way to override it.
Updated•7 years ago
|
Flags: needinfo?(mzehe)
Updated•7 years ago
|
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → INVALID
Comment 5•7 years ago
|
||
See comment #1 and comment #4 why this was closed as invalid.
You need to log in
before you can comment on or make changes to this bug.
Description
•