Re: ACTION-1039: aria-hidden and inner/outer elements

Okay,

I talked to Rich. He actually doesn't agree with what he wrote on this
initially - that the inner content with aria-hidden="false" should be
exposed in the accessibility tree.

The net is that this is an author error and the UA is not responsible for
correcting author errors. While we obviously don't list all author errors
in the UAIG, we do list some. So my recommendation is that we add this
scenario to the list of author errors in section 6.2 of the UAIG.

http://www.w3.org/WAI/PF/aria-implementation/#document-handling_author-errors

Any objection?

Andi



From:	James Craig <jcraig@apple.com>
To:	Andi Snow-Weaver/Austin/IBM@IBMUS
Cc:	cyns@microsoft.com, dbolter@mozilla.com, W3C WAI-XTECH
            <wai-xtech@w3.org>
Date:	05/15/2012 05:19 PM
Subject:	Re: ACTION-1039: aria-hidden and inner/outer elements




On May 15, 2012, at 8:55 AM, Andi Snow-Weaver <andisnow@us.ibm.com> wrote:
> Can you please take a look at action-1039? The one question for us (item
2) is about aria-hidden="true" on an outer element that has an inner
element with aria-hidden="false". Rich is asking for a clarification in the
UAIG that the inner element should still be exposed in the accessibility
tree. Do you agree with what he is proposing?
>
> https://www.w3.org/WAI/PF/Group/track/actions/1039

I don't agree that the element should be exposed. If the ancestor is
hidden, all descendants should also be hidden. If the same way, if you have
CSS display:none on a node, adding display:block to a child element does
not make it appear.

Another technical challenge regarding the AX tree would be that you'd have
to promote these child nodes to a higher branch, since the parent element
is no longer in the tree. This could result in very unexpected behavior in
some APIs.

James