SVG2 Accessibility API Mapping specification

Michael,

In our walk-through today, the SVG Accessibility Task Force has determined
that the SVG2 Accessibility Mapping Specification be called the SVG
Accessibility Mapping Specification.

The reason for this as they want the mapping specification to follow what
is implemented in today's browsers. So, any SVG markup that goes into a
browser today would need to conform to our mappings.

I am making changes to the mapping specification that do address this. At
the moment we do point to the actual SVG2 specification which does have a
version in the name and URL. That can be addressed at a later date perhaps.

I will place text at the beginning of the mapping specification that states
that this specification applies to all SVG and that it reflects what must
be supported in today's browsers.

I don't know how this effects the charter but this will be the name of the
specification that we produce. I should also point out that Steve Faulkner
has taken the SVG ARIA section from the SVG2 spec. and created a module for
ARIA 1.1. So, this is a very good step forward.

I am working through the great comments I received so that we can get a
first public working draft out in February. The feedback thus far was
exceptional!


Best,
Rich


Rich Schwerdtfeger