RE: Feedback on draft aria-labelledby guidance

Hi Bryan,

Thanks for your patience and apologies for the JS Fiddle link - I really need to find a better fast code snippet platform. I've attached an html file with the code to this email. Although if this requirement isn't new, perhaps it doesn't need to be explored now.

Thanks,
Sarah

From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Sent: Sunday, June 9, 2019 10:24 PM
To: Sarah Higley <Sarah.Higley@microsoft.com>; public-aria-practices@w3.org
Cc: public-aria@w3.org
Subject: RE: Feedback on draft aria-labelledby guidance

Hi Sarah,
Can you do me a favor and send me the code example as a plain txt attachment? I'm having trouble with JSFiddle, the accessibility of this sort of sucks.

Just as an FYI though, the single node processing requirement isn't a new proposal, but has always been part of the AccName spec going back to 1.0.

Thanks,
Bryan


Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com>
415.624.2709 (o)
www.LevelAccess.com<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.levelaccess.com%2F&data=02%7C01%7CSarah.Higley%40microsoft.com%7C0238ee660b2a4fa9916008d6ed63eb09%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636957410749579215&sdata=y73BnSC7oggiyDr91g1oP9lZwxGMj32amuLHa%2FYHMwo%3D&reserved=0>

From: Sarah Higley <Sarah.Higley@microsoft.com<mailto:Sarah.Higley@microsoft.com>>
Sent: Tuesday, June 04, 2019 12:23 PM
To: public-aria-practices@w3.org<mailto:public-aria-practices@w3.org>
Subject: Feedback on draft aria-labelledby guidance

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 all,

Expanding on what I said in the meeting, I think the restriction on parsing a node multiple times may cause unexpected results in the following example. It shows a table with one cell containing a button with a self-referencing ID. When parsing the cell's name using name from content, the button would be parsed twice. Let me know what you think!

Sample code link: https://jsfiddle.net/s7fwonvy/show<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjsfiddle.net%2Fs7fwonvy%2Fshow&data=02%7C01%7CSarah.Higley%40microsoft.com%7C0238ee660b2a4fa9916008d6ed63eb09%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636957410749579215&sdata=1H7fo09K56lS%2FDuBqLv8DQT%2B2hNHSixD9xO6YQ%2BZt5g%3D&reserved=0> (apologies for using JS Fiddle; you shouldn't need to enter code view though)

Relevant paragraph suggested by Bryan:

Any node that is parsed in the tree as a child or owned element via aria-owns, or as part of an aria-labelledby or aria-describedby traversal, can only be processed once and will be ignored by any other references to itself later by any other attribute or process during this computation. This prevents infinite loops from occurring. So, only the first instance of this node will be processed when encountered in the order of the naming computation, and not by any others after that.

Thanks,
Sarah