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

I like this approach

 

​​​​​

 

 

* katie *

 

Katie Haritos-Shea 
Senior Accessibility SME (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545

 

From: Richard Schwerdtfeger [mailto:schwer@us.ibm.com] 
Sent: Thursday, October 8, 2015 8:17 PM
To: W3C PF - DPUB Joint Task Force <public-dpub-aria@w3.org>
Cc: PF <public-pfwg@w3.org>
Subject: proliferation of reference roles in the dpub aria spec. 

 

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:  <https://rawgit.com/w3c/coga/master/issue-papers/links-buttons.html> https://rawgit.com/w3c/coga/master/issue-papers/links-buttons.html

So for these roles I would prefer to have:

<div role="link" aria-destination="biblioentry"> as opposed to  <http://rawgit.com/w3c/aria/master/aria/dpub.html#dpub-biblioref> http://rawgit.com/w3c/aria/master/aria/dpub.html#dpub-biblioref

similarly:

<div role="link" aria-destination="glossentry" as opposed to  <http://rawgit.com/w3c/aria/master/aria/dpub.html#dpub-glossref> http://rawgit.com/w3c/aria/master/aria/dpub.html#dpub-glossref

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

Feedback? Coga has similar needs. 

Rich



Rich Schwerdtfeger