RE: Question regarding role=directory, the usage and purpose is unclear

For me, from what I can see in the accessibility tree, the use of role=directory and not having any role at all on a UL reports the same role and assigned label via aria-label regardless, so it appears to have no effect other than this other than to break the list using JAWS16 in IE11, which would be an FS bug.

The problem I'm seeing with the spec text, is that it's not clear where this role is supposed to be applied, nor if there needs to be specific child elements. 

E.G From the spec text, it seems to imply that the following is valid

<div role="directory">
<input type="text" title="Filter table of contents" />
<p>
Introductory text...
</p>
... List markup here ...
</div>

Would this be valid in the accessibility tree?

Bryan Garaventa
Senior Accessibility Engineer
SSB BART Group, Inc.
bryan.garaventa@ssbbartgroup.com
415.624.2709 (o)
www.SSBBartGroup.com

-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] 
Sent: Friday, April 17, 2015 7:30 AM
To: Matthew King; Bryan Garaventa
Cc: W3C WAI Protocols & Formats
Subject: Re: Question regarding role=directory, the usage and purpose is unclear

On 2015-04-17 7:37 AM, Matthew King wrote:
> Also interesting that it has name from contents ... pretty odd for a 
> structure.

Not according to the latest editors' draft [1] nor the latest TR [2], where it's name from author [1].

[1] http://w3c.github.io/aria/aria/aria.html#directory
[2] http://www.w3.org/TR/wai-aria-1.1/#directory

--
;;;;joseph.

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

Received on Friday, 17 April 2015 18:08:10 UTC