W3C home > Mailing lists > Public > public-html-a11y@w3.org > May 2013

Re: HTML to platform accessibility API guide

From: <jason@accessibleculture.org>
Date: Mon, 20 May 2013 22:28:03 +1200
Cc: "public-html-admin@w3.org" <public-html-admin@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>, David Bolter <dbolter@mozilla.com>, Alexander Surkov <surkov.alexander@gmail.com>, Michael Smith <mike@w3.org>, James Craig <jcraig@apple.com>
Message-Id: <311B9A60-2C77-4175-9029-A1A69D4424FB@accessibleculture.org>
To: Steve Faulkner <faulkner.steve@gmail.com>

On 20/05/2013, at 8:58 PM, Steve Faulkner <faulkner.steve@gmail.com> wrote:

> Hi all
> work on this[1] has slowed to a crawl for some time for various reasons.
> I would like to see a version of this spec done.

Agreed. Thanks for this prodding, Steve. 

> So I am proposing the following:
> We limit the scope of the spec to:
>  - role state and property mapping of HTML elements and attributes
> - accessible name calculation
> many other things could be in scope, but what should have not been defined and having at least the above defined would be better than what we have now.

I'm not sure this significantly reduces the scope given what's already there (or not), but agree that focussing on the basic mappings of elements and attributes should be a priority. Additional direction, normative or otherwise, around the implementation of specific features, e.g. figure and figcaption or the table algorithm, can certainly be considered secondary at this point.

> the spec be made normative (current status undefined)

Also agreed. All of our discussions to date, as I've interpreted them, have found agreement on making the document describe correct mappings, as much as is possible, given the current specs of accessibility APIs. We would need, I think, to come to some agreement on how to address the non-spec particularities of some popular UA implementations.

> we ask for additional editors (people who will commit to working on the spec to get it completed).

This would be very helpful, especially if we could involve, needless to say, some editors with experience implementing or making use of the accessibility APIs. There is such variation in, for example FF and IE's, mapping of roles and states, and how different AT make use of them, that getting some involvement on this front, if possible, would be really useful. I've got a few ideas about who to approach here.

> Cynthia has indicated she doesn't have time to work on it (confirmation needed), but I believe jason is still doing bits and I will commit to help.

I've continue to manage fits and bits here and there, but unfortunately nothing quite comprehensive enough to move things along to where they should be.

> I will also move to github as its easier to work on from there. (unless anyone objects)

Sounds good.


> [1] https://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html
> --
> Regards
> SteveF
> HTML 5.1
Received on Monday, 20 May 2013 10:28:39 UTC

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