One of the things we will need to add in SVG2 is tabindex for keyboard
navigation so that we can have a consistent keyboard navigation model
between HTML and SVG. In HTML all elements with the body that are visible
support a tabindex.
Drawing objects, like paths, will need to be keyboard accessible and be
able to support ids, such as in this example:
http://kelvinlawrence.net/svg/animate-spin.html
When we enable content with ARIA we need to be able to reference
interactive elements by IDREF to support ARIA relationships. I this example
we could have an HTML form control that controls the spin rate of the arrow
(aria-controls relationship) or we could have a text label in SVG that
labels it (aria-labelledby). Both would have ARIA relations ships where the
ID would need to be on the path and one would need to be on the SVG text.
Rich
Rich Schwerdtfeger
From: Robin Berjon <robin@berjon.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>,
Cc: Erik Dahlstrom <ed@opera.com>, public-svg-wg@w3.org
Date: 07/27/2012 04:25 PM
Subject: Re: id's in the SVG2 spec
On Jul 27, 2012, at 19:54 , Tab Atkins Jr. wrote:
> On Fri, Jul 27, 2012 at 6:05 AM, Erik Dahlstrom <ed@opera.com> wrote:
>> A thing about the SVG2 draft, I'd be happy if we could make it possible
to
>> reference all sections and paragraphs. For example in some elements that
>> have several paragraphs of requirements most often there's only a single
id
>> on the heading, which isn't good for referencing.
>>
>> So, if you're editing and spot places where we could use some more id's
>> please add them.
>
> Couldn't we just put this into the build process and add generated ids
> to every <p>/etc?
That would be great, but do you have a way of guaranteeing that they remain
stable (enough)?
--
Robin Berjon - http://berjon.com/ - @robinberjon
