MSHTML: Hidden content inside button elements incorrectly rendered in browse mode #3776
Comments
Attachment log01132014.txt added by dhezl on 2014-01-13 20:50 |
Comment 2 by jteh on 2014-01-13 22:51 |
Comment 3 by dhezl on 2014-01-13 23:09 The simplest case is as in the following:
In the above example, only "STATE 2" visibly shows on the page. Other AT tested will only read the second state in the above example. However, NVDA will read the following:
This was tested in IE8, IE9, IE10, IE11, and Chrome on Windows 7. Thanks for the fast reply! Really appreciate what you guys are doing here. |
Comment 4 by jteh on 2014-01-13 23:19 I can confirm it in IE 11, which is very odd. |
Comment 5 by jteh on 2014-01-13 23:26 |
Comment 7 by jteh on 2014-07-08 23:39 |
Comment 8 by Michael Curran <mick@... on 2015-01-22 23:52
Changes:
|
Comment 9 by Michael Curran <mick@... on 2015-02-05 00:23
Changes:
|
Comment 10 by mdcurran on 2015-02-05 00:24 |
Reported by dhezl on 2014-01-13 20:50
<button>
elements that contain multiple nested<div>
elements for purposes of managing display state fail when read by NVDA, resulting in all button states being read in sequence. Use ofdisplay:none
andaria-hidden="true"
within the nested elements, while functioning properly in all other tested AT (JAWS, VoiceOver, ChromeVox), is ignored by NVDA.Please add support for these tags on content nested within
<button>
elements and other form inputs to be more inline with other AT and prevent necessitation of multiple event handlers for what should be possible to accomplish with a single page element.Thank you!
Blocking #4250
The text was updated successfully, but these errors were encountered: