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

Re: FW: making applets accessible

From: Leonard R. Kasday <kasday@acm.org>
Date: Tue, 16 Feb 1999 12:31:52 -0500
Message-Id: <>
To: "Silas S. Brown" <ssb22@cam.ac.uk>
Cc: w3c-wai-er-ig@w3.org
Neat!  Yes, that rendered the scrolling ticker at http://www.att.com

For this particular applet one could apply some ad hoc rules to make it
more compact.  Right now it's rendered as

AT&T WorldNet Service growing faster than the industry average

In this special case, you could make the text "AT&T Worldnet..." a link
with the URL on the second line, and discard the third line.  

However, this means we're guessing the semantics and gets away from the
simple algorithm of just listing the applet params.  It would take some
more experiments to find out whether guessing semantics helps or hurts.

As for why you didn't see a ticker at http://www.temple.edu

That's a version that contains frames and a scrolling ticker.  The web
access gateway however goes to the <noframes> version, which doesn't have a

So I guess at this point it doesn't handle frames?


  At 09:19 AM 2/11/99 +0000, Silas S. Brown wrote:
>> But even for applets other than the scrolling ticker, I suggest that 
>> for many applets, it will be useful to list the names and values of the
>> params, at least params that are text or url's.  This is because 
>> applets used by non-programmers will be cannned effects populated with 
>> a list of easy to enter params, like names and colors, not hexidecimal 
>> equivalents of a set of bits.
>I can't find the applet at Temple University but please try the AT&T 
>site with the gateway now and see if it's any help.  (Please use the 
>www.accu.org gateway as the others might not have updated themselves yet 
>and the one on my machine has altifier; you probably only want to test 
>one thing at a time.)
>Here is the code I put in, in case you're interested.  (Of course there 
>is other stuff, like the extra option on the form, the extra bit in the 
>help text and the initialisation of processParams in the query decoder, 
>but you get the idea.)
>if(noApplets && processParams && !stricmp(theTag.getName(),"PARAM")) {
>		const char* v=theTag.getAttribute("VALUE"); if(v) {
>			if(!strnicmp(v,"http://",7)) {
>				HTMLTag tag2("A");
>				tag2.addAttribute("HREF",v);
>				processTag(tag2,htmlLineInput);
>				theEnvironment->h_fputs(v);
>				processTag("/A",htmlLineInput);
>				theEnvironment->h_puts("<BR>");
>			} else if(strchr(v,' ')) {
>				// It's probably text
>				theEnvironment->h_fputs(v);
>				theEnvironment->h_puts("<BR>");
>			}
>		}
>	}
>-- Silas S Brown, St John's College Cambridge UK
>"I know of no way of judging the future but by the past" - 18th century
> American statesman Patrick Henry
Leonard R. Kasday, Ph.D.
Universal Design Engineer, Institute on Disabilities/UAP, and
Adjunct Professor, Electrical Engineering
Temple University

Ritter Hall Annex, Room 423, Philadelphia, PA 19122
(215} 204-2247 (voice)
(800) 750-7428 (TTY)
Received on Tuesday, 16 February 1999 12:31:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:28 UTC