SUPPORT / SAMPLES & SAS NOTES
 

Support

Usage Note 15970: Jaws Screen Reader might have trouble reading Log window

DetailsHotfixAboutRate It

When you use the Jaws Screen Reader and SAS® 9.1, the Log window might not read the Log window line by line. When this happens, the SAS cursor and the JAWS cursor get separated.

Contact SAS Technical Support, referencing this SAS note, and ask for a new sasvwu.dll file that corrects this problem. To implement the new sasvwu.dll, follow these instructions:

  1. Make a backup of your existing sasvwu.dll located in !SASROOT\core\sasexe (the default location is "C:\Program Files\SAS\SAS 9.1\core\sasexe").
  2. Stop all SAS processes that appear in Task Manager and under Services in the Control Panel. For example: sas.exe and any services starting with SAS Lev1.
  3. Copy the new sasvwu.dll to default location !SASROOT\core\sasexe (the default location is "C:\Program Files\SAS\SAS 9.1\core\sasexe")
  4. Restart your PC.

This sasvwu.dll file will be included in SAS 9.1.3 Service Pack 4 when it becomes available.

If you are unable to apply the sasvwu.dll at this time, use the following commands to allow Jaws to read line by line in the Log window:

  • Use Ctrl-L or Alt-V, L to access the Log window.

    Note: JAWS will acknowledge that you have activated the Log window but it will not read the contents.

  • Activate the Log window menu with Alt-(minus sign).
  • Press the Esc key twice to exit from the menu and put the cursor focus back to the Log window. This action grabs the JAWS cursor and performs a "Sync Up" with the SAS cursor. At this point, you are ready to step through and read line by line.
  • To read the first line (or the current line, where the cursor is positioned), use Insert/Page Up - .
  • To take the cursor to the next line where it will send JAWS into "READ ALL" mode (from the top), use the down arrow.
  • Press Ctrl to interrupt the "READ ALL" mode.
  • Press Insert/Page Up to read the current line, then repeat.

Sometimes there might be inconsistent behavior. Please see the following information:

If you have previously moved the SAS cursor within the Log window and left the Log window to work in the Editor (or any other window) and returned to the Log window, your cursor placement will be where you left it previously or after your newly submitted code. It does not automatically go to a home position at the top line in the Log window.

In the above scenario, we do not know exactly where the SAS cursor is upon re-entry and the JAWS cursor might not be in the same position. The cursor will always be in the top left position of the Log window, not the top line of the Log and always the top one visible after the log has scrolled.

On re-entry in the Log window, press Insert/Page Up to read the line where the JAWS cursor is, not the SAS cursor. At this point you MUST press Alt/- (minus sign) to sync up JAWS and the SAS cursors again. This action will take the JAWS cursor to where the SAS cursor is. Every time that you re-enter the Log window, you will have to do redo the sync up process in order to read line by line.

Select the Hot Fix tab in this note to access the hot fix for this issue.

IMPORTANT: You must have SAS 9.1.3 Service Pack 3 installed on your system before installing D9BA47.

IMPORTANT: Please carefully review the on-line "Install Instructions" for information on setting the "-accessibility extended option" which is required by this hot fix.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemBase SASMicrosoft Windows 2000 Server9.1 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M0
Microsoft Windows Server 2003 Standard Edition9.1 TS1M0
Microsoft Windows NT Workstation9.1 TS1M0
Microsoft Windows XP Professional9.1 TS1M0
Microsoft Windows 2000 Advanced Server9.1 TS1M0
Microsoft Windows 2000 Datacenter Server9.1 TS1M0
Microsoft Windows 2000 Professional9.1 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.