The Java Desktop System Release 3 includes an Accessible Login feature. The feature allows users to log in to their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. This feature allows the user to launch assistive technologies at login time by means of special gestures from the standard keyboard and from a keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. The feature also allows the user to change the visual appearance of the login dialog before the user logs in, for instance to use a higher-contrast color scheme for better visibility. To enable Accessible Login, the system administrator must perform the following steps: Configure the desktop to use the GNOME Display Manager (GDM) as the login manager. See for more information. Make some configuration changes to GDM. The system administrator can make these changes by manually modifying the following three human-readable configuration files as described in and : /etc/X11/gdm/gdm.conf /etc/X11/gdm/modules/AccessKeyMouseEvents /etc/X11/gdm/modules/AccessDwellMouseEvents To configure the desktop to use GDM as the login manager, perform the following steps: Log in as the root user. Enter the following command to stop the dtlogin manager: /usr/dt/bin/dtconfig -d Edit the /etc/inittab file as follows: co:234:respawn:/usr/lib/saf/ttymon -g -h -p "`uname -n` console > login: " -T sun -d /dev/console -l console -m ldterm,ttcompat > co:234:wait:/opt/jds/bin/gdm This comments out the line to start ttymon and adds a line to start GDM. Enter the following commands to create a /var/lib/gdm directory: mkdir -p /var/lib/gdm chown gdm:gdm /var/lib/gdm Reboot your system. Log in as the root user. Edit the file /etc/X11/gdm/gdm.conf. Search the file for the following line: #Greeter=/usr/bin/gdmgreeter and replace the line with the following: Greeter=/usr/bin/gdmlogin This step enables a standard login greeting rather than a graphical login greeting. Search the file for the following line: #AddGtkModules=false and replace the line with the following: AddGtkModules=true Search the file for the following line: #GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener and remove the # from the start of the line so that the line reads: GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener The above lines must be displayed as single lines in the gdm.conf file without line breaks. The formatting of this guide may display the lines over two lines. This step and previous step enable the use of assistive technologies such as the Onscreen Keyboard, Screen Reader, and Magnifier. System administrators may wish to load only the minimum subset of these modules which is required to support their user base. Depending on your end-user needs, not all of the above GtkModules may need to be loaded. If your end-users need the integrated Screen Reader and Magnifier, you must include gail and atk-bridge. If your users need to use a pointing device without buttons or switches, include dwellmouselistener. If some of your users use pointing devices with switches, alternative physical keyboards, or switch/button devices, include keymouselistener. Including all four modules is suitable for most system configurations. The Onscreen Keyboard can operate without gail and atk-bridge, but with a reduced feature set. For optimum accessibility we recommend including gail and atk-bridge. To allow users to change the color and contrast scheme of the login dialog, include the following line in the file: AllowThemeChange=true To restrict user changes to the visual appearance to a subset of the available themes, you can add a line similar to the following: GtkThemesToAllow=blueprint,HighContrast,HighContrastInverse Save the gdm.conf file. Once keymouselistener and/or dwellmouselistener have been added to the GtkModules loaded by GDM, you can assign end-user actions to launch specific assistive technologies. These gesture associations are contained in the following files, respectively: /etc/X11/gdm/modules/AccessKeyMouseEvents /etc/X11/gdm/modules/AccessDwellMouseEvents The gesture format is described in the two files. The following section demonstrates some suggested examples that have been tested with common usage scenarios. In the file AccessKeyMouseEvents, the following line associates ControlS held for one second with the Screen Reader in "speech and braille" mode: <Control>s 1 1000 1000 srcore --login --disable-magnifier --enable-speech --enable-braille You can assign similar key combinations to launch the Screen Reader in "magnification only" mode, such as: <Control>m 1 1000 1000 srcore --login --enable-magnifier --disable-speech The above lines must be displayed as single lines in the AccessKeyMouseEvents file without line breaks. The formatting of this guide may display the lines over two lines. You can use end-user button, key, or switch actions to launch assistive technologies. Since the primary input device for many Onscreen Keyboard users is a switch or buttons, this is a good way to allow such users to signal their need for the Onscreen Keyboard at login time. To reduce the likelihood of launching the application unintentionally, you can associate the gestures with multiple switch presses and/or minimum durations. For example, the following line in the file AccessKeyMouseEvents associates three presses of "Switch 2" for a minimum of 100 milliseconds each within 2 seconds, with the launch of the Onscreen Keyboard in "inverse scanning" mode: <Switch2>3 100 2000 gok --login --accessmethod=inversescanning --scan-action=switch1 --select-action=switch2 Users of single switches may prefer the 'automatic scanning' access method. The following line associates GOK with a prolonged press (> 4 seconds) of switch 1 on an alternate access device: <Switch>1 4000 5000 gok --login --accessmethod=automaticscanning --scan-action=switch1 --select-action=switch1 The above lines must be displayed as single lines in the AccessKeyMouseEvents file without line breaks. The formatting of this guide may display the lines over two lines. You can also define gestures that involve only the motion of a pointing device such as the system mouse or an alternative pointing device such as a head pointer or trackball. All such gestures are specified by the same syntax, that is there is no distinction between a core mouse gesture and motion from an alternate input device. Motion gestures are defined as crossing events into and out of the login dialog window. If the dwellmouselistener GtkModule is loaded, alternative pointing devices are temporarily latched to the core pointer so that motion from alternative devices results in movement of the onscreen pointer. The following gesture can be completed by moving the onscreen pointer, starting from inside the login dialog, across the top edge, back into the dialog across the top edge, out of the dialog via the left edge, back into the dialog via the left edge, and similarly through bottom and right-hand edges of the dialog, in a cross pattern. The gesture launches GOK in Dwell mode. Note that the --input-device parameter specified in the gesture must match the name of the user input device as specified in /etc/X11/XF86Config. TTLLBBRR O 10000 gok --login --access-method=dwellselection --input-device=MOUSE[3] The above line must be displayed as a single line in the AccessKeyMouseEvents file without line breaks. The formatting of this guide may display the line over two lines. To use text-to-speech services at login time, for example when you are using the Screen Reader in Speech mode, the GDM user must be a member of the "audio" group. You can confirm this by checking the file /etc/group. Please see the Java Desktop System Release 3 Administration Guide for details about changing group membership. To facilitate Accessible Login using alternative pointing devices and end-user switch devices such as sip-and-puff switches, wheelchair-mounted switches, trackballs, and so on, you may need to modify your X server system configuration to recognize these devices. Most devices which emulate mouse buttons, including USB single switches, mouse-like pointing devices, and devices that emulate them, can be used with Accessible Login and the Onscreen Keyboard. In the Java Desktop System Release 3, the GDM user has a readable home directory. If this setting is removed for security reasons, the Screen Reader and Magnifier will not function properly during Accessible Login. Alternate input devices should not be configured to control the primary onscreen pointer. This may result in undesirable behavior or cause situations from which the user of the alternate input devices cannot recover without the use of the primary keyboard or mouse. To enable the standard GDM greeter, perform the following steps: Log in as the root user. Edit the file /etc/X11/gdm/gdm.conf. Search the file for the following line: #Greeter=/usr/bin/gdmgreeter and replace the line with the following: Greeter=/usr/bin/gdmlogin Save the file. To configure the Java Environment for accessibility, perform the following steps: Log in as the root user to the base directory of the Java SDK installation. Enter the following command to change to the jre/lib directory: cd jre/lib Enter the following command: ln -s /usr/share/jar/accessibility.properties Enter the following command to change to the ext directory: cd ext Execute the following command: ln -s /usr/share/jar/gnome-java-bridge.jar To enable full screen magnification in Gnopernicus, perform the following steps: Configure two video cards as :0.0 and :0.1. It is not essential that both video cards have the same resolution and bit depth. However, if the resolutions and bit depths of both cards differ greatly, the apparent magnification factor may differ slightly from the nominal magnification factor. Click Launch, then chooseApplicationsAccessibilityScreen Reader and Magnifier to start Gnopernicus. Click on Preferences. Click on Magnifier. Click on Add/Modify. Specify :0.0 as the Source for magnification. Specify :0.1 as the Target for magnification. Set the Zoomer Placement to be [0,0,1023,767]. These instructions assume a video resolution of 1024x768. Restart Gnopernicus. The magnified view is displayed on the second display 0.1. To disable the screensaver, perform the following steps: Click Launch, then choose PreferencesDisplayScreensaver. In the Display Modes tabbed section, deselect the Lock Screen After check box. In the Mode drop-down list, select Disable Screen Saver. Choose FileRestart Daemon. Choose FileQuit to close the Screensaver dialog. If you are a GOK user, you cannot use the GNOME Terminal application in Full Screen mode because the GNOME Terminal window obscures the GOK display. To resize the GNOME Terminal window for use with the GOK application, perform the following steps: Do not enable the Full Screen mode in GNOME Terminal. Give focus to the GNOME Terminal window. Press F10 to maximize the application.