Re: Extensible ARIA?

Yes, the role attribute allows it.
However ARIA  roles (not the role attribute) supported it in the earlier versions - not what went to TR.

All the best

Lisa Seeman

Athena ICT Accessibility Projects 
LinkedIn, Twitter





---- On Wed, 02 Apr 2014 16:44:41 +0300 Shane McCarron<shane@aptest.com> wrote ---- 


Actually, the Role Attribute module does allow for extensibility via vocabularies.  See http://www.w3.org/TR/role-attribute

This permits the use of roles that look like foo:bar, where foo is a reference to a vocabulary via a URI.  This is a conforming use of the Role Attribute, although at this time no ATs that I know of take advantage of this capability.  In my mind, it would be easiest to use this as:
 

role="myRoles:someRole basicRole" where basicRole is a defined ARIA role so that ATs and User Agents that do not recognize the extended role will still fall back to the well known basic role from ARIA.
 






On Wed, Apr 2, 2014 at 5:15 AM, lisa.seeman <lisa.seeman@zoho.com> wrote:
 Hi Leonie and Steve,

Aria roles were originally designed to be extendable via the RDF.
 
In the early drafts of the roles module there was even a section on how to extend them.
See http://www.w3.org/TR/2006/WD-aria-role-20060926/#Extending
 
For the sake of simplicity and adoption this was not part of the later versions however at the time we said we would revisit it for ARIA 2.0. I am not sure that will happen but this thread is an argument to do so.
 I personal would like to see that happen. Extentions could be part a central repository that prevents duplication and then special interest groups could have a role extension which works with their AT's 

All the best
 
Lisa Seeman

Athena ICT Accessibility Projects
LinkedIn, Twitter
 




---- On Wed, 02 Apr 2014 12:17:39 +0300 Steve Faulkner<faulkner.steve@gmail.com> wrote ---- 

 
hi leonie,


have a look at thread(s) on public PF list on aria-roledescription  http://lists.w3.org/Archives/Public/public-pfwg/2014Apr/
 
--

Regards

SteveF
 
HTML 5.1



 

On 2 April 2014 09:15, Léonie Watson <lwatson@paciellogroup.com> wrote:
  Hello,
 
Web components offer exciting possibilities, and accessibility is going to need to keep pace with this potential. This came up at EdgeConf recently, where ARIA was widely thought to be the solution amongst developers.
  
I’m not sure that ARIA (as it stands) can keep pace with the near infinite range of components that developers could/will create? It seems improbable that the ARIA spec could ever encompass every/any element/role that a developer might conjure up.
  
Jeremy Keith made this point at EdgeConf, and also suggested the possibility of ARIA becoming extensible [1].
 
 I thought it was worth raising here for discussion. Apologies if it’s already being discussed here or elsewhere.
  
Léonie.
 [1] http://adactio.com/journal/6719/
 
 
  
 -- 
Senior Accessibility Engineer, TPG
@LeonieWatson @PacielloGroup