W3C home > Mailing lists > Public > w3c-wai-er-ig@w3.org > February 1999

Re: FW: making applets accessible

From: Silas S. Brown <ssb22@cam.ac.uk>
Date: Wed, 17 Feb 1999 15:26:25 +0000
To: "Leonard R. Kasday" <kasday@acm.org>
CC: w3c-wai-er-ig@w3.org
Message-Id: <E10D8rn-0006VU-00@violet.csi.cam.ac.uk>
> Actually it did work.

On www.att.com yes, but not on the Temple site I'm afraid.  www.att.com 
has the URLs in separate parameters, whereas Temple embeds them in the 
same parameters as the text.

> BTW, the <A...>'s contain onMouseOver="window.status='etc...  What are they
> for?

Normally when a sighted user moves the mouse over a link, the status 
window displays the URL that the link points to.  If that link has been 
redirected through the gateway, the URL will be awfully long (including 
all the options etc) and would not fit in the status window.  The 
onMouseOver stuff makes it look like it's not redirected, except I put 
the word "Access" in just to make sure there's no confusion.

It turns out that most of the people using the gateway around here are 
fully sighted Japanese (and a few Chinese) who want to look at those 
pages without needing the fonts (the gateway can substitute a load of 
gif files and handle the encoding detection automatically).  And then 
there are one or two sighties who use it just because they like their 
paragraphs indented rather than a line left between them.

Also, I must admit, I've used the status window before.  I do have 
partial sight and I don't always want to work quite like totally blind 
people do; this is the advantage of having something that is 
configurable.

Regards

-- Silas S Brown, St John's College Cambridge UK http://epona.ucam.org/~ssb22/

"He that is slow to anger is better than a mighty man, and he that is
controlling his spirit than the one capturing a city" - Proverbs 16:32
Received on Wednesday, 17 February 1999 10:26:44 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:10:32 GMT