- From: Frank Tobin <ftobin@uiuc.edu>
- Date: Tue, 10 Apr 2001 12:08:35 -0500 (CDT)
- To: Kynn Bartlett <kynn@reef.com>
- Cc: <w3c-wai-ig@w3.org>
Kynn Bartlett, at 09:50 -0700 on Tue, 10 Apr 2001, wrote: In my opinion, while the ability in CSS to override creator styles is a nice thing, I feel that it's not a good "solution" because it requires users to understand how configure their software in a way that is not very apparent nor easy to do. This introduces an extra hurdle to accessibility -- "hi, user, you need to learn CSS to write yourself a stylesheet" or even "hi, user, you need to learn how to choose your own stylesheet after downloading it" if using a library of CSS written by someone else -- and puts too much _technical_ burden on the end users. There is an argument, though, that only with more knowledge, may users be able to free themselves. In order to effect styles that CSS is capable of accomplishing, users need to be able to express what they want to have done in some coherent manner. To try to come up with a means for users to express what they want done with their personal stylesheets without actually haivng a working of CSS, would be, in effect, coming up with a language parallel to CSS. And given that CSS is itself a fairly minimal, simple language for the most rudimentary tasks, I think it is a good syntax for users expressing the style they want. Sure, there may be frontends for manipulating a CSS file, but the basic notion of how CSS applies to elements, and what elements exist, are fairly intrinsic applying CSS effectively. -- Frank Tobin http://www.uiuc.edu/~ftobin/
Received on Tuesday, 10 April 2001 13:08:36 UTC