RE: Two new sites

> >>On my copy of pwWebspeak, it reads the title tags, too.
> >
> >This doesn't seem like the right way to handle TITLE attributes aurally.
> >The TITLE attribute gives "advisory information" [1], so I don't think it
> >should be read without somehow indicating that it's only giving advisory
> >information.
>
> I agree about advisory information. I find the title useful, but not
> something that should be read automatically.

I can agree with the idea of making title reading optional. At present, in
webspeak, it is not. Your example of ABBR is a good one, but raises several
other issues:

1. With title reading ON, should we hear:
"U.S., United States, "
or
"United States, abbreviation U.S."
or
"U.S., title United States"

2. With Title reading OFF, should we hear:
"<auditory cue> + U.S.", replacing auditory cue with either musical note or
voice cue or nothing.

Should the "Detail" function (in webspeak), when selected for "U.S", read
the title to you?

3. Would the "Page Summary" function (in webspeak) list all abbreviated
terms on a page, with definition?


My preference will be to make Title reading optional, and handle the reading
behavior via style sheets.  We'll explore the Summary option a bit more.

Mark




> For example, if I
> use the ABBR
> tag to indicate that U.S. stands for United States (obvious to most, but
> perhaps not to others), pwWebspeak reads "United States U.S."
> every time. If
> it were possible to have some kind of aural clue that a title was
> available
> when the abbreviation or acronym was read, then I could only hear
> descriptions of those that interested me. I know what W3C stands for. I
> don't need to hear it every time. I'll write to the Productivity
> Works about
> this.
>
> Charles Munat
> coder@acnet.net
>
>
>
>

Received on Sunday, 25 October 1998 13:34:44 UTC