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

RE: Are Small Text buttons level 2 compliant

From: Dave J Woolley <david.woolley@bts.co.uk>
Date: Tue, 26 Sep 2000 19:06:03 +0100
Message-ID: <81E4A2BC03CED111845100104B62AFB5824A37@stagecoach.bts.co.uk>
To: "'WAI'" <w3c-wai-ig@w3.org>
> -----Original Message-----
> From:	Kynn Bartlett [SMTP:kynn-edapta@idyllmtn.com]
> 
> 
> There are huge problems with using HTML + CSS as a substitute for
> graphical buttons; namely, they don't work.  CSS has yet to be
> 
[DJW:]  I tend to agree with this as well.  CSS failed
to achieve its aims because there was no commercial
imperative to implement it completely and accurately,
but there was one to implement certain features.  As
a result, it is one more thing that one was to allow
for and work round broken and incomplete implementations
that will mean that CSS will never fulfill its aims until
most current GUI browsers have disappeared.

(However, I'm fairly sure that custom fonts, one of the main
reasons for text as graphics, will degrade gracefully even
across broken CSS implementations.)

BUTTON was always ill conceived, because of the lack
of backward compatibility, and because the market had
already settled on less structured solutions, even
before IE4 mis-implemented it (I actually tested HTML
to be used for an exhibition in an HTML 4 only envrionment
on Lynx, and had the buttons work, only to find that they
didn't work with IE!)  The market is also concerned about
backward compatibility to Netscape.
-- 
--------------------------- DISCLAIMER ---------------------------------
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of BTS.
Received on Tuesday, 26 September 2000 14:06:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:49 GMT