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

I like single 'Roles' approach but it may need some explanation somewhere.

On Mon, Aug 15, 2016 at 5:43 PM, Jason Kiss <jason@accessibleculture.org>
wrote:

> Ok. So, to confirm, we can delete the MSAA + UIA Express column, and move
> the  MSAA role to the MSAA + IA2 column, so that for something like the
> <abbr> element, we'd have the following:
>
> MSAA Role: ROLE_SYSTEM_TEXT
> IA2 Role: IA2_ROLE_TEXT_FRAME
> Object attributes: "abbr" attribute on the containing td
> <https://rawgit.com/w3c/aria/master/html-aam/html-aam.html#el-td> if a
> single child, text content used as a value
> Interfaces: IAccessibleText2; IAccessibleHypertext2;
> Or is it clear enough from the role names which API they belong to such
> that we could include them together? For example,
>
> Roles: ROLE_SYSTEM_TEXT; IA2_ROLE_TEXT_FRAME
>
> Any preference?
>
> Jason
>
>
> On Sat, Aug 13, 2016 at 5:13 AM, Alexander Surkov <
> surkov.alexander@gmail.com> wrote:
> > You know, we can move MSAA roles to MSAA + IA2 column instead, then UIA
> > patterns will be matched by UIA column. Do we have anything left?
> > Thanks.
> > Alexander.
> >
> > On Thu, Aug 11, 2016 at 11:22 PM, Jason Kiss <
> jason@accessibleculture.org>
> > wrote:
> >>
> >> I also prefer the idea of adding notes to the UIA column.
> >>
> >> Alex, wrt the HTML-AAM, can you give me an impression of what from the
> >> existing MSAA + UIA Express column needs to be added as a note to the
> UIA
> >> column, for which elements and properties? Once that’s done, we can get
> rid
> >> of the MSAA + UIA Express column.
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >>
> >> On 11/08/2016, at 7:43 AM, Alexander Surkov <surkov.alexander@gmail.com
> >
> >> wrote:
> >>
> >> Hi, Cynthia. Sorry for my late reply. If you're still looking for my
> >> input, then notes in UIA column should work well.
> >> Alex.
> >>
> >> On Fri, Feb 26, 2016 at 12:30 PM, Cynthia Shelly <cyns@microsoft.com>
> >> wrote:
> >>>
> >>> 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.
> >>>
> >>>
> >>>
> >>
> >>
> >
>
>