W3C home > Mailing lists > Public > public-html-a11y@w3.org > March 2014

Re: User Agent Implementation Guide Coordination and Development - proposal

From: <jason@accessibleculture.org>
Date: Mon, 10 Mar 2014 08:08:02 +1300
Cc: W3C WAI Protocols & Formats <public-pfwg@w3.org>, Joseph Scheuhammer <clown.idi@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-Id: <A5B6A126-71DB-4386-9F3A-467F9AA23215@accessibleculture.org>
To: Rich Schwerdtfeger <schwer@us.ibm.com>
HI Rich,

My time is unfortunately restricted, but Iím happy to help as I can in the time I have and work to any priorities set by the group.

Jason


Jason Kiss
jason@accessibleculture.org
http://www.accessibleculture.org




On 8/03/2014, at 12:33 pm, Richard Schwerdtfeger <schwer@us.ibm.com> wrote:

> Hi Jason, 
> 
> I did miss that. Thank you. 
> 
> Would you be able to help out with some of the ARIA module implementation guides as well? We are looking to have ones on eBooks and Drawing semantics for charting. The drawing semantics would be used for HTML5 Canvas and SVG. 
> 
> Rich
> 
> 
> Rich Schwerdtfeger
> 
> <graycol.gif>Jason Kiss ---03/05/2014 04:56:47 PM---Hi Rich, You might have missed my response [1] (had some w3c email list
> 
> From:	Jason Kiss <jason@accessibleculture.org>
> To:	Richard Schwerdtfeger/Austin/IBM@IBMUS
> Date:	03/05/2014 04:56 PM
> Subject:	Re: User Agent Implementation Guide Coordination and Development - proposal
> 
> 
> 
> Hi Rich,
> 
> You might have missed my response [1] (had some w3c email list
> weirdness), but I'm happy to continue working on the HTML5 guide.
> 
> [1] http://lists.w3.org/Archives/Public/public-html-a11y/2014Feb/0111.html
> 
> 
> Jason
> 
> On Thu, Mar 6, 2014 at 11:07 AM, Richard Schwerdtfeger
> <schwer@us.ibm.com> wrote:
> > Moving toward HTML 5.1 we need to produce a minium of 3 user agent
> > implementation guides. For those new to this it is the accessibility API
> > mapping guide that browsers must follow in order to support a host language
> > or cross-cutting markup like WAI-ARIA. ARIA 1.0 is in the process of moving
> > to recommendation status and we were the first standards effort to
> > effectively go through candidate recommendation on such a document.
> > Producing documents like this are necessary as it allows us to normatively
> > ensure that what we put in content will work with assistive technologies
> > across multiple operating system platforms.
> >
> > Unfortunately, the HTML A11y task force did not effectively produce a
> > normative implementation specification. Hindsight being 20/20 we did not
> > pool all the qualified resources together to achieve the task and there was
> > duplication of effort between what the ARIA task force was doing and what
> > the HTML5 accessibility task force was doing. In addition to HTML we also
> > need to do produce a User Agent Implementation Guide for SVG2. Furthermore,
> > we have a convergence of HTML markup in SVG. Here are some examples:
> >
> > canvas support
> > WAI-ARIA support
> > Definition of elements in terms of WAI-ARIA host language semantics
> > tabindex support
> > iFrame support
> > Use of the same DOM3 event handlers
> > Use of document object methods used for things like activeElement needed to
> > support keyboard support by JavaScript developers.
> >
> >
> > Given all these issues I had meetings with editor stake holders and I have
> > produced a draft outline for 3 specifications which the editor stake holders
> > have agreed to - as a solid starting point.
> >
> > The proposal is to:
> >
> > 1. Start with the follow outline for the documents
> > http://www.w3.org/WAI/PF/wiki/Outline_Core_User_Agent_Implementation_Guide
> >
> > It would mean that the ARIA user Agent implementation would form a core
> > implementation guide as the subsequent host languages will have elements
> > defined in terms of ARIA semantics. This allows HTML 5.1 and SVG2 to
> > leverage the mappings that are in the Core, such as role, state, and
> > property mapping tables as well as event notification. Host languages will
> > be able to also define name and description computation rules specific to
> > the host language.
> >
> > 2. Make Protocols and Formats or (the new name Accessibility Platform
> > Architectures) be responsible for coordinating the activities and ensure
> > input from both the HTML accessibility task force and the SVG working group.
> >
> > 3. Start with the following editors who have signed on as editors:
> >
> > - ARIA Core: Joseph Scheuhammer
> > - HTML5: Steve Faulkner and Alexander Surkov
> > - SVG2: Rich Schwerdtfeger
> >
> > 4. We do have additional ARIA modules that will need to be created for both
> > eBook structural semantics and Graphics (applicable to Canvas and SVG) that
> > will need to be factored in.
> >
> > This does not mean that the HTML working group or SVG 2 working group cannot
> > publish the documents. This is a coordination discussion that pools the
> > right resources. I can tell you that Steve Faulkner and I already coordinate
> > on edits for ARIA support in HTML 5.1 and SVG2.
> >
> > 5. Post CSUN conference we will develop the logistics as to where we put
> > these documents - Github location, etc.
> >
> > Note: our goal should be to get these done in time for HTML 5.1 CR end at
> > the end of 2016 as a minimum. I would like SVG2 sooner. Without this pooling
> > of resources and coordination in APA (formerly PF) I don't see it happening.
> >
> > Janina, if you could ensure that this is discussed in the HTML a11y task
> > force this Thursday it would be much appreciated.
> >
> > Best Regards,
> > Rich
> >
> >
> > Rich Schwerdtfeger
> 
> 
Received on Sunday, 9 March 2014 19:08:44 UTC

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