WThis obviously focuses on window eyes and jaws and section 508.
ยง508 1194.22(n) references the behavior assistive technology, so yes, some particular brand has to stand in for that, and Jaws and Window Eyes have been the most commonly used bench mark for five year now.
That table of edit fields though is bunk.
It is not uncommon to encounter in the wild. There are no credible authorities that advocate avoiding the construct altogether. Opinion varies on how to make construct it in an accessible fashion. The most popular strategy, using redundant title attributes, works only for Jaws and maybe Home Page Reader. Window Eyes ignores title attributes, but it honors data table headers, even on form elements.
When we see single edit fields, not the ones with text in them although they work too, the labels show up where they should.
I am not of the opinion that everything should have to be linearized to serve the lowest common denominator. I am disappointed that VoiceOver is so limited with properly constructed data tables.
When we have test cases for mozilla and safari,
We have test cases for Safari
we'll have a wider field to work with.
It seems to me that the limitation is not with the browser, but the screen reader.
Yes, the technology is not sufficiently developpedd in safaari,
If by safaari you mean VoiceOver, then yes, I agree.
but I could not even get throughh the page without loosing my place
Using VoiceOver, neither could I.
because it is clearly targetted at IE.
No, the form is clearly targeted to be valid and accessible html. Using the title attribute on form elements is a technique that caters to Jaws on IE, but that is not what posted. It is a reasonable expectation that a screen reader would readily expose header cells when navigating data tables. In a similar vane, a screen reader user should be able to navigate straight down a column when in a data table. It is not credible to assert that this a prejudice perspective favoring IE or Jaws.
