Re: Agenda: July 30, 2015 WAI-PF ARIA Caucus

On 2015-07-27 4:53 PM, Richard Schwerdtfeger wrote:
> > *Agenda: July 30, 2015 WAI-PF ARIA Caucus* ... > > 6. Issue 736 
aria-label overriding listitem and treeitem content as > containers o 
https://www.w3.org/WAI/PF/Group/track/issues/736 > > ...

Just to see what was exposed through AAPIs, I made a test file of 
listitems with and without an @aria-label attribute.  Broadly speaking, 
without an aria-label attribute, the name property is based on the 
content of list item element.  The result is that the accessible's name 
and content are identical.  With an aria-label, the accessible's name is 
as given by the aria-label, but the accessible's content is based on the 
element's content [1].

Technically speaking, then, aria-label is *not* overriding the listitem 
content, as claimed in ISSUE-736.  It is only "overriding" the name 
property (as it should).

According to the spec, an accessible name is required for the listitem 
role, and can be either author supplied or taken from the content [2].  
Also, according to the text alternative computation, author supplied 
names have precedence over content supplied names [3].  The results I'm 
seeing are consistent with the specifications.

I have one question:  why do list items *require* an accessible name?  
Anyone know the rationale for that?

[1] http://clown.idrc.ocad.ca/Fluid/aria/ListItemsWithLabels.html
[2] http://w3c.github.io/aria/aria/aria.html#listitem
[3] 
http://w3c.github.io/aria/accname-aam/accname-aam.html#mapping_additional_nd 

-- 
;;;;joseph.

'Array(16).join("wat" - 1) + " Batman!"'
            - G. Bernhardt -

Received on Wednesday, 29 July 2015 20:08:58 UTC