Hi Rich, I don't necessarily have an objection to introducing a new role, but I also don't quite follow the justification. I follow that region became a subclass of landmark. However, I don't follow how this changes the "landmark" role; if anything, it changes the "region" role. And even then, the region role never had its own IA2 role in the first place. Furthermore, since we have to look at xml-roles anyway (as we always have, despite my objection years ago, but that's an entirely different story), I don't follow how the landmark role is useful. I'm sure I'm missing something here. Can you enlighten me? :) Thanks, Jamie On 20/02/2016 9:37 AM, Richard Schwerdtfeger wrote: > 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 > > > 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 > > > So, this is the revised set of landmarks: > > 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. > > Thanks, > > Rich > > > > _______________________________________________ > Accessibility-ia2 mailing list > Accessibility-ia2@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 -- James Teh Executive Director, NV Access Limited Ph +61 7 3149 3306 www.nvaccess.org Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess SIP: jamie@nvaccess.org
Received on Tuesday, 23 February 2016 01:37:52 UTC