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