Re: Expectations regarding aria-hidden="true" + a valid aria-label value?


I believe the core AAM requires anything that can be a source of an event MUST be in the accessibility tree.  I don't recall whether giving something a tabindex qualifies. 



> On Nov 15, 2016, at 3:32 PM, Amelia Bellamy-Royds <> wrote:
> We agreed that the presence of aria-label should cancel out role="none" or role="presentation".
> aria-hidden is different. You might have an element with a valid role and label, which you are temporarily hiding (e.g., to reflect a change in opacity or a movement off-screen).
> The only thing that cancels out aria-hidden="true" is interactivity. If the element receives keyboard focus, it can't be hidden.
> ~ABR
>> On 15 November 2016 at 10:22, Joanmarie Diggs <> wrote:
>> Hey all.
>> I am looking into failures encountered when my ATTA is used with the SVG
>> testable statements found here: [1].
>> My recollection of the consensus reached was that the presence of a
>> valid aria-label value necessitated inclusion in the accessibility tree
>> -- even if the element with that aria-label also had aria-hidden="true"
>> or was contained in an ancestor with aria-hidden="true". However, that
>> seems to contradict the expectations in a significant number of tests on
>> the aforementioned testable statements page.
>> Could someone please clarify if my recollection is wrong or if the
>> testable statements are? If it is the former, then I have an
>> implementation to fix, but if it is the latter, it would be great to
>> have the testable statements wiki corrected.
>> Thanks!
>> --joanie
>> [1]

Received on Wednesday, 16 November 2016 01:01:27 UTC