JAWS Scripts For Skype - Screen Reader Not Detected

General Information

Support for these scripts is primarily provided in the following places, most preferred first:

SkypeEnglish Mailing List
Public forum in which blind Skype users can help each other.
@dlee_code on Twitter
The script author's low-traffic Twitter account for project (including script) announcements and limited technical support.

This page is laid out for easy navigation via JAWS:

Screen Reader Not Detected: Why and What To Do

You may have arrived at this page because the Skype scripts produced a message saying your screen reader was not detected, or you may have come here from the Frequently Asked Questions page or from elsewhere. Either way, what follows is an explanation of this problem and what to do if it occurs.

Why Does This Happen?

Some applications, including Skype, provide a lot of accessibility information in order that screen readers, such as JAWS, can relay that information to the user. However, this can require much processing, memory, and in some cases, can require visible changes to the interface of the application. For this reason, applications can choose to provide this information only when a screen reader is actually running.

The system used in Windows to let applications know a screen reader is running can sometimes fail. This usually happens when a user runs two screen readers at once and then exits one of them while still running the other. For example, if JAWS is running and the user launches and then closes Microsoft Narrator while leaving JAWS active, Windows can lose track of the fact that a screen reader is still running. Applications that then ask Windows if one is running will be told "no." The easiest solution to this problem is to exit all running screen readers, then restart the preferred screen reader by itself.

What To Do

If you receive a message from JAWS saying that Skype is not aware that a screen reader is running, do one of the following, depending on which best fits your situation: