W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2000

RE: Request for site review

From: Bruce Bailey <bbailey@clark.net>
Date: Mon, 17 Apr 2000 10:47:03 -0400
To: "Marjolein Katsma" <access@javawoman.com>
Cc: "Web Accessibility Initiative" <w3c-wai-ig@w3.org>
Message-ID: <001101bfa87b$cb95d020$53fe330a@msde>
Dear Marjolein,

I don't disagree with you about the byte bloat of the Sailor Page.  Like I
said before, I don't have much influence on correcting that particular

I would mention that my computer ain't all that great.  After your earlier
comments I tried the Sailor site on an even older system with dial-up, but I
didn't experience problems that were nearly as bad as what you described.
After I let it finish loading (yawn), I did NOT have any lag problems with
the onMouseOver content.  (This was on a 120MHz system, 32MB RAM, but using
IE 5.)

My most recent comments to Jim are about onMouseOver behavior in general,
which is designed to be fluid -- even if it is not always that way in

> -----Original Message-----
> From: Marjolein Katsma [mailto:access@javawoman.com]
> Sent: Monday, April 17, 2000 10:19 AM
> To: Bruce Bailey; jim@jimthatcher.com
> Cc: Web Accessibility Initiative
> Subject: RE: Request for site review
> Bruce,
> At 09:36 2000-04-17 -0400, Bruce Bailey wrote:
>> I agree with your meta over-all view of this, but visually, with
>> a mouse and
>> the context sensitive onMouseOver content, the two middle items happen so
>> fluidly (and possibly without planning and/or much thought on the part of
>> the user) that the operation is very condensed and feels more like one
>> operation than two.
> Maybe it's fluid on your computer - it certainly isn't on mine.
> Yes, maybe if you have the latest, fastest hardware and a video
> with lots of memory - but not everyone has that (or can afford
> it). Like I mentioned before, it's so slow that the mouse
> continues moving when the submenu and arrow on the main one stops
> displaying.
> Try it on another computer (mine is a P166 with 64M RAM and the
> video has 2M).
> Testing tip: put the site (or at least the part you need to test)
> on a floppy disk and load the site from there. It will give you
> approximately the access speed of a 28.8K modem (which is not
> what's in the shops now - but it is what many people still use,
> or the effective speed they can get out of their provider...)
>> The mechanics of activating the onMouseOver content is
>> completely contained within the "action" of selecting the
>> original target.
>> In fact, the visual user has little choice but to be exposed (however
>> briefly) to the additional content.
> Nope - I can just click - on a link that doesn't have an arrow.

Sure, and I can follow a link before the onMouseOver content loads too!
I think you know what I meant.  I was referring to links with onMouseOver
content defined for them!  I was also trying to highlight a problem with the
somewhat vague term "action".
Received on Monday, 17 April 2000 10:50:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:35:56 UTC