WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: using title attribute as form field label

for

From: GILLENWATER, ZOE M
Date: Nov 8, 2011 7:45AM

Thanks Vincent, that's a consideration with the title attribute I hadn't thought of.

Zoe

Zoe Gillenwater
Technical Architect, Design Standards Accessibility
Creative Experience Team
AT&T eCommerce

o:  919-241-4083
e:   <EMAIL REMOVED>

This e-mail, and any attachments, are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. It is the property of AT&T. If you are not the intended recipient of this email, you are hereby notified that any dissemination, distribution or copying of this email, any attachments thereto, and any use of the information contained is strictly prohibited. If you have received this email in error, please notify me at 919-241-4083 and permanently delete the original and any copy thereof.


-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Vincent Young
Sent: Monday, November 07, 2011 5:14 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] using title attribute as form field label

> In other words, are there any advantages of these CSS or ARIA techniques
over simply using the title attribute that I should be aware of?

Zoe, one situation I can think of is when you have interested parties that
do not want the title showing up on hover (for whatever reason). I've run
into this more on the private more than public sector. For me, the
particular form and situation dictated what was most appropriate. Often,
I'm not able to do what I really want to and have to get a bit creative.
For example labels inside input. Would like to use an actual label as the
visual value (
http://www.alistapart.com/articles/makingcompactformsmoreaccessible/), but
project constraints do not allow this or title, so I might do some CSS
hiding. I'm a traditionalist as you are when it comes to forms and try to
use labels and title where appropriate. Forms can get complicated so
aria-labelledby, aria-desscribedby, CSS, etc. have their place.


On Mon, Nov 7, 2011 at 1:50 PM, GILLENWATER, ZOE M < <EMAIL REMOVED> > wrote:

> Hi everyone,
>
> I know and preach that it's best to use a label for every form field, but
> in those cases where it's really not possible or practical (such as one
> label describing more than one field), what's the best alternative
> technique? Title attribute? Always, or just in some situations?
>
> Using the title attribute on the form field has good support and is simple
> to implement. In fact, is there any reason to even consider other
> techniques, such as using CSS to hide a label or using aria-labelledby? In
> other words, are there any advantages of these CSS or ARIA techniques over
> simply using the title attribute that I should be aware of?
>
> Thanks,
> Zoe
>
> Zoe Gillenwater
> Technical Architect, Design Standards Accessibility
> Creative Experience Team
> AT&T eCommerce
>
> o: 919-241-4083
> e: <EMAIL REMOVED>
>
> This e-mail, and any attachments, are intended only for use by the
> addressee(s) named herein and may contain legally privileged and/or
> confidential information. It is the property of AT&T. If you are not the
> intended recipient of this email, you are hereby notified that any
> dissemination, distribution or copying of this email, any attachments
> thereto, and any use of the information contained is strictly prohibited.
> If you have received this email in error, please notify me at 919-241-4083and permanently delete the original and any copy thereof.
>
>
>
>