Re: Acessibility of <audio> and <video>

Dave Singer wrote:

> Note that the current design does allow for fall-back content.

Yes, but according to Anne v. K., that (in the
current editor's draft of the specification),
fallback can be reached only if the browser
itself does not support <video> (or <audio>),
rather than through a user preference that says
"I am unable to benefit from rendered video;
please offer me the fallback content whenever
a <video> element is encountered" (this is an
extrapolation from Anne's position, not his
exact words of course).  This seems to me to
force those who cannot see (or hear) to use
what will almost certainly be an inferior browser
(it seems safe to assume that most leading-edge
browsers /will/ support <video> and <audio>,
if ever HTML 5 becomes a reality), just in order
to be able to gain access to the fallback content.

Philip TAYLOR