RE: updating HTML to AAPI mapping

Let me know what I can do to help :-) (Sorry I've been quiet lately.just a
bunch of different things going on.)

 

From: Steve Faulkner [mailto:faulkner.steve@gmail.com] 
Sent: Monday, February 04, 2013 2:17 PM
To: jason@accessibleculture.org
Cc: Cynthia Shelly; Char James-Tanny; Larry Weiss; David Bolter; W3C
WAI-XTECH
Subject: Re: updating HTML to AAPI mapping

 

Hi Jason, 

 

Great!

 

>Should we be updating the tables to represent HTML5.1 WD as it currently
is, or stick only with what is in HTML5.0 CR?

 

I think we should be updating the tables as new features are added or
modified or removed (in the case of command it was never implemented) so
does not need to be included in my opinion)

 

I think we should be linking to HTML 5.1

 

If you have the cycles please update the doc at will, ping me if you need
anything.

 

regards

 

Steve

On 3 February 2013 03:52, jason@accessibleculture.org
<jason@accessibleculture.org> wrote:

Cynthia, Steve,

I'd like to start filling in some of the holes in the HTML to Platform A11y
APIs guide [1]. I made a few negligible changes today, but think, as a
starting point for a renewed run at this document, that it would be useful,
at least to me, to discuss what we will be doing with the differences
between HTML5.0 and 5.1. When we link to elements and attributes from our
document, to what version of the HTML5 spec should we be linking? Should we
be updating the tables to represent HTML5.1 WD as it currently is, or stick
only with what is in HTML5.0 CR? For instance, there are some significant
changes around <menu>, <command> and <menuitem>. There are also some new
elements, e.g., <main> in the pipeline and that already implemented in some
browsers.

I also think it would be good to come up with some additional text to
describe why MSAA and IA2 are each now in columns combined with UIA Express,
what "Use MSAA or UIA guidance" means, and a convention for how we should be
presenting that information for elements where IAccessibleEx applies.
Currently, a few of the MSAA + UIA Express values for some elements refer to
UIA Control Types. As I understand it, IAccessibleEx can only be used to
expose a certain number of properties and control patterns [2], and this
doesn't include control types. Or is the idea that IAccessibleEx should be
used to expose the relevant properties and control patterns associated with
whatever control type is referred to? Happy to be corrected here.

Cheers,

Jason

[1] https://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html
[2]
http://msdn.microsoft.com/en-us/library/windows/desktop/dd561899%28v=vs.85%2
9.aspx








 

-- 
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
<http://www.paciellogroup.com/resources/wat-ie-about.html>