Re: [Accessibility-ia2] Form role mapping

>*AT and browsers support those roles, if Firefox Nightly starts to expose IA2_ROLE_LANDMARK instead IA2_ROLE_FORM, then it >breaks all existing screen reader versions. In case of commercial screen readers this is painful for the users, since they have to buy a >new version of their screen reader. 

Re: [Accessibility-ia2] Form role mapping

Hi Rich, I think this is fine. This seems like a reasonable way to move forward. Brett Brett Lewis VFO | Software Engineer 11800 31st Court North, St. Petersburg, FL 33716 T 727-299-6270 ble...@vfo-group.com www.vfo-group.com From: Richard

Re: [Accessibility-ia2] Form role mapping

There's a point in discussing, the spec can be changed, if there's solid ground for that. My concerns are: * Both IA2 and ATK have a better role match for both role='form' and HTML form, which is ATK_ROLE_FORM and IA2_ROLE_FORM. Thus if there's no strong reason why we have to use a 'weaker'

Re: [Accessibility-ia2] Form role mapping

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

Re: [Accessibility-ia2] Form role mapping

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