Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

role=presentation dont work in IE8-9-10-11 #3713

Closed
nvaccessAuto opened this Issue Dec 12, 2013 · 5 comments

Comments

Projects
None yet
1 participant

Reported by tutej on 2013-12-12 14:45
Hello,
I've noticed that NVDA don't work properly anymore with role=presentation attribute.

The attached code is connected with another ticket :

http://community.nvda-project.org/ticket/3711#comment:2

The functions of elements are the same.

In attached is simple code to explain the situation.
Styles are neglible, if disabled - nothing changes.

It's GWT aplication.

Attachment NewFile.html added by tutej on 2013-12-12 14:46
Description:

Comment 1 by Michael Curran <mick@... on 2013-12-16 10:03
In [0dac6b5]:

Merge branch 't3713' into next. Incubates #3713

Changes:
Added labels: incubating

Comment 2 by mdcurran on 2013-12-16 10:07
Hopefully this has been implemented write in the above commit. You can try it in the next available 'next' snapshot. However I must confirm though: you are talking about role=presentation on the tables? NVDA treets the tables in your testcase as layout tables. You wouldn't have noticed them at all unless you'd explicitly turned on include layout tables in the browse mode settings dialog. This is okay to do of course, but its certainly not the standard config for most people. Just checking in case I'm miss-understanding your testcase. Now NVDA should be no longer announcing tables or any container with role presentation.

Comment 3 by Michael Curran <mick@... on 2014-01-06 07:23
In [5d88d89]:

Merge branch 't3713'. Fixes #3713

Changes:
Removed labels: incubating
State: closed

Comment 4 by mdcurran on 2014-01-06 07:33
Changes:
Milestone changed from None to 2014.1

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the 2014.1 milestone Nov 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment