Re: aria-labelledby pointing to an element with aria-hidden=”true”

refer to Accessible Name and Description: Computation and API Mappings 1.1

http://w3c.github.io/aria/accname-aam/accname-aam.html#step2

Comment:
> By default, assistive technologies
> <http://w3c.github.io/aria/accname-aam/accname-aam.html#dfn-assistive-technologies>
> do not relay hidden information, but an author can explicitly override that
> and include hidden text as part of the accessible name
> <http://w3c.github.io/aria/accname-aam/accname-aam.html#dfn-accessible-name>
> or accessible description
> <http://w3c.github.io/aria/accname-aam/accname-aam.html#dfn-accessible-description>
> by using aria-labelledby or aria-describedby.
>

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>

On 13 April 2017 at 12:49, Schnabel, Stefan <stefan.schnabel@sap.com> wrote:

> I have a question to the group regarding aria-labelledby pointing to an
> element with aria-hidden=”true”.
>
> Is that *an allowed relation* according to
> *http://www.w3.org/TR/wai-aria/* <http://www.w3.org/TR/wai-aria/> ?
>
> Also, *http://www.w3.org/TR/wai-aria-1.1/#aria-hidden*
> <http://www.w3.org/TR/wai-aria-1.1/#aria-hidden> and
> *http://www.w3.org/TR/wai-aria-1.1/#aria-labelledby*
> <http://www.w3.org/TR/wai-aria-1.1/#aria-labelledby> give no clue about
> this so it seems to be OK.
> I do not speak of better alternatives for respective use cases, just if
> the specification explicitely leaves that as a possible option.
> Screen readers (Jaws) currently read information in nodes with
> aria-hidden=”true” associated with aria-labelledby when respective elements
> with that relation are focused.
>
> Best Regards
> Stefan
>
>