WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Trying to Understand 2.5.3

for

From: Jonathan Avila
Date: Sep 3, 2019 9:41AM

> 1. Does aria-labelledby have to be used even on <label>?

Hi JP, SC 2.5.3 is not aimed at this. The goal of label in name is to make sure the visible label text (however it is displayed visually) is included in the accessible name that is provided on interactive controls including inputs and button (however it is provided).

Jonathan

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of JP Jamous
Sent: Tuesday, September 3, 2019 11:31 AM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: [WebAIM] Trying to Understand 2.5.3

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Hi folks,



As I am reading WCAG 2.1, I am really struggling with 2.5.3 Label in Name.
Here are the questions I have.



1. Does aria-labelledby have to be used even on <label>?
2. Does this success criterion suggest that we have to add alt and
title attributes to any HTML element? I had developers in the past use alt attributes on an anchor tag, which is improper markup.
3. Does 2.5.3 target elements that are divs and spans by ensuring that
they have a role and aria-label with the visible text embedded?





I think what I am lacking to understand this success criterion is some markup to go along with it. Any help will be much appreciated.







--------------------

JP Jamous

Senior Digital Accessibility Engineer

<mailto: <EMAIL REMOVED> > E-Mail Me | <http://linkedin.com/in/JPJamous>; Join My LinkedIn Network

--------------------