trevor

jake <jake@gododdin.demon.co.uk> wrote in
news:dikRUvKINqdCFwaf@gododdin.demon.co.uk:

ok Jake, it sounds like you have probably more experience with this and i
appreciate your input, just please feel free to contribute more than one-
liners in the future. i'm not here trying to play expert, i'm sharing my
findings as they occur and hoping other developers and blind surfers can
be found to participate. hint hint.

you hit it on the head when you said i need to be specific about the tool
in use. what we really need is a chart showing the various capabilities
and pitfalls of the speech tools and an idea of the marketshare.
otherwise we'll end up with this yes-it-do or no-it-don't format which
has gotten old in about 30 seconds. other responses inline.


> Text-to-speech engines, surely?
>

yes, speech recognition software, also called speech-reading or text-to-
speech software.

>
> Probably not -- if they're actually marked up as <Hn></Hn>. A problem,
> though, if they're simply stylized in the CSS.

ok, what the heck is <Hn>? are you specifying an arbitrary <h> tag or is
this some demonological proprietary tag? we are so NOT going down any
proprietary roads here no matter what the installed base.

>
> (You need to be specific about the screen-reader or talking browser
> you're referring to.)
>

we all do. would you by chance be willing to tell us what you know about
the software tools out there? thanks in advance.