Re: [css3-reader] compared to aural

> What would the difference be to having a 'reader' media type, to the 
> currently existing 'aural' media type? Surly screen readers should be 

Because aural has been deprecated in CSS2.1, although in a 
non-standard way.  Normally deprecated material should indicate
the construct that makes it unnecessary.  CSS2.1 does indicate
the possibilty of a speech media type doing that, but can't actually
quote it as the replacement because it is still under development.
That puts the whole area into limbo rather than indicating a
transition.

CSS2.1 also tries to describe it's description of aural as non-normative,
but at the same time saying that any use of aural will have a meaning
it then describes.

Finally it fails to say that it is deprecated (rather than being
deferred) in the summary of changes.

Based on last call version of CSS2.1.

Received on Friday, 27 February 2004 02:51:41 UTC