search

dj091111 / google-axs-chrome

Automatically exported from code.google.com/p/google-axs-chrome
0 stars 0 forks source link

ChromeVox: creats artificial/fake tables, where there are none--algorithm is too smart #42

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Mac OS X 10.7.2 and Windows 7 x86
ChromeVox 1.16.0
Chrome 16 beta and 17 canary

Gmail.com Basic HTML (standard has some serious accessibility and usability 
issues);
ChromeVox+N, T;

Expected: ChromeVox to navigate to, read, and interact with only table, which 
is message table.
Actual: ChromeVox is creating fake/artificial tables, which don't really exist 
on the page, requiring a lot of next table keyboard commands to get to message 
table.

Regression: Yes, ChromeVox 1.1.15.0 didn't exhibit these fake/artificial tables.

Notes: ChromeVox+L, T will show about half a dozen tables, where NVDA+Firefox 
will only show one table.

Original issue reported on code.google.com by KevinCha...@gmail.com on 23 Nov 2011 at 11:18

GoogleCodeExporter commented 8 years ago 
Repro'd.

To clarify what's going on here, the ChromeVox+N+T command *is* jumping you to 
real tables - but it's not very smart and so it's simply moving to the next 
<table> element on the page.

This command *isn't* doing the tricky heuristics that we use to determine 
whether to jump into table navigation when you're navigating using 
ChromeVox+Down. (We only start table navigation if we determine that the 
<table> element is a data table and not a layout table that's being used for 
visual styling).

So these are real tables, but they're only used for visual styling. Either way, 
we probably shouldn't be jumping to them when you hit ChromeVox+N+T.

Original comment by rshea...@google.com on 30 Nov 2011 at 12:36