Jamie,
I thought I addressed this before: The HTML AAM points to the ARIA core mapping specification now. They will implement what we have. One of the reasons ARIA in HTML is being held up is for us. The plan is for the host language platforms to use as much of the ARIA spec. as possible to avoid duplication of effort. Here is the link to the spec.: http://rawgit.com/w3c/aria/master/html-aam/html-aam.html
If you go down to the form element mapping you will see it says "Use WAI-ARIA mapping"
So, for backward compatibility you test for both the IA2 form role and all ARIA 1.1 and HTML 5.2 level browsers support the IA2_ROLE_LANDMARK for all landmarks and use the xml-roles object attribute to get the landmark type, ... in this case "form".
Rich
Rich Schwerdtfeger
----- Original message -----
From: James Teh <[email protected]>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS, [email protected], [email protected], [email protected]
Cc: [email protected]
Subject: Re: Form role mapping
Date: Tue, Sep 6, 2016 6:15 PM
Hi Rich,
I've already stated my view on this:
I understand the reason for the use of the landmark role for role="form". However, I disagree with the HTML form element being mapped to the landmark role because semantics are lost. The fact that something is a form has more semantic value than just being a landmark. Still, if the spec already requires this, I guess we have little choice but to comply at this stage.
At the end of the day, I'm not sure why this is still an open question, since it seems that the spec groups have already made a decision on this:
The HTML the form element now uses the ARIA mappings for the form role. See "Use WAI-ARIA mapping” under the form element. This is for all platforms.
In other words, we can't comply with the spec unless we do as you suggest, so there is no other choice. There is no point in discussing this further.
Thanks,
Jamie
On 7/09/2016 5:54 AM, Richard Schwerdtfeger wrote:Jamie, Alex, Brett,We need to reach consensus on the <form> element and role="form" mapping.Can we agree on the following? :1. that the IA2 IDL supports IA2_ROLE_LANDMARK and IA2_ROLE_FORM (so that old versions of FF and other applications using the form role can still work with ATs)2. For Firefox updates here on out the <form> element and role="form" map to IA2_ROLE_LANDMARK and xml-roles="form"This way AT vendors can check if something is a landmark to determine if something is a landmark and then expose xml-roles="form"Eventually, it would be better to not have to make an exception for the Form role when all the other landmark roles are represented as IA2_ROLE_LANDMARK with xml-roles="form"This and the other discussion items of the last 2 weeks are holding up 3 working groups - ARIA, HTML, and SVG.
Rich Schwerdtfeger--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: [email protected]
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
