Thread Subject: Re: General Issues:Speechinterfacesandequivalent facilitation
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Debbie Cook
Date: Wed, Jan 10 2007 4:50 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: David Poehlman: "Re: General Issues:Speechinterfacesandequivalent facilitation"
- Previous message in thread: Gregg Vanderheiden: "Re: General Issues:Speechinterfaces and equivalent facilitation"
- Messages sorted by: Author | Thread | Date
"Is refreshable braille support something we feel is a requirement?
I can waffle on this--but if I were deaf/blind I'd not waffle one bit."
The issue is that in a PC type application both speech and Braille support
come from the screen reader. If Braille isn't supported well in that
context, it's frankly the problem of the screen reader. If we're talking
about something that is self-contained and therefore provides its own AT,
it's not possible for it to support Braille other than to provide the
interface and even that's tricky since there are so many varieties each with
their own protocol. I think Braille has to come through interface with a PC
or directly with a Braille device supplied by the user. Unlike enlargement
and speech output which can easily be native to the application.
- Next message in Thread: David Poehlman: "Re: General Issues:Speechinterfacesandequivalent facilitation"
- Previous message in Thread: Gregg Vanderheiden: "Re: General Issues:Speechinterfaces and equivalent facilitation"
WebAIM is an initiative of:
