W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2014

RE: ARIA labelledby & adopted children?

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Thu, 23 Oct 2014 14:10:23 +0000
To: Adam Cooper <cooperad@bigpond.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <c428a33d8b3f44e799eaee416ce8312f@BY2PR03MB272.namprd03.prod.outlook.com>
  Does aria-labelledby adopt a child?

The name calculation for text alternatives should be used by elements referenced by aria-labelledby - so yes, according to the calculation the same set of rules should apply and it should work.  In practice however this technique may not be accessibility supported.  I'd ask the question why not use another technique.  For example, when CSS is turned off the title attribute won't be displayed.  What then is the benefit of using this over aria-label?   In my experience the more the accessible name is obscured the more likely it is to not be updated and harder it is to maintain.


From: Adam Cooper [mailto:cooperad@bigpond.com]
Sent: Wednesday, October 22, 2014 4:16 AM
To: w3c-wai-ig@w3.org
Subject: ARIA labelledby & adopted children?

Hi all,

recently, I encountered a technique for providing a name for a text control:

<input type="text" aria-labelledby="abc" />
<span class="hidden" id="abc" title="name"></span>

it works as follows:
Full support (quick navigation keys & tabbing)

-          JAWS 16 +IE11 & FF32

-          Voiceover +Safari 7.1
Partial support (quick navigation keys, but not tabbing)

-          NVDA 2014.3 + IE11 & FF32
No Support

-          JAWS 16/NVDA 2014.3 + GC38

The accessible name value for MSAA, UIA, & IA2 is empty ... any thoughts as to how this might be working and not working in selected user agents?

Does aria-labelledby adopt a child?

Received on Thursday, 23 October 2014 14:10:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:53 UTC