On Wednesday, Stefan Huszics wrote:
> Thus presumably there needs to be a high level of optimization to get a screenreader
> to work with a browser in the first place.
Really? Opera 6 (probably IE as well) was supposedly very accessible to
screen readers (a disabled person was complaining about the lack of screen
reader support in Op7b1).
> Thus making sure a screenreader gets access (via the brower) to the info specifically
> designed for aural browsing seems like a very logical step in that
> optimisation effort.
That would require work from the visual browsers, and do they care?
>> No one includes aural CSS anyway
> Wow, that's a greate argument for continuing to not adding it...
It's not my argument, but it's what I think is part of the reason why
screen readers generally don't implement CSS.
Kevin W :-)