- From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
- Date: Mon, 14 Jan 2019 16:35:22 +0000
- To: "Gunderson, Jon R" <jongund@illinois.edu>, ARIA Group <public-aria@w3.org>
- Message-ID: <SN6PR03MB4383A16A21ACC4D29639C9A6F2800@SN6PR03MB4383.namprd03.prod.outlook.com>
Hi, Yes, I would expect this to be the case, where the label role would have to be processed in the same manner as an explicit label element. Otherwise, to me anyway, it seems like the role would be sort of pointless. Can you do me a favor and file this as a 1.2 issue and I’ll put this on the queue for proposing something? Thanks, Bryan Bryan Garaventa Principle Accessibility Architect Level Access, Inc. Bryan.Garaventa@LevelAccess.com 415.624.2709 (o) www.LevelAccess.com<http://www.LevelAccess.com> From: Gunderson, Jon R <jongund@illinois.edu> Sent: Sunday, January 13, 2019 2:41 PM To: ARIA Group <public-aria@w3.org> Subject: Would role=label provide an accessible name if in encapsulates a interactive widget 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. For the following example of an element with role=”label” encapsulating a checkbox widget. Would a proposed label role assign the accessible name “foo” to the checkbox in this case? <div role=”label”> <div role=”checkbox” aria-checked=”false”></div> foo </div> If so, we would need to updated the accessible name calculation to include the effects of the label role. Jon
Received on Monday, 14 January 2019 16:35:47 UTC