W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2019

Some discussion points for Label in Name

From: Michael Gower <michael.gower@ca.ibm.com>
Date: Mon, 21 Jan 2019 22:51:38 +0000
To: WCAG <w3c-wai-gl@w3.org>
Message-Id: <OF5AAFE382.8A571116-ON88258389.007B922B-88258389.007D9402@notes.na.collabserv.com>
"Success Criterion 2.5.3 Label in Name (Level A): For user interface 
components with labels that include text or images of text, the name
 contains the text that is presented visually."
Time permitting, here are some topics I'd like to delve into on our next 
call in relation to 2.5.3 Label in Name.

Problem 1: When we ignore the programmatic stuff, getting agreement on 
what exactly constitutes a 'label' for a component isn't always simple.

Problem 2: The Accessible Name Rec has a specific method for determining 
name. It affects implementation, especially when you try to satisfy 
various interpretations of what IS a label. (Key considerations: group 
role not in calculation, aria-label/labelledby have priority in 
calculation, aria-describedy not calculated)

Problem 3: It is harder than anticipated to balance the needs of screen 
reader users with the needs of speech recognition.

Five examples. What is the label for each UI Component (or does it have 
one)?













Michael Gower
Senior Consultant
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
cellular: (250) 661-0098 *  fax: (250) 220-8034


picture
(image/gif attachment: 01-part)

picture
(image/gif attachment: 02-part)

picture
(image/gif attachment: 03-part)

picture
(image/gif attachment: 04-part)

picture
(image/gif attachment: 05-part)

Received on Monday, 21 January 2019 22:52:08 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:29 UTC