On Aug 16, 2006, at 9:30 PM, Access Curmudgeon wrote:
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.
And I maintain that the forms section of the standard was written with windows and IE in mind. Accessible means I can use it with a heavy browser at least. How would you use forms like this on the phone? I know they'd have to be heavily reworked before being sent over the wire. It is *safari* and not Voice Over which is at issue here though for unlike msaa and bolted on apps, It is a good deal the responsibility of the app to provide the information to the screen reader and Safari does not expose the information to Voice Over even if it were prepared to use it. If this were the case, we would be able to use the table commands available in Voice Over with safari.
A form is not a data table it is a layout table if it is a table at all. The wild has lots of bad stuff in it. I agree that information should not be coded in liniar fashion but there should be ways to code which allow it not to be liniarized and still functional in a liniar way. O wonder how .31 would play here? Why not come up with a way to code a form which meets the standards and is as accessible as possible to all?
