Skip to main content

Search and Top Navigation

#10407 open bug ()

Opened July 25, 2014 10:42PM UTC

Last modified May 03, 2017 01:01PM UTC

Selectmenu: inaccessible in IE when screen reader is active

Reported by: dasjestyr Owned by:
Priority: minor Milestone: none
Component: ui.selectmenu Version: 1.11.0
Keywords: accessibility Cc:
Blocked by: Blocking:

Observed in IE 11, while screen reader is running, the combobox cannot be expanded nor indexed. Confirmed using current versions of NVDA and JAWS

Attachments (0)
Change History (7)

Changed July 25, 2014 11:40PM UTC by scottgonzalez comment:1

component: ui.coreui.selectmenu

Changed July 26, 2014 12:19PM UTC by tj.vantoll comment:2

status: newopen
summary: Selectmenu inaccessible in IE when screen reader is activeSelectmenu: inaccessible in IE when screen reader is active

Confirmed with JAWS on The space bar and up/down arrows do nothing when JAWS is active for some reason.

Changed July 31, 2014 09:32AM UTC by fnagel comment:3

Thanks for reporting.

We're having some other a11y edge case issues and currently working on that.

Changed March 22, 2015 08:28PM UTC by joshgrossnz comment:4

Has there been any progress on this? I've noticed the same issue, using NVDA and IE11.

Interestingly enough, NVDA can read the selectmenu fine if the selectmenu is inside an iframe.

For example, if you look at this page with NVDA, it can read the selectmenu:

That page contains an iframe, which has the actual selectmenu. If you go directly to the page with the selectmenu and try it there, NVDA can't read it:

I've recreated this by creating two dummy pages on my local environment - the first page has a selectmenu, and the second page has an iframe that includes the first page. As above, NVDA can read the selectmenu on the second page, but not the first page.

Probably the first time I've come across a screenreader that can read things inside an iframe easier than things outside an iframe - you'd think it would be the other way around. :)

Changed May 26, 2015 05:39PM UTC by ftrujillojr comment:5

Has there been any progress or fix for this? Change the jsfiddle from jQuery 1.10.1 to anything else and it does not work.

Changed May 26, 2015 05:52PM UTC by scottgonzalez comment:6

When there is progress, the ticket will be updated.

Changed May 03, 2017 01:01PM UTC by scottgonzalez comment:7

keywords: → accessibility