W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2013

keyboard focus questions (I am working on tabindex and sequential focus navigation)

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Sun, 20 Jan 2013 17:00:08 -0600
To: public-svg-wg@w3.org
Cc: Kelvin Lawrence <klawrenc@us.ibm.com>
Message-ID: <OFFADC7B99.E30A4C04-ON86257AF9.007D7B72-86257AF9.007EBD1A@us.ibm.com>


So, I am trying to be consistent with what is in HTML5 but I have some
questions.

   Does the group want focus events that are not handled within the SVG
   document to bubble up into a containing DOM (HTML) if they are not
   handled within? I guess this would be the case for any events. We are
   sharing the same DOM.
      Same goes for an SVG element embedded in another SVG element.
   Does the group want to support access keys. Personally I think they are
   terrible and should never have been created? I am not a big fan of them
   and I know of no IBM group that uses them. As we go to mobile I think
   they will go the way of the bit bucket. (my 2 cents),
   Do people agree the anchor element in SVG should be in the keyboard
   navigation order like HTML? It is the only active element, by default, I
   am aware of.
   In terms of keyboard navigation, if we are being used inside of a parent
   document that also supports tabindex I believe we should be included in
   the sequential navigation order so at to have seamless navigation. Do
   you all agree? This happens today with IFrames and is a good
   accessibility practice.
   Do folks want to go to the same degree of specification whereby we
   dictate the processing of keyboard events like they do in HTML5?

I will have lots more questions.



Rich Schwerdtfeger
Received on Sunday, 20 January 2013 23:01:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:16 UTC