Hi all,
I've updated the script and taken in to account the contrast factor as well
as the accessibility issue.
If I were to take it to the exterme, I'd dynamically generate the control
links.
As it is, i've chucked them into a separate <div>
http://www.grafx.com.au/wip/marquee.html
All comments welcome.
Cheers ;o)
Richard
----- Original Message -----
From: "Richard Czeiger" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 08, 2006 8:52 AM
Subject: Re: [WSG] XHTML Marquee
Aha! Thanks Christian!
This was the kind of accessibility suggestion I was looking for.
I sometimes forget about the keyboard test when I get into depending on
the NILS and FireFox extensions.
I'll see if I can work in two keyboard links: toggle stop/start and speed
up/down
Is it OK to have a toggle button for start/stop?
Also would it be acceptible to have the 'speed control' operate so that it
moves to the next level like this:
default speed (5)
6
7
8
9
10
1
2
3
4
That way, I'd only need one button instead of two (an up AND a down)
R :o)
----- Original Message -----
From: "Christian Heilmann" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, September 07, 2006 9:09 PM
Subject: Re: [WSG] XHTML Marquee
I think one animation going across the page isn't going to kill people.
Like most scrollers, mousing over it pauses the animation.
And how do I do this with a keyboard? I'm not saying your
implementation is not good (actually it is very thorough), I'd just be
_very_ careful about claiming something is "accessible", as that is a
very subjective matter. Technical accessibility is just assumption.
While I agree that everything should be in moderation, many people seem
to
go the extreme: no flash, no animation, no movement.
I think there's room here to have a balance.
No, you just need to provide a means to stop and to change the speed.
Both is very easy to achieve with JavaScript and two links - which are
also keyboard accessible.
In terms of 'crashing' your browser, this is why I'm hoping that the
information is available whether you have CSS or JavaScript turned off.
If anyone thinks it's inaccessible, I would be eager to here why and
hope
that you can offer alternatives to make it accessible.
That is the Java Applet, not your example. For some reason their
classes never load properly.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
