WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Unlabelled form field with adjacent button as label?

for

From: Lynn Holdsworth
Date: Mar 1, 2015 9:08AM

Hi Jonathan,

Thanks for the confirmation - I fweared that was the case but hoped
I'd interpreted it incorrectly.

Yes, I understand that sufficient techniques aren't the only way. But
I wish that this particular one didn't exist, as I don't think an
adjacent button should serve as a label by itself.

Thanks again, Lynn

On 01/03/2015, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> Does this mean that the field *does* need a label of some description, and
>> that the adjacent button doesn't serve as a label by itself unless it's
>> associated somehow
>
>
>
> Lynn, my understanding is that you don't have to associate the visual label
> and the input's accessible name -- that is, you could use a title attribute
> on the input. The idea here is that you need a visual and a programmatic
> label for all input -- but there are many ways that could be solved. Using
> aria-labelledby is certainly semantically best but I don't think required.
> If you look at the checks they say:
>
>
>
> For a field and a button using this technique:
>
> 1.Check that the field and button are adjacent to one another in the
> programmatically determined reading sequence.
>
> 2.Check that the field and button are visually rendered adjacent to one
> another.
>
>
>
> The check doesn't required programmatic association other than reading
> order. In my opinion there should also be a check there to make sure the
> field has an accessible name.
>
>
>
> Also, for what it's worth sufficient techniques are not required for
> conformance - conformance can be met using other techniques as long as the
> success criteria is met.
>
>
>
> Jonathan
>
>
>
>
>
> --
>
> Jonathan Avila
>
> Chief Accessibility Officer
>
> SSB BART Group
>
> <EMAIL REMOVED>
>
>
>
> 703-637-8957 (o)
>
> Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
>
>
>
>