MSHTML: Hidden content inside button elements incorrectly rendered in browse mode

[nvaccessAuto]

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 of display:none and aria-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

[nvaccessAuto]

Attachment log01132014.txt added by dhezl on 2014-01-13 20:50
Description:
NVDA log file

[nvaccessAuto]

Comment 2 by jteh on 2014-01-13 22:51
I'm unclear as to exactly what you're referring to. Please provide a simple test case, the behaviour you are seeing and the behaviour you expect. Please also specify what browser(s) you are testing with. Thanks.

[nvaccessAuto]

Comment 3 by dhezl on 2014-01-13 23:09
Of course!

The simplest case is as in the following:

<button>
    <div style="display: none" aria-hidden="true">STATE 1</div>
    <div style="display: block" aria-hidden="false">STATE 2</div>
</button>

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:

Button STATE 1
Button STATE 2

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.

[nvaccessAuto]

Comment 4 by jteh on 2014-01-13 23:19
I can't reproduce this in either Firefox nightly or Chrome Canary. NVDA only reads the STATE 2 portion.

I can confirm it in IE 11, which is very odd.

[nvaccessAuto]

Comment 5 by jteh on 2014-01-13 23:26
We're using the name of the button as reported by Internet Explorer's accessibility implementation. Unfortunately, it seems that IE doesn't bother to remove hidden content in this case, so we'll need yet another hacky work around.

[nvaccessAuto]

Comment 7 by jteh on 2014-07-08 23:39
Changes:
Changed title from "Buttons with multiple states not supported" to "MSHTML: Hidden content inside button elements incorrectly rendered in browse mode"

[nvaccessAuto]

Comment 8 by Michael Curran <mick@... on 2015-01-22 23:52
In [19c7b38]:

Merge branch 't3776' into next. Incubates #3776

Changes:
Added labels: incubating

[nvaccessAuto]

Comment 9 by Michael Curran <mick@... on 2015-02-05 00:23
In [6533c6b]:

Merge branch 't3776'. Fixes #3776

Changes:
Removed labels: incubating
State: closed

[nvaccessAuto]

Comment 10 by mdcurran on 2015-02-05 00:24
Changes:
Milestone changed from None to 2015.1