E-mail List Archives
Re: Unlabelled form field with adjacent button as label?
From: Birkir R. Gunnarsson
Date: Mar 4, 2015 5:49AM
- Next message: Steve Faulkner: "Re: Unlabelled form field with adjacent button as label?"
- Previous message: Patrick H. Lauke: "Re: Unlabelled form field with adjacent button as label?"
- Next message in Thread: Steve Faulkner: "Re: Unlabelled form field with adjacent button as label?"
- Previous message in Thread: Patrick H. Lauke: "Re: Unlabelled form field with adjacent button as label?"
- View all messages in this Thread
Great discussion.
I agree with Lynn in that I find the wording in the technique confusing.
Basically what the technique is saying is that an invisible label,
such as ones provided by aria-label or title (easy to implement, no
layout or design changes required), is sufficient for cases where an
input field is next to a button, visibly and in focus order.
I wish the wording of the technique was clearer on this, and it would
help eliminate any confusion.
I was somewhat confused when reading this myself, and I have dabbled
in accessibility for some time now.
I think a clearer wording would help everybody.
It should say something along the lines of
"in those cases, an invissible accessible name, provided via the
aria-label or title attribute, (see accessible name calculation) is
sufficient for the form field).
Cheers
-B
On 3/4/15, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 04/03/2015 12:12, Lynn Holdsworth wrote:
>> But isn't it hugely confusing if a success criterion for one
>> checkpoint fails on others? Presumably this one fails 4.1.2?
>
> On its own, it would fail 4.1.2. Of course, you'd then also need to look
> at making sure your form fields pass 4.1.2, which would lead you down
> the path of using a <label> element, aria-label, aria-labelledby, etc.
>
>> As a
>> developer, if I implement this success criterion, aren't I likely to
>> assume that it passes WCAG2?
>
> You'd assume wrong. Just implementing a technique that is sufficient for
> one SC does not mean it satisfies all other SCs.
>
> For instance, imagine if you added a nice visible <label>...but then
> styled it so that its color contrast is something like 1.5:1. Yes, you
> just satisfied 4.1.2, but now are failing 1.4.3.
>
> To pass WCAG2, you need to ensure all SCs are satisfied. If, as a
> developer, you just take one sufficient technique that addresses one SC
> and hope that this then automatically also satisfies all other SCs,
> you're going to have a bad time in many cases.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > >
--
Work hard. Have fun. Make history.
- Next message: Steve Faulkner: "Re: Unlabelled form field with adjacent button as label?"
- Previous message: Patrick H. Lauke: "Re: Unlabelled form field with adjacent button as label?"
- Next message in Thread: Steve Faulkner: "Re: Unlabelled form field with adjacent button as label?"
- Previous message in Thread: Patrick H. Lauke: "Re: Unlabelled form field with adjacent button as label?"
- View all messages in this Thread