WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: 2.4.4 Link purpose (In context)

for

From: Birkir R. Gunnarsson
Date: Mar 7, 2020 12:50AM

With some "creative interpretation".
The success criterion requires visible labels, it doesn't say "visible
label when empty " or "visible labels when filled in", which I take to
mean the form control labels have to be visible in both states.
In other words, the visible labels have to be there when you load the
page and they also have to be there after you've filled in the text
inputs, the value of a text input is not a visible and descriptive
label for the input (2.4.6 again).

Theoretically, does it pass if visible label is only display on
hover/focus? It's up to interpretation I guess (and possibly it could
be argued that it would suffice).
I choose not to believe it. *grin*
I've seen a stronger argument in the past, I'm sure about it, but I
also fail to find it now.


On 3/6/20, Greg Jellin < <EMAIL REMOVED> > wrote:
> I realize this isn't the purpose of this discussion, so apologies for
> taking this thread on a tangent, but Birkir, you mention 3.3.2 requires
> a PERSISTENT visible label. I advise this as well, but I've yet to be
> able to identify where in 3.3.2 I can find support to enforce that as
> required. Can anyone explain how we can interpret it as required?
>
> -Greg
>
> On 3/6/2020 5:00 PM, Patrick H. Lauke wrote:
>> On 07/03/2020 00:00, Birkir R. Gunnarsson wrote:
>>> Yes, 3.3.2 requires that a form control has a persistent visible label
>>> (no, it can't be labeled by placeholder text alone), any label passes
>>> 3.3.2, 2.4.6 requires that the label describes topic/purpose.
>>> 2.4.6 does not say that the label has to uniquely describe topic pr
>>> purpose, so "delete" or "read more" seem to be sufficient, at least on
>>> the surface, even if you really want users to be able to clearly
>>> distinguish between multiple "delete" buttons on the same page, or at
>>> least be damn sure what they are deleting (3.3.4 comes into play here,
>>> to some extent, if the deletion affects user data or financial info).
>>
>> I've recently pondered if having various "delete", "read more" etc
>> buttons (not links) that are visually clearly related to something but
>> lack any other association/hint in their accessible name may be
>> failing 1.3.1 Info and Relationships. Seems a reasonable SC to hang a
>> failure against.
>>
>> P
> > > > >


--
Work hard. Have fun. Make history.