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

The @rel rationale has turned me too……..

 

​​​​​

 

 

* 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: Gunderson, Jon R [mailto:jongund@illinois.edu] 
Sent: Friday, October 9, 2015 9:38 AM
To: James Craig <jcraig@apple.com>; Richard Schwerdtfeger <schwer@us.ibm.com>
Cc: W3C PF - DPUB Joint Task Force <public-dpub-aria@w3.org>; PF <public-pfwg@w3.org>
Subject: 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.

 

 

Jon

 

 

From: James Craig [mailto:jcraig@apple.com] 
Sent: Thursday, October 08, 2015 8:03 PM
To: Richard Schwerdtfeger <schwer@us.ibm.com <mailto:schwer@us.ibm.com> >
Cc: W3C PF - DPUB Joint Task Force <public-dpub-aria@w3.org <mailto:public-dpub-aria@w3.org> >; PF <public-pfwg@w3.org <mailto:public-pfwg@w3.org> >
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.

 

James

 

 

On Oct 8, 2015, at 5:17 PM, Richard Schwerdtfeger <schwer@us.ibm.com <mailto:schwer@us.ibm.com> > 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:  <https://urldefense.proofpoint.com/v2/url?u=https-3A__rawgit.com_w3c_coga_master_issue-2Dpapers_links-2Dbuttons.html&d=AwMFAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=PTUU3A-rlaO9MLoADNR5ZLP4MN07464oZJOjtFmHuQE&s=RR1mQwAzCvsIn6biKJRzh4y5tSoms3jExQ7PW-LeLwQ&e=> 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  <https://urldefense.proofpoint.com/v2/url?u=http-3A__rawgit.com_w3c_aria_master_aria_dpub.html-23dpub-2Dbiblioref&d=AwMFAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=PTUU3A-rlaO9MLoADNR5ZLP4MN07464oZJOjtFmHuQE&s=HsuejDRI_HgwZ_DMgOPt3W3gIwxC2U-PJdOs7yB2fNw&e=> http://rawgit.com/w3c/aria/master/aria/dpub.html#dpub-biblioref

similarly:

<div role="link" aria-destination="glossentry" as opposed to  <https://urldefense.proofpoint.com/v2/url?u=http-3A__rawgit.com_w3c_aria_master_aria_dpub.html-23dpub-2Dglossref&d=AwMFAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=PTUU3A-rlaO9MLoADNR5ZLP4MN07464oZJOjtFmHuQE&s=mXKjFCwJdHcblaRMMTD47M1CJZBEow_7vUxDzlY4k8U&e=> 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