WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Name, Role, Value and Labels or Instructions techniques...


From: Sean Keegan
Date: Mar 29, 2015 3:06PM

> Yes, they may not be using actual <label> elements, but does
> their current markup still provide a name to those controls?

Good question and I realized that I neglected to include an example of what
I was encountering. Here is one sample in which label is not used:

a) The on-screen text says "Social Security Number" and under that text
input field there is a sample as to how the social security number should
be formatted (###-##-####).

b) The title attribute in the input field says, "Please enter your number
in the described format. To change this information after completing the
application, please check under the Settings. If you do not include this
information, you will not be able to submit for financial aid."

Because there was such a disassociation between the on-screen text and
@title, I believed this would be a 3.3.2 issue as well as 4.1.2. I should
have also reviewed 1.3.1 (thanks, Birkir, I completely bypassed that one).

So, there is @title, it just is not equating to the on-screen text, thus I
saw this as failing 4.1.2. I agree that @title could be used, but to be
conformant it would need to have the social security number and formatting
information - yes?

Admittedly, I have a slight bias towards using <label> for form fields as
this provides options for someone using speech-recognition, so I need to
get over my issues with @title when it's used properly.

Thanks all for the reference to the accessible name calculation - that's a
great help.

Take care,