Replication Server
version 12.6
The Replication Server
product consists of two server applications: The actual Replication Server
and the Replication Server Manager (RSM) server. The management interface
for these two servers is either through a TSQL query utility such as isql,
or through one of the two management utilities: the Replication Server
Manager (RSM) plug-in for Sybase Central (C++ version 3.2), or the Replication
Manager (RM) plug-in for Sybase Central Java edition (version 4.1.1).
Replication Server Manager (RSM)
Plug-in
The RSM plug-in is a Microsoft Windows
application. The assessment was performed on Windows 2000.
| Section
1194.21 Software Applications and Operating Systems |
| Criteria
|
Supporting
Features |
Remarks
and explanations |
| (a) When
software is designed to run on a system that has a keyboard, product
functions shall be executable from a keyboard where the function itself
or the result of performing a function can be discerned textually. |
Supported
with exceptions: Keyboard access is provided throughout the RSM
plug-in. Keyboard shortcuts, tab order, shortcut keys, and menu commands
are readily available in the RSM plug-in. |
1.
The user cannot activate the context menu of an item in a list box
in any of the dialogs without using the mouse.
2. Connection Properties dialog, Table Properties dialog, RSM Server
Events dialog: The user cannot make a selection in the list box
without using the mouse.
3. Non-Sybase Properties dialog: The user cannot access the “Suspend
DSI” checkbox without using the mouse.
4. Table Properties dialog: Page tabs cannot be access without using
the mouse.
5. RSM Server Events: The user cannot select the “Perform
Action” checkbox without using the mouse.
6. Create Publications dialog: The user cannot navigate the dialog
without using the mouse.
7. Create Subscription dialog: The user cannot edit the “where
clause” without using the mouse. |
| (b) Applications shall
not disrupt or disable activated features of other products that are
identified as accessibility features, where those features are developed
and documented according to industry standards. Applications also
shall not disrupt or disable activated features of any operating system
that are identified as accessibility features where the application
programming interface for those accessibility features has been documented
by the manufacturer of the operating system and is available to the
product developer. |
Fully Supported:
RSM plug-in does not disrupt or disable any accessibility features
of the operating system. RSM plug-in fully supports operating system
accessibility features including StickyKeys, FilterKeys, MouseKeys,
High Contrast and more. The Microsoft Windows magnifier application
is available to magnify dialog text. |
|
| (c) A well-defined
on-screen indication of the current focus shall be provided that moves
among interactive interface elements as the input focus changes. The
focus shall be programmatically exposed so that Assistive Technology
can track focus and focus changes. |
Supported with
exceptions: Visual on-screen focus and tracking is provided throughout
the RSM plug-in. |
Focus is not programmatically
exposed for the Latency graph. The Windows magnifier does not follow
the graph. |
| (d) Sufficient information
about a user interface element including the identity, operation and
state of the element shall be available to Assistive Technology. When
an image represents a program element, the information conveyed by
the image must also be available in text. |
Supported with
exceptions:
Text is associated with each element and all images have an associated
text description in the RSM plug-in. |
List box controls
on dialogs throughout the application do not have associated text
labels. |
| (e) When bitmap images
are used to identify controls, status indicators, or other programmatic
elements, the meaning assigned to those images shall be consistent
throughout an application's performance. |
Fully Supported:
Standard and consistent images are utilized throughout the RSM plug-in. |
|
| (f) Textual information
shall be provided through operating system functions for displaying
text. The minimum information that shall be made available is text
content, text input caret location, and text attributes. |
Fully Supported:
Operating system settings for text content, caret location, and
text attributes are used by the RSM plug-in. |
Note text attributes
such as font and font size cannot be changed on a standard Microsoft
Window dialog. |
| (g) Applications shall
not override user selected contrast and color selections and other
individual display attributes. |
Supported with
exceptions: RSM plug-in supports most system-wide color settings
as identified in the operating system display properties. |
1. Replication Definition
Properties dialog, Table Properties dialog, RSM Server Events dialog,
Generate DDL Edit window, and Function String Edit window do not use
system settings for the font foreground color. Therefore, the text
disappears when using the high contrast black screen setting.
2. Configure dialogs do not use system settings for the selection
color in the configuration parameter table.
3. The Latency graph lines cannot be seen when using the high contrast
black screen setting. |
| (h) When animation
is displayed, the information shall be displayable in at least one
non-animated presentation mode at the option of the user. |
Fully Supported:
The Latency graph is the only animation in the RSM plug-in. |
The Latency graph
displays each set of data points in a table at the bottom of the screen. |
| (i) Color coding shall
not be used as the only means of conveying information, indicating
an action, prompting a response, or distinguishing a visual element. |
Fully Supported:
RSM plug-in does not use color-coding to convey any information. |
|
| (j) When a product
permits a user to adjust color and contrast settings, a variety of
color selections capable of producing a range of contrast levels shall
be provided. |
Fully Supported:
RSM plug-in does not permit the user to adjust color and contrast
settings. RSM plug-in supports operating system settings for high
contrast color schemes that make the screen easier to view for some
users by heightening screen contrast with alternate color combinations. |
|
| (k) Software shall
not use flashing or blinking text, objects, or other elements having
a flash or blink frequency greater than 2 Hz and lower than 55 Hz. |
Fully Supported:
RSM plug-in does not use flashing or blinking objects or text
that falls within this frequency range. |
|
| (l) When electronic
forms are used, the form shall allow people using Assistive Technology
to access the information, field elements, and functionality required
for completion and submission of the form, including all directions
and cues. |
Supported with
exceptions: RSM plug-in electronic forms (dialogs) support all
accessibility features with minor exceptions. |
1. Microsoft Windows
Narrator does not read non-editable text on dialogs and cannot read
text in list box tables. The Narrator does not read help text displayed
using the Microsoft on-line help application.
2. The Microsoft On-Screen Keyboard cannot activate menu items on
the Sybase Central menu. The On-Screen Keyboard cannot activate
links in context sensitive help. |
Replication Manager (RM) Plug-in
The RM plug-in is a multi-platform Java application. The assessment was
performed on Windows 2000.
| Section
1194.21 Software Applications and Operating Systems |
| Criteria
|
Supporting
Features |
Remarks
and explanations |
| (a) When software
is designed to run on a system that has a keyboard, product functions
shall be executable from a keyboard where the function itself or the
result of performing a function can be discerned textually. |
Fully Supported:
The Replication Server installation program does not disrupt or
disable any accessibility features of the operating system. |
|
| (b) Applications shall
not disrupt or disable activated features of other products that are
identified as accessibility features, where those features are developed
and documented according to industry standards. Applications also
shall not disrupt or disable activated features of any operating system
that are identified as accessibility features where the application
programming interface for those accessibility features has been documented
by the manufacturer of the operating system and is available to the
product developer. |
Supported with
exceptions: RM plug-in supports operating system accessibility
features including StickyKeys, FilterKeys, MouseKeys, High Contrast
and more. The Microsoft Windows magnifier application is available
to magnify dialog text. |
1. The Windows
Narrator does not read Java dialogs.
2. Alt sticky keys do not work.
3. Windows high contrast feature does not take affect until Sybase
Central is restarted. |
| (c) A well-defined
on-screen indication of the current focus shall be provided that moves
among interactive interface elements as the input focus changes. The
focus shall be programmatically exposed so that Assistive Technology
can track focus and focus changes. |
Supported with
exceptions: Visual on-screen focus and tracking is provided throughout
the RM plug-in |
Windows screen magnifier
does not follow the focus when moving between fields using the tab
key. |
| (d) Sufficient information
about a user interface element including the identity, operation and
state of the element shall be available to Assistive Technology. When
an image represents a program element, the information conveyed by
the image must also be available in text. |
Supported with
exceptions:
Text is associated with each element and all images have an associated
text description in the RM plug-in. |
The edit field
at the top of properties dialog is for entering the name of the new
Database replication definition or subscription. There is no label
preceding this field. Without the label, a screen reader will be unable
to identify the purpose of the field. |
| (e) When bitmap images
are used to identify controls, status indicators, or other programmatic
elements, the meaning assigned to those images shall be consistent
throughout an application's performance. |
Fully Supported:
Standard and consistent images are utilized throughout the RM
plug-in. |
|
| (f) Textual information
shall be provided through operating system functions for displaying
text. The minimum information that shall be made available is text
content, text input caret location, and text attributes. |
Supported with
exceptions:
Operating system settings for text content, caret location, and text
attributes are used by the RM plug-in. |
Text attributes such
as font and font size cannot be set on a dialog. |
| (g) Applications shall
not override user selected contrast and color selections and other
individual display attributes. |
Supported with
exceptions:
RM plug-in supports most system-wide color settings as identified
in the operating system display properties. |
Changing the system
color does not take affect until Sybase Central is restarted. |
| (h) When animation
is displayed, the information shall be displayable in at least one
non-animated presentation mode at the option of the user. |
Fully Supported:
RM plug-in does not use any animation. |
|
| (i) Color coding shall
not be used as the only means of conveying information, indicating
an action, prompting a response, or distinguishing a visual element. |
Fully Supported:
RM plug-in does not use color-coding to convey any information. |
|
| (j) When a product
permits a user to adjust color and contrast settings, a variety of
color selections capable of producing a range of contrast levels shall
be provided. |
Fully Supported:
RM plug-in does not permit the user to adjust color and contrast settings.
RM plug-in supports operating system settings for high contrast color
schemes that make the screen easier to view for some users by heightening
screen contrast with alternate color combinations. |
|
| (k) Software shall
not use flashing or blinking text, objects, or other elements having
a flash or blink frequency greater than 2 Hz and lower than 55 Hz. |
Fully Supported:
RM plug-in does not use flashing or blinking objects or text that
falls within this frequency range. |
|
| (l) When electronic
forms are used, the form shall allow people using Assistive Technology
to access the information, field elements, and functionality required
for completion and submission of the form, including all directions
and cues. |
Supported with
exceptions:
RM plug-in electronic forms (dialogs) support all accessibility features
with minor exceptions. |
The Windows Narrator
does not read Java dialogs. |
Replication Server Configuration
Utility (rs_init)
The configuration utility for the Replication Server is called rs_init.
The rs_init utility exists on all supported platforms and can be executed
interactively, or in batch mode using a resource file. Neither the Microsoft
Windows interactive mode nor the Unix command line mode is 508 compliant.
However, a user can create a resource file using a 508 compliant text
editor and then execute rs_init from an operating system command prompt..
Table Comparison Utility (rs_subcmp)
The Replication Server product provides a utility called rs_subcmp that
compares a replicated table to the primary version of the table, finding
and optionally reconciling missing, orphaned, and inconsistent rows. The
rs_subcmp utility is a batch mode program that can be executed using a
configuration file. To support accessibility, a user can create the configuration
file using a 508 compliant text editor and then execute rs_subcmp from
an operating system command prompt.
Replication Server Installation
The installation program used by Replication Server provides three execution
modes: graphical user interface (GUI) interactive mode, console mode,
and silent mode. See the Replication Server documentation for more details.
To invoke the console mode, the Replication
Server is started with the following command: setup –console
This allows the resulting text in the command prompt to work with native
Windows 2000 accessibility. Accessibility items such as screen readers,
on screen keyboards, and magnifiers all function correctly using this
mode. This provides an alternative to some small issues found in the (GUI)
interactive mode, described below.
The following assessment is for the
GUI interactive mode. The assessment was performed on Windows 2000.
| Section
1194.21 Software Applications and Operating Systems |
| Criteria
|
Supporting
Features |
Remarks
and explanations |
| (a) When
software is designed to run on a system that has a keyboard, product
functions shall be executable from a keyboard where the function itself
or the result of performing a function can be discerned textually. |
Supported
with exceptions: Keyboard access is provided throughout the Replication
Server installation program. Keyboard shortcuts, tab order, shortcut
keys, and menu commands are readily available in the installation
program. |
1. The
user cannot regain focus on the Status page without using the mouse.
2. The user cannot scroll the summary area on the Summary page without
using the mouse |
| (b) Applications
shall not disrupt or disable activated features of other products
that are identified as accessibility features, where those features
are developed and documented according to industry standards. Applications
also shall not disrupt or disable activated features of any operating
system that are identified as accessibility features where the application
programming interface for those accessibility features has been documented
by the manufacturer of the operating system and is available to the
product developer. |
Fully
Supported: The Replication Server installation program does not
disrupt or disable any accessibility features of the operating system.
|
|
| (c) A
well-defined on-screen indication of the current focus shall be provided
that moves among interactive interface elements as the input focus
changes. The focus shall be programmatically exposed so that Assistive
Technology can track focus and focus changes. |
Fully
Supported: Visual on-screen focus and tracking is provided throughout
the Replication Server installation program. |
The Component
Selection page and the Language Module page do not provide visual
focus for checkbox controls. |
| (d) Sufficient
information about a user interface element including the identity,
operation and state of the element shall be available to Assistive
Technology. When an image represents a program element, the information
conveyed by the image must also be available in text. |
Fully
Supported: Text is associated with each element and all images
have an associated text description in the Replication Server installation
program. |
|
| (e) When
bitmap images are used to identify controls, status indicators, or
other programmatic elements, the meaning assigned to those images
shall be consistent throughout an application's performance. |
Fully
Supported: Standard and consistent images are utilized throughout
the Replication Server installation program. |
|
| (f) Textual
information shall be provided through operating system functions for
displaying text. The minimum information that shall be made available
is text content, text input caret location, and text attributes. |
Fully
Supported: The Replication Server installation program uses operating
system settings for text content, caret location, and text attributes. |
Text attributes such
as font and font size cannot be changed on a standard Microsoft Window
dialog. |
| (g) Applications
shall not override user selected contrast and color selections and
other individual display attributes. |
Fully
Supported: The Replication Server installation program supports
system-wide color settings as identified in the operating system display
properties. |
The installation
program does not use the system colors when displaying window background
colors or font colors. |
| (h) When
animation is displayed, the information shall be displayable in at
least one non-animated presentation mode at the option of the user. |
Fully
Supported: The Replication Server installation program does not
contain any animation. |
|
| (i) Color
coding shall not be used as the only means of conveying information,
indicating an action, prompting a response, or distinguishing a visual
element. |
Fully
Supported: The Replication Server installation program does not
use color-coding to convey any information. |
|
| (j) When
a product permits a user to adjust color and contrast settings, a
variety of color selections capable of producing a range of contrast
levels shall be provided. |
Fully
Supported: The Replication Server installation program does not
permit the user to adjust color and contrast settings. |
|
| (k) Software
shall not use flashing or blinking text, objects, or other elements
having a flash or blink frequency greater than 2 Hz and lower than
55 Hz. |
Fully
Supported: The Replication Server installation program does not
use flashing or blinking objects or text that falls within this frequency
range. |
|
| (l) When
electronic forms are used, the form shall allow people using Assistive
Technology to access the information, field elements, and functionality
required for completion and submission of the form, including all
directions and cues. |
Supported
with exceptions:
The Replication Server installation program’s electronic forms
(dialogs) support all accessibility features with minor exceptions. |
1. The Microsoft Windows
Magnifier does not follow the focus on the installation program’s
dialogs. The dialogs do not automatically resize to fit under the
magnification window.
2. Screen readers such as Windows Narrator and JAWS only read the
title bar on the dialogs. Dialog text, including the license agreement,
is not currently readable. If this is a serious issue, we recommend
running the installer in console mode so the text will be announced. |
RSM Server Configuration
Utility
The configuration utility for the RSM Server on all Unix platforms is
called rsmgen. The rsmgen utility is a command line shell script that
is not 508 compliant.
The configuration utility
for the RSM Server on the Microsoft Windows platform is called RSMSetup.
The assessment was performed on Windows 2000.
| Section
1194.21 Software Applications and Operating Systems |
| Criteria
|
Supporting
Features |
Remarks
and explanations |
| (a) When
software is designed to run on a system that has a keyboard, product
functions shall be executable from a keyboard where the function itself
or the result of performing a function can be discerned textually. |
Supported
with exceptions: Keyboard access is provided throughout RSMSetup.
Keyboard shortcuts, tab order, shortcut keys, and menu commands are
readily available in the installation program. |
The user
cannot access the browse buttons without using the mouse. |
| (b) Applications
shall not disrupt or disable activated features of other products
that are identified as accessibility features, where those features
are developed and documented according to industry standards. Applications
also shall not disrupt or disable activated features of any operating
system that are identified as accessibility features where the application
programming interface for those accessibility features has been documented
by the manufacturer of the operating system and is available to the
product developer. |
Fully
Supported: RSMSetup does not disrupt or disable any accessibility
features of the operating system. |
|
| (c) A
well-defined on-screen indication of the current focus shall be provided
that moves among interactive interface elements as the input focus
changes. The focus shall be programmatically exposed so that Assistive
Technology can track focus and focus changes. |
Fully
Supported: Visual on-screen focus and tracking is provided throughout
RSMSetup. |
The Component
Selection page and the Language Module page do not provide visual
focus for checkbox controls. |
| (d) Sufficient
information about a user interface element including the identity,
operation and state of the element shall be available to Assistive
Technology. When an image represents a program element, the information
conveyed by the image must also be available in text. |
Fully
Supported: Text is associated with each element in RSMSetup. |
|
| (e) When
bitmap images are used to identify controls, status indicators, or
other programmatic elements, the meaning assigned to those images
shall be consistent throughout an application's performance. |
Fully
Supported: RSMSetup does not display any images. |
|
| (f) Textual
information shall be provided through operating system functions for
displaying text. The minimum information that shall be made available
is text content, text input caret location, and text attributes. |
Fully
Supported: RSMSetup uses operating system settings for text content,
caret location, and text attributes. |
Note text attributes
such as font and font size cannot be changed on a standard Microsoft
Window dialog. |
| (g) Applications
shall not override user selected contrast and color selections and
other individual display attributes. |
Fully
Supported: RSMSetup supports all system-wide color settings as
identified in the operating system display properties. |
The installation
program does not use the system colors when displaying window background
colors or font colors. |
| (h) When
animation is displayed, the information shall be displayable in at
least one non-animated presentation mode at the option of the user. |
Fully
Supported: RSMSetup does not contain any animation. |
|
| (i) Color
coding shall not be used as the only means of conveying information,
indicating an action, prompting a response, or distinguishing a visual
element. |
Fully
Supported: RSMSetup does not use color-coding to convey any information. |
|
| (j) When
a product permits a user to adjust color and contrast settings, a
variety of color selections capable of producing a range of contrast
levels shall be provided. |
Fully
Supported: RSMSetup does not permit the user to adjust color and
contrast settings. |
|
| (k) Software
shall not use flashing or blinking text, objects, or other elements
having a flash or blink frequency greater than 2 Hz and lower than
55 Hz. |
Fully
Supported: RSMSetup does not use flashing or blinking objects
or text that falls within this frequency range. |
|
| (l) When
electronic forms are used, the form shall allow people using Assistive
Technology to access the information, field elements, and functionality
required for completion and submission of the form, including all
directions and cues. |
Fully
Supported:
RSMSetup electronic form supports all accessibility features. |
|
|