Re: [Accessibility-ia2] aria-details and aria-errormessage mapping [Issue-1044]

Alex, Jamie,   We discussed this concatenation and Microsoft (Cynthia Shelly) and also Matt King and the more we look at concatenation the worse it looks. This impact more than IA2. It would effect the UIA Mapping for Edge and it creates problems for internationalization whereby we can't put a

Re: [Accessibility-ia2] IA2 Role Landmark

Well it is used by the most pervasive apps on the planet using IA2 already. Chrome, FF, and eclipse-based apps. Sent from my iPhone > On Aug 25, 2016, at 10:45 AM, Alexander Surkov > wrote: > > I definitely agree that IA2 needs a flexible mechanism to expose

Re: [Accessibility-ia2] IA2 Role Landmark

I definitely agree that IA2 needs a flexible mechanism to expose roles, I'm just not sure it should be xml-roles object attribute. On Thu, Aug 25, 2016 at 11:15 AM, Rich Schwerdtfeger wrote: > Alex, those object attributes should have been included in IA2 a long time >

Re: [Accessibility-ia2] IA2 Role Landmark

Alex, those object attributes should have been included in IA2 a long time ago. I in no way see these as a hack. Eclipse uses them too. Sent from my iPhone > On Aug 25, 2016, at 9:49 AM, Alexander Surkov > wrote: > > This is true, however xml-roles is not standard

Re: [Accessibility-ia2] IA2 Role Landmark

This is true, however xml-roles is not standard attribute in IA2, it's rather a browser specific hack to expose the semantics, that otherwise was missed. So if the API provides a way to expose an element semantics more fully, then I'd say it's the way to go. Having said that, I'm also concerned

Re: [Accessibility-ia2] IA2 Role Landmark

Hi, Joanie. I'd say HTML form is a landmark as any other form in the world, but I let judge others on this. If there's no use case for ATK form role, then what is a reason to keep it? On Thu, Aug 25, 2016 at 10:24 AM, Joanmarie Diggs wrote: > Hi Alex, all. > > I don't

Re: [Accessibility-ia2] IA2 Role Landmark

I don't think Jamie argues that FORM is not a landmark. The point is that FORM is a form and also a landmark. IA2 provides a special FORM role, which is used both for ARIA and HTML currently, and adopted by browsers and screen readers. If we use weaker role for forms, then we loose semantics as

Re: [Accessibility-ia2] IA2 Role Landmark

Hi James, currently Jaws treats forms like regions as landmarks, i.e. showing them in its landmarks dialog, too. They do this for reason, page structure is very clearly revealed by this. I consider this as a strong feature and do not like this changed. The logic behind that is the pragmatic