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

RE: freezing text and background sounds

From: Charles (Chuck) Oppermann <chuckop@MICROSOFT.com>
Date: Thu, 28 May 1998 12:22:33 -0700
Message-ID: <E3A3FFB80F5CD1119CED00805FBECA2F03804669@red-msg-55.dns.microsoft.com>
To: "'jkrieger@cast.org'" <jkrieger@cast.org>, w3c-wai-gl@w3.org
Java is not the major issue with moving or blinking objects - it's with
<MARQUEE> and <BLINK> tags.

On the Java side - screen readers running Active Accessibility already have
object model access to <MARQUEE> and <BLINK> and to Java applets running
with Microsoft's Virtual Machine.  Current screen readers like Window-Eyes
2.1 and WinVision 97, to name a few,  already take advantage of this.  

-----Original Message-----
From: Josh Krieger [mailto:jkrieger@cast.org]
Sent: Thursday, May 28, 1998 6:12 AM
To: w3c-wai-gl@w3.org
Subject: freezing text and background sounds

> 3.4. [REQUIRED] Provide a mechanism for the user to freeze all 
> moving or blinking objects, particularly those that contain text.

This should be an INTERIM guideline as hopefully at some not too
distant time in the future ATs will be able to interrogate 
Java applets and a browser's document object model.

> 5.[RECOMMENDED] Provide visual notification of sounds that 
> are played automatically.

Like the comment regarding the MARQUEE element, the IE 3.0/4.0 
element BGSOUND is not a supported element in HTML 4.0. This should
be mentioned. 

Josh Krieger
Received on Thursday, 28 May 1998 15:21:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:27 UTC