>> 12/25/00 Do start/value attributes for <ol> <li> elements in CSS >>break WCAG 1.0 checkpoint 6.1 which requires that the document be >>readable w/o stylesheets? >><http://lists.w3.org/Archives/Public/w3c-wai-gl/2000OctDec/0965.html> > >In general I think there is an issue that we should be clear that >using style mechanisms to provide content is breaking the "cardinal >rule" of seperating presentation and content. The list items are still marked up inside <li> and </li>. It may be inconvenient to lose the start value in no-stylesheet viewing, but the structure remains. Also, could I just say here that it is high time we stopped pretending there are very many devices out there that cannot understand stylesheets? It is absurd to hamstring 95% of Web-browser users (it's more like 98%) because Lynx and a few non-Web devices do not understand CSS. If anything, we should require that tools and devices *understand* CSS, not force authors to twist themselves to accommodate backward or maldesigned devices that don't. And this is coming from someone who uses Lynx for hours a day and owns a Newton. It's time to grow up a little. Technology marches on. -- Joe Clark | joeclark@joeclark.org | <http://joeclark.org/access/> Accessibility articles, resources, and critiques || "I can't pretend to understand the mind of Joe Clark" -- Larry GoldbergReceived on Monday, 26 November 2001 21:36:41 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:16 GMT