W3C home > Mailing lists > Public > www-svg@w3.org > August 2006

Accessibility Features of SVG was Re: should element with focus be within client window?

From: Jonathan Chetwynd <j.chetwynd@btinternet.com>
Date: Sat, 26 Aug 2006 21:52:51 +0100
Message-Id: <D4C28924-1926-4F17-9A68-F97753B27654@btinternet.com>
Cc: <www-svg@w3.org>, "'T Rowley'" <tor@cs.brown.edu>
To: Doug Schepers <doug@schepers.cc>


my error, oops.

things are a little busy here and I read your response
"I'll reply inline..."

however you then didn't reply to a direct question
"should element with focus be within client window?"

so I took your response to mean that you would reply in the future,  
which you appeared not to have done....

thanks for your detailed response.

A few fundamental problem with the w3c process include the failure to  
engage end users, the reliance on corporate funding, the  significant  
jargon hurdle, and indeed the very long delays between publication  
and product.

A simple case being the "Accessibility Features of SVG"

this document can hardly have been considered complete on  
publication, however six years later there is little if any evidence  
of intention to revise, update or supercede. Though perhaps this is  
off-topic for the subject header :-)


Jonathan Chetwynd

On 26 Aug 2006, at 19:29, Doug Schepers wrote:

Hi, Jonathan-

Jonathan Chetwynd wrote:
| Doug and Tim,
| you appear to be describing a different issue.
| the issue is that when using the keyboard (tabbing) with html, when
| focus moves to an element outside the client window, the application
| moves the element into the client window so it can be seen.
| thus the element in focus is always in view.
| (Obviously the mouse user can move an element in focus outside the
| window in many instances.)
| Currently no SVG UA has this behaviour afaik.
| My question is whether the current standards ensure that this
| behaviour in html is replicated with SVG.
| Please note well that this is a very different issue from providing
| the means to search for the area currently in focus.

Tim and I did indeed go off on a different issue, but only after I  
your original question (rather in detail):


The short answer is that navigation and focus (tabbing) are not  
included in
SVG1.1, which means that most browsers won't have them.  They *are*  
in SVG Tiny1.2, which hopefully means that they will be included in  
versions of those browsers.  This includes the behavior you are  
asking for,
which is to change the viewport so that the focused element is always

In the meantime, you can do this with script.

Received on Saturday, 26 August 2006 20:53:03 UTC

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