I've been following this thread from the sidelines but now I will jump in. It is possible that CSS is the most fundamentally important part of this entire undertaking because the separation of "content", "structure" and "presentation" is vital to almost all aspects of accessibility. *HOWEVER* The "until User Agents comply" problem makes Rob's points significant. If we make a 20 mph speed limit that almost everybody ignores, the full implementation of this stuff will be jeopardized. I suggest an erratum for checkpoint 3.3 that includes "amnesty" for otherwise conformant sites - until User Agents comply - but strongly "denounce" the distribution of browsers that don't treat CSS well. There are hundreds of millions of Websites and probably less than a hundred browsers. It is a bit Draconian to put P2 (and AA conformance) on something that will be a while coming online without somehow acknowledging that you're not a sociopath if your site uses <i> and <b> or even (shudder!) <font>. I cannot agree however that nobody knows what "deprecate" means. -- Love. ACCESSIBILITY IS RIGHT - NOT PRIVILEGE http://dicomp.pair.comReceived on Thursday, 15 July 1999 09:21:36 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:00 GMT