W3C home > Mailing lists > Public > www-svg@w3.org > April 2008

Re: BPG: more section 3.2 (key nav) comments

From: Erik Dahlström <ed@opera.com>
Date: Thu, 17 Apr 2008 11:01:00 +0200
To: "Simon Pieters" <simonp@opera.com>, "David Bolter" <david.bolter@utoronto.ca>
Cc: "Aaron M Leventhal" <aleventh@us.ibm.com>, w3c-wai-pf@w3.org, www-svg <www-svg@w3.org>
Message-ID: <op.t9qzbyvdgqiacl@gnorps.palace.opera.no>

On Tue, 15 Apr 2008 19:26:05 +0200, Simon Pieters <simonp@opera.com> wrote:

> On Tue, 15 Apr 2008 18:36:20 +0200, David Bolter  
> <david.bolter@utoronto.ca> wrote:
>> Simon Pieters wrote:
>>> On Tue, 15 Apr 2008 16:11:05 +0200, David Bolter  
>>> <david.bolter@utoronto.ca> wrote:
>>>>> tabindex in SVG is spelled focusable='true' and is supported in at  
>>>>> least Opera.
>>>> Is it possible to denote something focusable but not in the tab order?
>>> No, but it would be a straightforward addition to SVG, AFAICT (just a  
>>> new value to the focusable attribute); perhaps we should ask the SVG  
>>> WG about the matter.

I suggest reading a bit here:

Yes, you can define the order of navigation in svg.

>>>> Maybe that question doesn't make sense in SVG world.
>>> I don't see why not.
>>> For reference, the definition is at  
>>> http://www.w3.org/TR/SVGMobile12/interact.html#focusable-attr
>> Thanks for the link. I see the fourth case for the 'auto' value is  
>> "elements that are the 'target' or 'observer' of a 'listener' element  
>> that is registered on one of the following user interface events:  
>> DOMFocusIn, DOMFocusOut, DOMActivate". I suspect this might be similar  
>> to the tabindex="-1" scenario but I don't really understand the case as  
>> described.

Well, that part just says which elements are considered to be focusable  
automatically (without no additional markup), like links for example.

> It's not the same as tabindex='-1'. It's a case where 'auto' is  
> equivalent to 'true', and 'true' means that the element is focusable and  
> in the tab order (whereas tabindex='-1' means that the element is  
> focusable but not in the tab order).
>> Would it have been a good idea to cc the SVG WG on this reply? (I'm a  
>> w3c noob).
> I've cc-ed www-svg now.
>>>> In HTML we use tabindex="-1" for this which allows us to customize  
>>>> keyboard operation of some widgets such as using arrows to change  
>>>> tabs in a tab container.

Well, let us know if the focusable and nav-* attributes together don't  
address your particular use-case.


Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Thursday, 17 April 2008 09:01:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:18 UTC