Posted by jojo on 07/23/06 16:52

Toby Inkster schrieb:
> jojo wrote:
>
>> No, it definitely is *not*. An image just expands the loading time of a
>> webpage, so try to avoid it whenever possible. There is a tag for quotes
>> in HTML (<q>, you already named it...), so why don't you use it?
>
> Do you actually understand what a pull quote is?!

Yes, I do.

> A pull quote is a part of the text which has been duplicated and pulled
> out of the normal flow. If you include this content in a Q element amongst
> the normal flow of text then a non-CSS browser, or a screen reader, will
> read the pull-quote mid-flow, which will be confusing for the reader. By
> including it in an image with alt="", the pull-quote becomes entirely a
> matter of presentation, which is how things should be.
>
> Consider the following in a screen reader or, say, Lynx:
>
> http://examples.tobyinkster.co.uk/pull-quotes/1.strict
> http://examples.tobyinkster.co.uk/pull-quotes/2.strict
>
> There is a blue pull-quote fairly early on in the text, designed to entice
> the reader to carry on reading. Viewed in Lynx, this causes the second
> paragraph to read as follows:
>
> Where is the party in opposition that has not been decried as
> Communistic by its opponents in power? "The history of all hitherto
> existing societies is the history of class struggles." Where is the
> Opposition that has not hurled back the branding reproach of
> Communism, against the more advanced opposition parties, as well as
> against its reactionary adversaries?
>
> With the quote completely out of place. With the quote included as an
> image, the second paragraph reads as:
>
> Where is the party in opposition that has not been decried as
> Communistic by its opponents in power? Where is the Opposition that
> has not hurled back the branding reproach of Communism, against the
> more advanced opposition parties, as well as against its reactionary
> adversaries?
>
> as it should. The second example makes far more sense to text-based
> browsers, and to screen-readers, so is arguably better for accessibility.
>

Depends on how you place the <q> where it is supposed to be. For example
if you position it absolute a screen-reader or text-browser will
read/view it at the position where it is placed in the code, no matter
where it is placed on the screen in "normal" browsers.

[Back to original message]