RE: proliferation of reference roles in the dpub aria spec.

I agree, we should try to use existing markup (e.g. rel attribute) before adding new aria-* properties.


From: James Craig []
Sent: Thursday, October 08, 2015 8:03 PM
To: Richard Schwerdtfeger <>
Cc: W3C PF - DPUB Joint Task Force <>; PF <>
Subject: Re: proliferation of reference roles in the dpub aria spec.

Proliferation of a new aria-* attribute to avoid role proliferation? I haven't yet seen any non-academic reason to make these anything other than standard links.

You could add a @rel value if you like.
<a href="#" rel="bibliography">

I don't see a compelling reason for a new role or a new attribute.


On Oct 8, 2015, at 5:17 PM, Richard Schwerdtfeger <<>> wrote:

As I said, I have had somewhat of a concern about the numerous definition of roles that are essentially links. The Coga task force wants to introduce and aria-destination attribute for links to create standard destinations users would go to to enable consistent style of the UI for familiarity to the user.

See the aria-destination attribute from coga:<>

So for these roles I would prefer to have:

<div role="link" aria-destination="biblioentry"> as opposed to<>


<div role="link" aria-destination="glossentry" as opposed to<>

This would cause us to start folding in some of the coga features into ARIA 1.1.

Feedback? Coga has similar needs.


Rich Schwerdtfeger

Received on Friday, 9 October 2015 13:39:58 UTC