Issue metadata
Sign in to add a comment
|
Screen readers not reading angular bootstrap datepicker
Reported by
dado.klj...@gmail.com,
Mar 8 2017
|
||||||||||||||||||||||
Issue description
Chrome Version : 56.0.2924.87
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
IE 11:OK
What steps will reproduce the problem?
1.Go to http://angular-ui.github.io/bootstrap/#!#datepickerPopup
2.Navigate to datepicker popup, and use keyboard to select date.
3.Dates are not announced to user with ChromeVox
What is the expected result?
While using the datepicker with keyboard the date selections should be announced by Chromevox. Using IE11 and Jaws the date selections are announced but not on Chrome using Chromevox.
What happens instead of that?
The Chromevox is mute.
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
,
Mar 9 2017
,
Mar 10 2017
Able to reproduce this issue on Mac 10.12.3, Win-10 and Ubuntu 14.04 using chrome reported version #56.0.2924.87 and latest canary #59.0.3036.0. This is a non-regression issue as it is observed from M50 old builds. From M45 and older builds,when selected datepicker popup, the chromevox stayed mute. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Mar 10 2017
Assigning to dmazzoni@ for chromevox triage.
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 4 2017
,
Aug 4 2017
,
Aug 9 2017
Still looking into this but one thing about the widget is odd -- it doesn't make sense to set the aria-activedescendant for the container datepicker widget if you're also putting actual focus on the individual date. It's either one or the other.
,
Aug 9 2017
Another problematic thing is that every time an arrow key is pressed, a lot of the markup is rewritten. It's good to have a stable DOM subtree and move focus or activedescendant around tat.
,
Aug 9 2017
Only rewriting content that actually changes should improve results and also performance. It's pretty slow when all the nodes keep getting destroyed and recreated. This leads to a lot of work in the accessibility implementation.
,
Aug 9 2017
Changing the summary as this affects NVDA as well.
,
Aug 9 2017
Also does not work with NVDA + Firefox.
,
Aug 9 2017
Marking WONTFIX since the implementation has clear issues. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dado.klj...@gmail.com
, Mar 8 2017