W3C home > Mailing lists > Public > www-svg@w3.org > October 2011

Re: Selecting text in a clipPath: accessibility and advice to search engines

From: Dirk Schulze <vbs85@gmx.de>
Date: Sat, 1 Oct 2011 19:20:21 +0200
Cc: "'www-svg'" <www-svg@w3.org>
Message-Id: <D9914371-CE1A-40CD-A537-A14D652C5A30@gmx.de>
To: David Dailey <ddailey@zoominternet.net>

Am 01.10.2011 um 15:18 schrieb David Dailey:

> In the first example, a pattern containing a bitmap is applied to a text string. In the second, a clipPath containing the text is applied to the image.
> The first has the advantage that the text remains selectable by dragging over it (so that it can be copied to the clipboard), but the second doesn’t. (It also has the advantage of being able to stroke the text.)
> Should text in a clipPath be selectable?

In my opinion clipPaths, masks and filters are pure visual effects. The SVG viewer can't assume that the content of visual effects have any context. Therefor texts that are part of visual effects should not be selectable or searchable. If the visual effect has a context that people with special needs or preferences could be interested in, the author should apply alternative texts (like the 'alt' attribute on <img>). In the case of SVG this can be done with the <title> tag.

This is of course not the case for texts where you apply visual effects like patterns or gradients. They should indeed be selectable. 

But it gets really difficult if you apply filters or clip paths on texts. In WebKit, Batik and Opera you can still select texts where you apply filters, even if you use feFlood or feOffset:

<svg xmlns="http://www.w3.org/2000/svg">
<filter id="filter">
<feFlood flood-color="green"/>
<text y="100" filter="url(#filter)">ABCDEFGHIJKLMNOPQRSTUVWXYZ</text>

But at least the last problem was not part of your question :)

Received on Saturday, 1 October 2011 17:20:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:26 UTC