W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2003

Re: screen readers for macs - also bobby question

From: David Woolley <david@djwhome.demon.co.uk>
Date: Wed, 12 Mar 2003 07:47:57 +0000 (GMT)
Message-Id: <200303120747.h2C7lvp01293@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org

> spacers, but on ?bobbying? was advised to separate adjacent links with
> something ? and a 1px gif was suggested (and works beautifully).  having

[Obviously incorrectly coded characters replaced with ?.]

To me, these look like tactics for defeating Bobby, not good practice.
As far as I can see, confusing adjacent links is not a problem limited
to screen readers.  To not require proper separation, one would probably
need something like the boxes around links that are displayed (at least
with ghostview) in the PDF version of the HTML specification.  Broken
underlines offer no clue; solid underlines need careful inspection; the
current practice of no underlines doesn't help at all.

Note according to the email header's character set, "bobbying" is surrounded
by a superscript 3 and and a superscript 2 and there is a soft hyphen,
surrounded by spaces between "something" and "and".  At a guess, you've
used a raw Macintosh character set file and sent it with headers suggesting
the more universally supported ISO 8859/1 character set.

I guess that the 2 and 3 are quotes, but I don't know what the soft hyphen
is meant to be.  I don't have the recode utility on this system to fix
it up to see.

Your email content-type header:

Content-type: text/plain; charset="ISO-8859-1"

Valid email formatting requires the IANA name for the Macintosh character
set, although best accessibility practice would be to use ASCII for the
quotes, and probably the HTML entity for the other character, assuming 
it was content, not punctuation.
Received on Wednesday, 12 March 2003 02:48:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:08 GMT