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

Re: Accessibility API Mappings - location in Github?

From: Michael Cooper <cooper@w3.org>
Date: Mon, 02 Jun 2014 21:54:18 -0400
Message-ID: <538D2ACA.2060402@w3.org>
To: "jason@accessibleculture.org" <jason@accessibleculture.org>, Steve Faulkner <faulkner.steve@gmail.com>, "Robin Berjon (robin@w3.org)" <robin@w3.org>, Joseph Scheuhammer <clown@alum.mit.edu>
CC: "public-html-admin@w3.org" <public-html-admin@w3.org>, W3C WAI Protocols & Formats <public-pfwg@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On 02/06/2014 9:23 PM, jason@accessibleculture.org wrote:
> Robin, Michael, Steve, Joseph,
> What do you think? Where do we want to put these things?
> I think it makes sense to keep all three (Core, HTML, SVG) mapping 
> docs together in the same repo as they can easily reuse shared styles 
> and scripts, e.g. show/hide table columns and details/summary.
Yes, that is highly desirable. The ARIA-related documents pull content 
from each other (to generate proper cross reference links) as well as 
share tools, so it's desirable to have them all in one repository.
> The recently renamed “Core Accessibility API Mappings 1.1” document 
> currently resides in an “implementation” folder under the "w3c/aria" 
> tree [1].
> What is presumably a placeholder for the SVG mapping guide is in an 
> “svg” folder under the "w3c/aria" tree [2].
These documents are part of a deliberate effort to address different 
host languages better with ARIA. But because of their close relationship 
to ARIA and to each other in terms of what they do, it made sense to us 
to put them in the w3c/aria repository together.
> The yet to be renamed “HTML to Platform Accessibility APIs 
> Implementation Guide” lives in its own "w3c/html-api-map" tree [3].
> There’s a recent new tree for the PFWG [4]. Might this be a good 
> location for these three and any future mapping guides?
This is meant for PFWG-developed documents *besides* ARIA. The thinking 
is that ARIA has become a whole suite of documents and is of wider 
interest than just of the PFWG, so makes sense to have a dedicated 
repository that's not inherently associated with a particular WG. The 
w3c/pfwg repository is for other things that don't need the close 
relationship to ARIA.
> Or do we start a whole new tree, e.g. “w3c/a11y-api-map” and move 
> everything there?
I wouldn't want to do that, because it loses the benefit of shared 
resources that putting them all in the w3c/aria repository would bring.
> Without wanting to proliferate trees under the w3c repo, I think my 
> preference is nonetheless to start a new one. But I’m easily swayed.
So in sum, my preference is to put all these docs in the w3c/aria 
repository so we can keep them consistent with each other and share 
tools most easily. Editors of the various specs from different Working 
Groups can be given access to that repository as needed.

> [1] https://github.com/w3c/aria/tree/master/implementation
> [2] https://github.com/w3c/aria/tree/master/svg
> [3] https://github.com/w3c/html-api-map
> [4] https://github.com/w3c/pfwg
> Jason Kiss
> jason@accessibleculture.org <mailto:jason@accessibleculture.org>
> http://www.accessibleculture.org
> On 28/05/2014, at 6:48 am, Paul Cotton <Paul.Cotton@microsoft.com 
> <mailto:Paul.Cotton@microsoft.com>> wrote:
>> >3. Start with the following editors (as a minimum) as we who have 
>> signed on as editors:
>> ...
>> >- HTML5.1: Steve Faulkner, Jason Kiss, and Alexander Surkov
>> The HTML WG and PF WG Chairs have discussed the work outlined in 
>> Richard’s email with the current Editors of the HTML WG “HTML 5 to 
>> platform Accessibility APIs Mapping guide” [1] and have decided to 
>> appoint Jason Kiss and Steve Faulkner as Editors of the proposed new 
>> “HTML 5.1 User Agent Implementation Guide”.
>> In doing so we wish to thank Cynthia and Alexander for their work as 
>> Editors on the “HTML 5 to platform Accessibility APIs Mapping guide” 
>> [1] and look forward to their participation and contributions to the 
>> new specification.
>> Jason and Steve should now work with Robin Berjon to decide on a 
>> Github location for the proposed new “HTML 5.1 User Agent 
>> Implementation Guide” and should work with the A11Y TF and/or PF WG 
>> to progress the work as outlined in the plan given below.
>> /paulc
>> HTML WG co-chair
>> [1] http://www.w3.org/TR/html-aapi/
>> Paul Cotton, Microsoft Canada
>> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>> Tel: (425) 705-9596 Fax: (425) 936-7329
>> *From:*Richard Schwerdtfeger [mailto:schwer@us.ibm.com]
>> *Sent:* Thursday, April 03, 2014 1:47 PM
>> *To:* public-html@w3.org <mailto:public-html@w3.org> WG; HTML 
>> Accessibility Task Force
>> *Cc:* W3C WAI Protocols & Formats; janina@rednote.net 
>> <mailto:janina@rednote.net>; jbrewer@w3.org <mailto:jbrewer@w3.org>
>> *Subject:* HTML 5.1 User Agent Implementation Guide (formerly the 
>> HTML 5 to platform Accessibility APIs Mapping guide) Going Forward
>> Moving toward HTML 5.1 we will produce a minimum of 3 user agent 
>> implementation guides. For those new to this these are the 
>> accessibility API mapping guides that browsers must follow in order 
>> to support a host language or cross-cutting markup like WAI-ARIA. The 
>> ARIA 1.0 User Agent Implementation Guide, now a W3C Recommendation 
>> (http://www.w3.org/TR/wai-aria-implementation/), is the first 
>> industry document to achieve do this.
>> Producing documents like this is essential as it allows us to 
>> normatively ensure that what we put in content will work with 
>> assistive technologies
>> across multiple operating system platforms.
>> Going forward we must produce a normative implementation 
>> specification for both HTML 5.1 and SVG2. Furthermore, we have a 
>> convergence of HTML markup in SVG 2 so the timing is excellent. 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.
>> I have met with editor stake holders and we have produced a draft 
>> outline for 3 specifications which the editor stake holders have 
>> agreed to - as a solid starting point.
>> The following is our plan:
>> 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 1.1 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) will 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 (as a minimum) as we who have 
>> signed on as editors:
>> - Core User Agent Implementation Guide (based on current ARIA 1.0 
>> Implementation Guide but for ARIA 1.1): Joseph Scheuhammer
>> - HTML5.1: Steve Faulkner, Jason Kiss, and Alexander Surkov
>> - SVG2: Rich Schwerdtfeger
>> Shane McCarron will likely appear on some of these documents as an 
>> editor.
>> The HTML5.1 document will be a joint deliverable between PF and HTML. 
>> The SVG2 document will be a joint deliverable between PF and SVG. The 
>> Core document will be produced by PF.
>> 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.
>> 5. We are moving to Respec to create the specifications and Github as 
>> the versioning control system
>> We have had our first editors coordination meeting and have scheduled 
>> bi-weekly meetings. Shane McCarron is converting the existing 
>> documents to be based on Respec and the editors are reading up 
>> Respec. and Github. The ARIA 1.1 specification will also be based on 
>> Respec. and will go to Github versioning.
>> 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. This
>> pooling of resources and coordination in APA (formerly PF) is essential.
>> Best Regards,
>> Rich
>> Rich Schwerdtfeger
Received on Tuesday, 3 June 2014 01:54:27 UTC

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