W3C home > Mailing lists > Public > www-svg@w3.org > November 2002

Re: svg textLength issue (and a little thing about use...)

From: Jim Ley <jim@jibbering.com>
Date: Wed, 13 Nov 2002 16:46:08 -0000
Message-ID: <02c301c28b34$2c179b20$ca969dc3@emedia.co.uk>
To: <www-svg@w3.org>

"Thomas E Deweese" <thomas.deweese@kodak.com>

> It isn't clear to me how one would express a
> global zoom factor in CSS (what part of the document would you zoom
> on?).

Some appropriate default - there is the same problem for the visually
impaired though if we have them zoom in manually they can't identify any
of the content so they don't know where to zoom, it's also an extremely
inefficient barrier to accessing the content, to force the user to pick
somewhere at random to then zoom the content 2 or 3 levels just so they
can see where they are, at least if it zooms somewhere by default, it's
only panning that's necessary.

In my HTML user agent, I have a zoom css property, and I use body {
zoom:200% } on certain sites it shows the top left hand quarter of the
area it would've otherwise shown without the zoom*, that seems an
appropriate default for an SVG zoom to.

>     But the 'accessibility issue' posed by text-length is really a red
> herring - The real issue is SVG is not designed to robustly handle
> large changes in font-size (or lots of other things in the document).

Which is why I don't see it beneficial to give the users the ability, we
shouldn't confuse users by giving them tools which in using they make
things worse for themselves.  Since as you say SVG gives information by
position, we should only allow authors to change the position of things,
the scenarios where users benefit from changing text-size are minimal,
and the risks considerable - protect the user - don't let them!


* actually I use 120% but that 200% is easier demo with the quarter.
Received on Wednesday, 13 November 2002 11:48:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:46:54 UTC