Sybase.com

Sybase Powerbuilder 9.0
Voluntary Product Accessibility Template

Sybase PowerBuilder (PB) version 9.0 partially supports the development of applications that meet Section 508 compliance criteria. PowerBuilder 10.0 provides all the infrastructure and properties needed to build accessibility features into Windows and Web applications and to conform generally to Microsoft Active Accessibility (MSAA) Version 2, which defines the way accessibility aids obtain information about user interface elements and the way programs expose information to the aids.

Summary Table Voluntary Product Accessibility Template
Criteria	Supporting Features	Remarks and explanations
Section 1194.21 Software Applications and Operating Systems	Please refer to attached VPAT
Section 1194.22 Web-based internet information and applications	Not applicable
Section 1194.23 Telecommunications Products	Not applicable
Section 1194.24 Video and Multi-media Products	Not applicable
Section 1194.25 Self-Contained, Closed Products	Not applicable
Section 1194.26 Desktop and Portable Computers	Not applicable
Section 1194.31 Functional Performance Criteria	Please refer to attached VPAT
Section 1194.41 Information, Documentation and Support	Please refer to attached VPAT

Section 1194.21 Software Applications and Operating Systems - Detail Voluntary Product Accessibility Template
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 for applications developed with PB Partially supported for developers using the IDE: Some operations such as drag-and-drop actions require mouse input.	The PB developer can create shortcut keys or accelerator keys for menus, command buttons, and other visual controls to produce fully compliant applications. See Chapters 11 and 13 of the PowerBuilder User's Guide, Chapter 3 of Objects and Controls, and Chapter 5 of Application Techniques for information.
(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	PB does not disrupt applications that are not running under a PB instance. PB also provides system and environment functions to help the developer interact with other third-party tools and operating systems within the context of a PB application. See system and environment functions in the online Help and Chapter 10 of the PowerScript reference for more information.
(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	When an object on the screen receives focus, a dotted rectangle (focus rectangle) surrounds the item. If the control is editable, a blinking I-beam cursor indicates input focus PB programmatically exposes the focus.
(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	A unique name is associated with each control in a PB window or User Object. Controls have an enable/disable property that can be set at design or execution time to define the status of the control. The PictureButton control has a text property. See Chapter 3 of Objects and Controls and Chapter 3 of the DataWindow Reference for more information.
(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	By default, all PB painters are consistent. At runtime all the controls render uniform behavior unless the user changes them.
(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	PB supports all standard text display functions.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes.	Fully Supported	PB does not alter the hardware or software settings pertaining to display attributes.
(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	Animated images can be attached to picture buttons, which have a text property for presenting the images in non-animated mode. See PowerBuilder Objects and Controls for more information.
(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	For example, the PB MDI interface status bar and MessageBox functions are used to convey information, and modal windows are used to prompt responses. See the PowerBuilder User's Guide and Application Techniques for more 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	Color palette & RGB functions are provided to change the color attribute of displayed text and controls. See the PowerBuilder User's Guide and the PowerScript Reference for more information.
(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 PowerBuilder IDE has no flashing or blinking elements.
(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	The flow of the application created by the PB developer determines the degree of compliance.

Section 1194.31 Functional Performance Criteria - Detail Voluntary Product Accessibility Template
Criteria	Supporting Features	Remarks and explanations
(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.	Partially Supported	PB 9 standard controls do not support the required MSAA properties. Full support is provided in PB 10 for developers of 508-compliant applications. As a GUI-based development tool, the PowerBuilder IDE inherently depends upon the application developer's visual sense to deliver its full power.
(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.	Fully Supported	MS Magnifier can be used with the PowerBuilder IDE.
(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided	Fully Supported	The PowerBuilder IDE does not require user hearing.
(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.	Fully Supported	The PowerBuilder IDE does not require user hearing.
(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.	Fully Supported	The PowerBuilder IDE does not require users to provide spoken input.
(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.	Fully Supported	PB supports operating system tools such as StickyKeys and FilterKeys as well as other assistive technologies.

Section 1194.41 Information, Documentation, and Support - Detail Voluntary Product Accessibility Template
Criteria	Supporting Features	Remarks and explanations
Section 1194.41 (a) Product Support Documentation	Not Supported	PB 10 documentation provides image descriptions and table navigation aids and is fully compliant.
Section 1194.41 (b) Accessibility and Compatibility Features	Partially Supported	The chapters cited in the previous tables provide information about the 508 support provided by PB 9.0.
Section 1194.41 (c) Support Services	Fully Supported	The Sybase Technical Support group offers a variety of services including Technical Documents, White Papers, Product Manuals, Newsgroups, online Software Problem Case Management, Change Requests, and Maintenance Release Downloads. For information on these and other support services, visit the Sybase Technical Support Web site at http://www.sybase.com/support For information on TTY phones and accessible support services, see http://www.sybase.com/accessibility