W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2003

Re: Skip Nav (was RE: "Think EUO, not SEO"/Google)

From: David Poehlman <poehlman1@comcast.net>
Date: Sat, 14 Jun 2003 11:30:30 -0400
To: Charles McCathieNevile <charles@sidar.org>
Cc: David Woolley <david@djwhome.demon.co.uk>, w3c-wai-ig@w3.org
Message-id: <000401c33289$e4869740$6401a8c0@handsontech>

There are lots of problems with forcing audio rendering controll down the
pipe though.  What happens if the instructions are garbled?  There is no
fall back if the synthesizer has been handed a mess other than static.
screen readers use internal controlls to recover and to prevent this in the
first place.  Also, If I use aural css, what happens if am viewing rather
than listening?  Let's say for instance, that aural css is the only
presentation mechanism being used.  I have a braille display, I have a
screen and no speech.  It seems as though the content will be quite jumbled
under those circumstances.  AS you also point out, screen readers are used
for multiple activities such as word, irc interacting with media players and
the like.  Aural user agents are confined to one thing and that is rendering
content which is marked up for aural presentation.  To ask a screen reader
to reduce its self to being remotely controlled is to ask it to devolve, not
evolve.

----- Original Message ----- 
From: "Charles McCathieNevile" <charles@sidar.org>
To: "David Poehlman" <poehlman1@comcast.net>
Cc: "David Woolley" <david@djwhome.demon.co.uk>; <w3c-wai-ig@w3.org>
Sent: Saturday, June 14, 2003 11:20 AM
Subject: Re: Skip Nav (was RE: "Think EUO, not SEO"/Google)



Sure. But I would suggest that it is a better idea to think of a future
where styling information can be passed to the synthesiser, than to
think of one where speech synthesisers don't allow customisation of any
sort.

There is a separate question of whether CSS is a good styling mechanism
- for audio browsers I would suggest that it is a good approach, but
what about Window-eyes, which is expected to work with all the
different programs a user runs on their machine? (Actually IMHO if it's
a good enough mechanism for MS Word and my IRC client it probably does
make sense for screen readers too).

cheers

Chaals

On Saturday, Jun 14, 2003, at 16:59 Europe/Zurich, David Poehlman wrote:

>
> in my experience with aural css, it only works with sapi complient
> speech
> synthesizers.  Mine is not sapi complient and in fact, does not even
> relie
> on software except for rudimentary communication.  All the speeking is
> done
> in the box.
--
Charles McCathieNevile                          Fundación Sidar
charles@sidar.org                                http://www.sidar.org
Received on Saturday, 14 June 2003 11:30:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:09 GMT