- From: Jim Ley <jim@jibbering.com>
- Date: Thu, 31 Jan 2002 14:32:39 -0000
- To: "WAI Mailing list" <w3c-wai-ig@w3.org>
"Harry Woodrow": > If I cannot read where I am going how can I know to click there? Can you provide a screenshot, if you aren't willing to provide me with the information to recreate your scenario? > Does the user have to write a css for every page? Of course not, why would they? >....the default one should be enough. The default one in browsers is flawed where CSS-P is concerned, is that a failing with CSS-P or those browsers? > Whether you wish to make it accessible to users is up to you. I merely > pointed out as you had asked the conditions that in my opinion as a user I > felt inacessible. I have only asked for you to explain how it is inaccessible - if I asked you to complete the goal of say finding the useful addresses, which is in the information office - could you do it? what prevents you of achieving that goal? > In my > opinion expecting the user to click on a blue and black mess of lines is not > a normal user choice. The user chooses the colours. If it's just the CSS-P problem with your browser (which I've explained.) Are you suggesting that CSS-P should not be used as it's not accessible - In WCAG 1, we're told to use W3 technologies as they have built-in accessibility technologies, CSS-P is a W3 technology. Checkpoint 3.3 is "Use style sheets to control layout and presentation. [Priority 2] " Is this checkpoint flawed as CSS-P makes pages inaccessible? CSS is also advocated for layout in WCAG 2.0 - Is CSS for layout wrong, or is your User Agent not configured optimally? - I've provided the simple steps you need to overcome the flaw in your UA (and it's not a page specific fix, it's a fix for your UA.) Jim. (I am subscribed to the list, copying me in on the post is unnecessary.)
Received on Thursday, 31 January 2002 09:34:27 UTC