Thread Subject: Re: General Issues:Speechinterfacesandequivalent facilitation
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: David Poehlman
Date: Sat, Jan 20 2007 4:55 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: General Issues:Speechinterfaces and equivalent facilitation"
- Previous message in thread: Debbie Cook: "Re: General Issues:Speechinterfacesandequivalent facilitation"
- Messages sorted by: Author | Thread | Date
I'd be interested in exploring this. What would it take since apps
already provide display paths and could provide keyboard access to ad
a braille driver much like using a printer driver. maybe this needs
to be done at the os level.
On Jan 10, 2007, at 6:45 PM, Debbie Cook wrote:
"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
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
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
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
and speech output which can easily be native to the application.
- Next message in Thread: Gregg Vanderheiden: "Re: General Issues:Speechinterfaces and equivalent facilitation"
- Previous message in Thread: Debbie Cook: "Re: General Issues:Speechinterfacesandequivalent facilitation"