Thank you. I will probably ask for input on sections by people in the not
too distant future. ... specifically getting agreement on what minimal
information causes an accessible to get created for an SVG host language
element and then name computation. The name computation I am going to work
on once I get more of the link issues resolved. Joseph has been doing a
bang up job making sections of the Core spec. more generic so that I can
cut content out and refer to the core - in particular focus handling.
Rich Schwerdtfeger
From: James Craig <jcraig@apple.com>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc: SVG WG <public-svg-wg@w3.org>, SVG public list
<www-svg@w3.org>, W3C WAI Protocols & Formats
<public-pfwg@w3.org>
Date: 07/29/2014 02:32 AM
Subject: Re: SVG2 Accessibility API Mappings spec.
Great to hear, Rich! Please let us know when you think it's ready for
review.
On Jul 25, 2014, at 3:09 PM, Richard Schwerdtfeger <schwer@us.ibm.com
> wrote:
I pushed a VERY early editors version of this on github. As we
generalize the Core Accessibility API mapping more we will be able to
refer back to it.
http://rawgit.com/w3c/aria/master/svg/svg-implementation.html
I am not putting this out to ask for review but more to show we are
putting a stake in the ground.
Rich Schwerdtfeger
