W3C home > Mailing lists > Public > public-aria@w3.org > February 2016

IA2 Role Landmark

From: Richard Schwerdtfeger <richschwer@gmail.com>
Date: Fri, 19 Feb 2016 17:37:17 -0600
Message-Id: <F56816E7-E58E-4F9A-ACFF-A2BFB987F916@gmail.com>
Cc: IA2 List <Accessibility-ia2@lists.linux-foundation.org>, ARIA Working Group <public-aria@w3.org>, Joseph Scheuhammer <clown@alum.mit.edu>
To: Alexander Surkov <surkov.alexander@gmail.com>
Hi Alex, 

I am following up on this earlier discussion regarding needing an IA2_LANDMARK_ROLE 

http://lists.linuxfoundation.org/pipermail/accessibility-ia2/2016-January/001993.html <http://lists.linuxfoundation.org/pipermail/accessibility-ia2/2016-January/001993.html>

A fundamental change from ARIA 1.0 is we now have the role “region” as a descendant of a role of landmark:

https://www.w3.org/TR/wai-aria-1.1/#region <https://www.w3.org/TR/wai-aria-1.1/#region>

So, this is the revised set of landmarks:

https://www.w3.org/TR/wai-aria-1.1/#landmark_roles <https://www.w3.org/TR/wai-aria-1.1/#landmark_roles>

The reason for this is developers have been using labelledy regions as landmarks and in HTML5 we now have a section landmark which will default to a role of “region” if it has a label on it. 

Given this change we would like this a new IA2_ROLE_LANDMARK that matches the landmark role we now have in ATK/ATSPI. The xml-roles attribute would take the value of the actual role as we know. 

Is there any objection to introducing this new role in IA2?

We are trying to lock down ARIA 1.1 and this is one of the issues we need to address. 



Received on Friday, 19 February 2016 23:37:47 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:20 UTC