Closed
Bug 1035462
Opened 11 years ago
Closed 6 years ago
[a11y] Placing focus on an ARTICLE element does not read its contents by the NVDA screenreader
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: patrickfox, Unassigned)
Details
(Keywords: access)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36
Steps to reproduce:
In Windows 7, using NVDA 2014.2 with FF v30, I placed focus on an ARTICLE element - here's an example/test page: http://jsfiddle.net/pfox/92RWG/show/light/
Actual results:
Focus is placed correctly, but the contents of the ARTICLE are not read.
Expected results:
The contents of the ARTICLE should be read, just as the contents are read using the other container elements in the example.There's something different about the ARTICLE tag - I can't think of any reason for it to be treated differently.
| Reporter | ||
Updated•11 years ago
|
OS: Mac OS X → Windows 7
Hardware: x86 → x86_64
Updated•11 years ago
|
Component: Untriaged → General
Keywords: access
Summary: [a11y] Placing focus on an ARTICLE element does not read its contents → [a11y] Placing focus on an ARTICLE element does not read its contents by the NVDA screenreader
Comment 1•9 years ago
|
||
Given the age of this bug, it doesn't sound specific to e10s.
No longer blocks: 1258839
Comment 2•6 years ago
|
||
The reason is that the article element gets a role of document, which NVDA ignores for focus events in browse mode. This role mapping complies with the spec. (I'd argue that mapping is misguided, but that's something that needs to be addressed at the spec level.) Regardless, this is not a bug in Firefox.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•