Re: Query about intent of aria-expanded

Hi Léonie,

well, it can be expanded itself, too, for exxample an item in a tree
view that has child nodes. In any case, it controls whether some other
parts are showing (expanded) or hidden (collapsed).

Marco

On 09.09.2014 17:37, Léonie Watson wrote:
>
> Marco Zehe wrote:
>
> "I believe so, and I am recommending it be used that way. I even wrote
> an ARIA tip about it:
> http://www.marcozehe.de/2010/02/10/easy-aria-tip-5-aria-expanded-and-aria-controls/"
>
>  
>
> Thanks Marco.
>
>  
>
> Your article recommends putting aria-expanded "on the element that
> actually does the magic (the same element that has the onclick handler
> or click/keyboard event listener)". This makes complete sense.
>
>  
>
> The spec says something slightly different though.
>
>  
>
> "Indicates whether the element, or another grouping element it
> controls, is currently expanded or collapsed."
>
>  
>
> It may just be mis-placed commas making the language ambiguous, but if
> you take out the middle clause of that sentence, it reads like this:
>
>  
>
> "Indicates whether the element is currently expanded or collapsed."
>
>  
>
> Which implies something very different, that aria-expanded can be
> applied to an element that can itself be expanded or collapsed.
>
>  
>
> I think it is just ambiguous spec text, but wanted to sanity check my
> thinking before filing a bug.
>
>  
>
> Léonie.
>
>  
>
>  
>
> --
>
> Léonie Watson -- Senior Accessibility Engineer, TPG
>
> @LeonieWatson @PacielloGroup
>
>  
>
>  
>