Thread Subject: Re: "closed software"
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: James Elekes
Date: Fri, Feb 23 2007 9:50 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: "closed software""
- Previous message in thread: Hoffman, Allen: "Re: "closed software""
- Messages sorted by: Author | Thread | Date
Thanks for the clarification. From the initial post, as a blind
individual using GW Micro Window Eyes, my perception was somewhat different.
At 09:44 AM 2/23/2007, you wrote:
><quote>I think you are talking about speech and are using a product
>name. JAWS is one type of speech. Folks that use say Window Eyes
>would not necessarily have the skills to use JAWS. One must learn
>the program. I feel that if a specific speech product were "built
>in" that there would end up being the same issues that Microsoft had
>regarding the monopoly issue. </quote>
>Actually, I am talking about a specific situation where the JAWS for
>Windows screen reader was being used. A 4 key keypad was used and
>no knowledge of a particular screen reader was needed as there were
>only commands to move forward, backward, activate an item, or get help.
>__________ NOD32 1.1776 (20060926) Information __________
>This message was checked by NOD32 antivirus system.