Re: feedback on HTML to Platform Accessibility APIs Implementation Guide requested

thanks Alex! am capturing your feedback as individual bugs have been ccing
you, if you don't weant the bug noise can leave you off.

If you have a w3c bugzilla account you could add bugs directly.

You can use the bug adder that is built into the spec to quickly add bugs.

regards
steve

On 4 April 2012 10:51, Alexander Surkov <surkov.alexander@gmail.com> wrote:

> Hi, Steve. I'm going to run through the spec and compare it to what
> Firefox does. Often I don't have strong opinion what is correct and
> what is not. I'm pretty fine to change Firefox implementation but we
> should be careful because we wake up the sleeping dog. I'll split it
> into parts to make discussion easier. Here's a difference for elements
> starting from 'a'.
>
> 1) a (represents a hyperlink). Also, apply special rule to expose
> STATE_LINKED to link and all its descendants.
>
> I think Firefox doesn't apply state_linked to all descendants. It
> applies it to text node accessibles and to images only. Does it really
> make sense to apply it to any random element? That requires some extra
> work on the server side.
>
> 2) I didn't see any word about accessible actions, for example, link
> accessible exposes "jump" action. Is this table supposed to address it
> or should it be handled by some another table?
>
> 3) a (no href attribrute) MSAA: ROLE_SYSTEM_ TEXT
> Firefox exposes <a> as ROLE_SYSTEM_LINK always. If no @href then no
> STATE_LINKED. Any particular reason to expose it as SYSTEM_TEXT?
>
> 4) I don't see where the spec address applied CSS pseudo styles like
> a:visited. In that case Firefox exposes STATE_TRAVERSED for MSAA and
> ATK_STATE_VISITED for ATK on link accessible.
>
> 5) abbr elements is exposed in Firefox as "abbr" VARIANT on MSAA and
> IA2_ROLE_TEXT_FRAME on IA2.
>
> 6) area (no href attribute). If area is used to define an image map
> then it doesn't make sense to expose an accessible for it at all.
> However image accessible should contain link accessibles corresponding
> to area elements.
>
> 7) article is exposed as readonly DOCUMENT (so no question mark for me
> for ??ROLE_SYSTEM_GROUPING?)
>
> 8) aside. Firefox exposes VARIANT aside role on MSAA and IA2_ROLE_NOTE
> on IA2, ATK_ROLE_SECTION on ATK.
>
> 9) audio is exposed with ROLE_SYSTEM_GROUPING on MSAA and IA2,
> ATK_ROLE_PANEL on ATK.
>
>
> Thank you.
> Alex.
>
> On Wed, Apr 4, 2012 at 5:59 PM, Steve Faulkner <faulkner.steve@gmail.com>
> wrote:
> > Hi All,
> > The AAPI task force are looking for feedback on what needs to be added to
> > the HTML to Platform Accessibility APIs Implementation Guide
> > http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html
> > to make it as useful as possible  to browser and AT implementers.
> >
> > We realise that of the content we already have in there, there are still
> > many gaps to fill, but we also realise that the scope of information we
> > provide needs to be extended. We would appreciate your input in helping
> us
> > define that scope.
> >
> > any feedback you can provide would be appreciated
> >
> > --
> > with regards
> >
> > Steve Faulkner
> > Technical Director - TPG
> >
> > www.paciellogroup.com | www.HTML5accessibility.com |
> > www.twitter.com/stevefaulkner
> > HTML5: Techniques for providing useful text alternatives -
> > dev.w3.org/html5/alt-techniques/
> > Web Accessibility Toolbar -
> > www.paciellogroup.com/resources/wat-ie-about.html
> >
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html