Open alexlehner86 opened 3 years ago
Alexander Lehner wrote:
When navigating the content in the layout table with NVDA, the screen reader announces the content as a table element. This can be confusing for screen reader users as the content does not represent a data table.
What happens if you turn off the "include layout tables" option under NVDA's browse mode settings? (NVDA+ctrl+b, alt+a, space, enter)
I believe that setting is meant to resolve this issue.
Although, whether on or off, I'm not sure you should be seeing different results in Firefox and Chromium browsers, so that may still be a bug, even if the option helps.
NVDA version: 2020.3
Please, when submitting reports, test with the latest stable version, which in this case is 2020.4. You might also try the currently published beta, if any, which in this case is 2021.1beta1.
Thank you for the quick reply. I updated my installed NVDA application to 2020.4 and checked the "include layout tables" option. It was already disabled. I've repeated the tests with Chrome, Edge and Firefox and the results are the same as described in my initial post.
I don' think this should be excluded from tables rendering in NVDA. This might break lots of examples where this should be treated like a table. Note for example this post, even though it is recommended to use
Steps to reproduce:
Actual behavior:
When navigating the content in the layout table with NVDA, the screen reader announces the content as a table element. This can be confusing for screen reader users as the content does not represent a data table.
Expected behavior:
As far as I know, “display: table” was specifically created to allow web developers to design a table layout without defining the content as a table semantically. My proposal would be: NVDA should only present content as a table if the HTML table element or role=”table” is used.
When using NVDA with Firefox browser, content with "display: table" is already not announced as a table. This is also the information presented by the Accessibility Inspector feature of Firefox Dev Tools (see screenshot 2 at the end of the post). According to the accessibility inspector, the div container with “display: table” has the role “section”, not “table”. So this is another indication that “display: table” should not be interpreted as having semantic meaning.
System configuration
NVDA installed/portable/running from source:
NVDA is installed
NVDA version:
2020.3
Windows version:
Microsoft Windows 10 Enterprise, Version 10.0.19042 Build 19042
Name and version of other software in use when reproducing the issue:
The issue ocurred with Google Chrome Version 90.0.4430.212 and Microsoft Edge Version 91.0.864.37. In Firefox 87.0 the issue did not occur.
Other information about your system:
not relevant
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Did not try
Screenshots