This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
When validating a draft document at http://www.w3.org/2010/02/rdfa/sources/rdfa-core/Overview.html the validator complains about the value 'directory' for the attribute 'role'. The role attribute takes values defined in http://www.w3.org/1999/xhtml/vocab/#XHTMLRoleVocabulary and directory is one such value. Please add that value to the list of legal @role values.
As a follow up, I note that HTML5 references http://www.w3.org/TR/wai-aria/roles#role_definitions for the list of role values. This is a similar list to the one I referenced, and also includes 'directory' as a legal value.
The HTML spec disallows particular role values on particular elements. Not all role values are actually allowed on every element. In this case, the spec explicitly and intentionally disallows role=directory for the <section> element; see the table here: http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-implicit-aria-semantics Cc'ing Steve Faulkner so that he can comment on the rationale for that. But moving this to resolved=wontfix due to the fact that as far as I can tell the validator is in conformance with the current requirements in the HTML spec here.
(In reply to comment #1) > As a follow up, I note that HTML5 references > http://www.w3.org/TR/wai-aria/roles#role_definitions for the list of role > values. This is a similar list to the one I referenced, and also includes > 'directory' as a legal value. Hi Shane, as Mike pointed out the ARIA spec allows host languages to set restrictions on use of role vales dependent on the native semantics.[1] These restrictions are defined in HTML in [2] and [3]. [1] http://www.w3.org/TR/wai-aria/host_languages#host_general_conflict [2] http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-implicit-aria-semantics [3] http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-implicit-aria-semantics