- From: Joe Clark <joeclark@joeclark.org>
- Date: Sun, 25 Jan 2004 17:17:23 -0500 (EST)
- To: WAI-GL <w3c-wai-gl@w3.org>
> On the other hand, saying that something is accessible because it will work > on just one OS and with one piece of AT is also not appropriate. That rules out absolutely *anything* WCAG WG wants to custom-craft for Jaws and IE. Remember that when you spend hours dicking around with remixable link and heading lists. Anyway, somebody's gotta be the leader in supporting a feature. Let's take an hypothetical scenario with a real-world basis. Arguably only one browser supports CSS3 text-shadow, and that is Safari. (Theoretically any KDE engine could do so; that could include OmniWeb.) If we decided text-shadow were necessary for accessibility-- this is an hypothetical scenario here; work with me-- would we ban it just because only Safari could handle it? -- Joe Clark | joeclark@joeclark.org Author, _Building Accessible Websites_ <http://joeclark.org/access/> | <http://joeclark.org/book/>
Received on Sunday, 25 January 2004 17:19:07 UTC