Re: Use of pre-compilated text-fields in forms

sorry, message was sent beffore done.

It is my understanding that valid html at some level for  
accessibility is to use text in the forms.  It's broader than a  
bbraille and not braille issue.  Now, if I could gett my user agent  
to mark the fields with text for me so that my small screen would  
recognize or my audio or braille output device, we could retire this  
checkpoint with gusto.  This gets complicated though and I'm thinking  
of the still rather large numbers of people using technology which  
simply does not recognize or report to the user an edit field.  Just  
because a user agent or user agent at combination or two does, does  
not mean the issue is solved.

On May 9, 2006, at 7:11 AM, Alastair Campbell wrote:


> Puting in an x or a word or two which if left in would return an
> invalid entry message would be the solution.

So people enter 5x instead? (For example.)

I don't consider that a good solution, as people then have to go through
the form again.

We have a conflict here of people using screen readers versus people on
Braille displays. (There are probably exceptions on both sides, but in
general there isn't a clear solution.)

When you have this, surely the best/easiest option for the general
populace should win out? In that way even sites which have no regard for
accessibility aren't tripping up on this checkpoint, and everyone is
following the same (defacto) method.

I just don't see the advantage for anyone in catering for a user agent
that doesn't understand basic HTML.

Kind regards,

-Alastair

--
Alastair Campbell         |  Director of User Experience

Nomensa Email Disclaimer:
http://www.nomensa.com/email-disclaimer.html

Received on Tuesday, 9 May 2006 11:22:53 UTC