Re: Please help with Safari on forms

[David Poehlman]

Device independance comes to mind.  Perhaps that clears up my  
accessible assertion?  It's already been said that other browsers  
have trouble with the construct.  Safari needs to pass the info on to  
VO as other apps can and do.  VO is not developped around apps.  A  
data table is a structured data set.  A form is an interactive  
mechanism.  Thus, putting a form in a table is for visual purposes.

My only solution for your set of radio buttons is to either make  
certain they are labeled in such a way as to allow a VO user to find  
the labels easily with normal nav or to change them to dropdowns.  To  
make the radio buttons useful, only a number for each would be  
required in order to track positioning.  The scale then would be  
trackable without the need to count.  As there are so few for each  
group, counting in this instance is not a huge issue unless you cary  
a heavy load or get lost easily or loose your place or your attention  
is drawn away momentarily.  This is from a user perspective.  There  
are no claims here of complete correctness nor is there any  
substancce of value from a programatic perspective.