[aapi] RE: aria-ISSUE-1015 (uia-express): Firefox interested in doing UIA-Express. We may need to un-deprecate it. [ARIA 1.1 Core Mapping Specification]

Alex, 

I recall you saying in another context that Firefox was interested in UIA Express. The column for it was removed from Core-AAM, and is pretty sparse in HTML-AAM. We need to figure out how best to document it.  Most of the mappings will be the same as the UIA mappings. What do you think is the best way to document the places where it's different? We could add notes to the UIA column where needed, or have a separate column where we copy the UIA column and add the notes.  I think I'd prefer to have a single column if we can, because it will be easier to maintain in the spec. Do you think that would work for you? We're not doing any more development on the implementation in IE, so you're the main customer right now.

Thanks,
Cynthia

-----Original Message-----
From: Accessible Rich Internet Applications Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] 
Sent: Friday, February 26, 2016 9:20 AM
To: public-aria@w3.org
Subject: aria-ISSUE-1015 (uia-express): Firefox interested in doing UIA-Express. We may need to un-deprecate it. [ARIA 1.1 Core Mapping Specification]

aria-ISSUE-1015 (uia-express): Firefox interested in doing UIA-Express. We may need to un-deprecate it. [ARIA 1.1 Core Mapping Specification]

http://www.w3.org/WAI/ARIA/track/issues/1015


Raised by: Cynthia Shelly
On product: ARIA 1.1 Core Mapping Specification

Firefox has expressed interest in doing UIA Express. We may need to un-deprecate it. If we do that, I propose we start by copying the UIA column, and then making notes where there is a difference.

Received on Friday, 26 February 2016 17:30:39 UTC