W3C home > Mailing lists > Public > www-style@w3.org > July 2001

RE: code for visually impaired users

From: Dave J Woolley <david.woolley@bts.co.uk>
Date: Wed, 18 Jul 2001 15:34:46 +0100
Message-ID: <81E4A2BC03CED111845100104B62AFB50102A842@stagecoach.bts.co.uk>
To: "'www-style@w3.org'" <www-style@w3.org>
> From:	Manos Batsis [SMTP:m.batsis@bsnet.gr]
> 
> It's all on the css specs. If you are tired of reading long documents
> though,  just take a look on the stylesheets used in the W3C pages.
> 
[DJW:]  I don't believe it is.  Although phrased as
an (off topic) "how to" question, this is implicitly 
proposing something weaker than a media type.  Currently
the choice is between media types of screen, tty and aural.
What I think is being asked for is something that is
closer to screen than tty and is configured by the user
of a user agent that is fully capable of handling the 
screen media type.

My view is that it would be a pointless exercise, as
virtually no-one uses the existing media types, and
most write as though there could be:

* { display: none }
@screen {
/* enable display for everything */
}

rather than writing most of their rules under @screen,
which what they usually mean.

Consequently, it seem rather unlikely that browser 
suppliers would implement the necessary support.

As far as I can tell, even Mozilla doesn't have support
for sticky selection of named style sheets, which is how
one might emulate this now with HTML.

(Server side solutions are a different question.)
-- 
--------------------------- DISCLAIMER ---------------------------------
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of BTS.

>  
Received on Wednesday, 18 July 2001 10:35:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:10 GMT