|
|
Posted by William Gill on 12/04/07 02:42
André Gillibert wrote:
>
> I tested one screen reader (JAWS) combined with Internet Explorer.
> The document is read interactively. There's a key to read the next or
> previous paragraph, keys to jump to a section defined by a header
> level.
> There's a heading navigation dialog box to see the structure of the
> document and jump to a specific place.
>
OK, This makes some sense, the browser uses headers to delimit each
logical section of the "copy", and lets the user decide the delivery
sequence. What happens in logical blocks without headings, like
navigation? Are they automatically delivered in logical units in the
order they are encountered (FIFO)?
>> Better still, is there a utility to convert the html to a simple text
>> transcript.
>
> This wouldn't be equivalent to a screen reader such as JAWS.
> However, it may be possible to extract the data of a HTML document,
> deleting navigation bars and decorative things. I don't have a
> specific algorithm to recognize these things.
> Moreover tables and divisions will be difficult to interpret.
I could use a text only browser like Lynx to get a rough extraction, but
I was hoping to be able to review my html and get an estimation of how
it is "seen" by users relying on this technology. A transcript would be
a text copy of what the user would hear, in the order the user hears it.
Guess I'll have to assume that if my code is fairly logical and
reasonably semantic, whatever algorithm they use, it should be rendered
in an understandable manner.
Thanks.
Navigation:
[Reply to this message]
|