W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2011

Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Mon, 17 Jan 2011 15:29:47 +0000
Message-ID: <AANLkTika9GzJ=TFjNAprH095ybe5uA49jG37Rujy8gjg@mail.gmail.com>
To: David Bolter <dbolter@mozilla.com>
Cc: Cynthia Shelly <cyns@microsoft.com>, Charles McCathieNevile <chaals@opera.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Marco Zehe <marco.zehe@googlemail.com>, James Craig <jcraig@apple.com>, Loretta Guarino Reid <Lorettaguarino@google.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Janina Sajka <janina@rednote.net>, "Michael(tm) Smith" <mike@w3.org>, Sam Ruby <rubys@intertwingly.net>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, Ian Hickson <ian@hixie.ch>
Hi Dave, thanks for your feedback,

just to be clear, this your view as an user agent implementor (mozilla)
right?

regards
Steve

On 17 January 2011 15:21, David Bolter <dbolter@mozilla.com> wrote:

>  The guide is necessary to providing interoperable accessibility API
> support (in the browser) for desktop accessibility clients such as screen
> readers. Note I don't care where the guide sits as long as we have it and
> more than one browser vendor agrees to seriously use it.
>
> Cheers,
> David
>
>
> On 15/01/11 10:41 AM, Steve Faulkner wrote:
>
> A number of people including myself , Cynthia Shelly, Dave Bolter and Rich
> have started working on HTML to Platform Accessibility APIs Implementation
> Guide <http://dev.w3.org/html5/html-api-map/overview.html>. It is
> currently intended as a informative reference produced by the W3C HTML WG.
>
>
>
>  The editor of the HTML5 specification has provided some feedback [1] on
> this document.
>
>
>  I would appreciate some feedback from involved in the accessibility
> implementation space in regards to the usefulness of documenting the mapping
> between HTML elements and attributes and the roles states and properties in
> the various platform accessibility APIs. And what sort of information should
> be provided, if any.
>
>  If as the HTML5 editor states;
>
>  "the proposed document is unnecessary. Vendors have not shown an
> inability to read the existing normative specifications"
>
>  then it would be good to know that is not needed and will not be useful
> to its target audience, so those involved can use their time on more
> productive pursuits.
>
>
>  [1]
> http://wiki.whatwg.org/wiki/Objections_against_CP_for_ISSUE-129#The_HTML_to_Platform_Accessibility_APIs_Implementation_Guide
>
> --
> 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
Received on Monday, 17 January 2011 15:30:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:17 UTC