> has anyone thought of including a way in HTML [...] to tell a voice gen
> browser how to inflect the next phrase (rather than using it's defaults),
> thus identifying links in the document for those who can't see
> the screen
Is there any particular reason a voice gen browser cannot just use the <a> and
</a> tags to identify links? This seems to me a simpler and better solution and
is I presume what existing voice browsers use.