Stepping back a bit, How Browser independant is this type of form
really? Would it not bee simpler and more accessible to just label
things? Just because one or two assistive technnologies can jump
through hoops to provide the information does not make it right.
Just because they are common in thee wild doesn't make theem right.
I know, we were talking about how VO dealss with forms and I can tell
you that I've use a lot of forms with a high degree of ssuccess. I
still have ttrouble though, even iin windows with forms that insist
on making me count or jump through hoops. It's not necessarry. For
instance, you could number the radio buttons so that you'd at least
have a reference.
On Aug 11, 2006, at 6:35 PM, Access Curmudgeon wrote:
It's the second set of edit fields that *sucks*
The difficulty is that it is a grid, so each of four text fields needs
to be associated with the header on the top most row and left most
column. Short of memorizing the headers, I am not sure how one can
cope with this layout using Safari and VoiceOver. With Jaws and
WindowsEyes their are table reading commands to give one context. I
think this is a bug and VoiceOver should be able to provide the same
information.
Would it be possible too label the radio buttons?
No. It is the same problem that you have the questions in the far
left column and the rating labels in the top most row. The only way
to make it easier is to repeat the rating labels every time for every
question. That shouldn't be necessary. This kind of survey layout is
not uncommon. The associations are not just visual, they are
explicitly made from the structure of the table. But I cannot get
VoiceOver to provide prompts when there are two or header cells
associated with a table data cell.
like the first set of edit fields which is well done
I think the first set of edit fields benefit from being simple. They
do not use explicit labels (LABEL FOR) but I don't think they are
really necessary.
