[typeabilitybeta] TypeAbility 3.0.7 is ready

  • From: "David Pinto" <davepinto@xxxxxxxxxxx>
  • To: <typeabilitybeta@xxxxxxxxxxxxx>
  • Date: Tue, 08 Jul 2008 13:51:57 -0700

Beta Testers,

TypeAbility 3.0.7 can be downloaded from YesAccessible.com. You don't need your personal FTP site for the download. Just go to YesAccessible.com, and click on the link, Download a trial version of TypeAbility for JAWS. After downloading it, start it up, and on the registration page, enter the registration number that was e-mailed to you, in order to install a fully authorized TypeAbility. Here's some of the new features in 3.07.

1. The TypeAbility installer will always provide you with a choice of up to 3 JAWS versions to install into. There was a bug that Brian found, where having JAWS 10 on your system would only allow installation into JAWS 10. This has been fixed.

2. TypeAbility speech is highly controlled and depends on Eloquence. So if
Eloquence is not the JAWS speech synthesizer, Speech will be unintelligible,
because the TA functions for controlling speech will not behave properly.
So, now in TA 3.0.7, upon opening TypeAbility, if Eloquence is not running,
TA will tell the user to switch to Eloquence, including the exact steps on
how to reset the speech synthesizer.

3. Speech inflections continue to be improved.

4. Whenever a lesson introduces a new letter, the location of the key is
provided. But sometimes the location was being either over-explained, or
confusingly explained. This has been fixed.

5. When responding to an incorrect key press, TA responds with escalating
adjectives of surprise. But when the incorrect keypress is adjacent to the
desired key, TypeAbility will announce that they're close, and tell them
which direction to move over, whether up or down, or right or left, one key.
But TA would also pre pend not only the adjective of
surprise, but an additional one, to boot. This is fixed.

6. I continue to look for inappropriate adult messages, and replacing them
with the appropriate adult message. Certain messages were not respecting the
Adult User Preference. Like, Oopsey Whoopsey! is not an appropriate
adjective for Adults.

Please send TypeAbility through its hoops, and let us know as soon as possible how it works. We need to get it out ASAP.

Thanks,

David


Other related posts: