WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Best practices for identifying forms and their fields

for

From: Dave Merrill
Date: May 6, 2013 2:41PM

Related, is it considered bad accessibility practice to have controls that
aren't inside a form? Modern scripted interactions sometimes don't need
one, since they either don't post to a server at all, or do so via Ajax.

It would seem not to be required, if the form itself isn't really seen by
readers, so its purpose has to be stated as readable text.

Thanks,
Dave Merrill


On Mon, May 6, 2013 at 4:13 PM, Roger Hudson < <EMAIL REMOVED> >wrote:

> Hi
>
> While I agree an explicitly associate label is always the preferable way
> identify form controls this may not always be possible. I have been testing
> (or asking others to test) the use of the title attribute with different
> screen readers and browsers on and off since 2008, and have found it to be
> well supported. My recent article "Accessible Forms 1: Labels and
> identification"
> (
> http://usability.com.au/2013/04/accessible-forms-1-labels-and-identificatio
> n/) contains a video showing text input and select input in an imaginary
> order form being identified with the title attribute (NVDA and Firefox).
> Also a table summarising how it is supported by four different screen
> readers.
>
> Best wishes,
> Roger
>
>