Accessibility

Accessibility features help a user who has a physical disability, such as a visual impairment, hearing impairment, or limited mobility, to use software products successfully.

The following sections represent the major accessibility features in WebSphere Commerce:

Installation
You can install all WebSphere Commerce components by using the command line:
Feature Pack 6 or laterYou cannot use a screen reader with the Installation launchpad or the First Steps wizard. However, you can access all of the information and functionality on these user interfaces in other ways.
  • The Installation launchpad provides the following links:The launchpad also includes a button to start the installer. Instead, you can start the installer on the command line
    • WebSphere Commerce DeveloperTo install WebSphere Commerce Feature Pack for Developer, go to the FeaturePack_tempdir/ directory and enter the following command:
      • install_developer.bat
    • To install WebSphere Commerce Feature Pack for Server, go to the FeaturePack_tempdir/ directory and enter the following command:
      • SolarisLinuxAIX./install_server.sh
      • Windowsinstall_server.bat
      • For IBM i OS operating systemserver\install.os400.bat
  • The First Steps wizard provides links to the following sections of the WebSphere Commerce information center:

    WebSphere Commerce DeveloperThe First Steps wizard also provides a button for starting the toolkit. Instead, go to the WCDE_installdir/bin directory on the command line and enter startWCToolkit.bat.

Starter stores
The starter stores provide the following accessibility features:
  • Enables navigation by using the keyboard.
  • Communicates all information independent of color.
  • Interfaces that are commonly used by screen readers.
For more information about accessibility features in the starter stores, see:
Mobile starter stores
Mobile starter stores, which include Hybrid, Native, and web starter stores for smartphones and tablets do not support accessibility. Although mobile applications can be partially accessible, they cannot currently achieve full accessibility under the IBM Software or web checklist. This is due to inconsistent keyboard availability and screen reader applications.
Tools
Management Center
  • All Management Center functionality is available by using the keyboard for navigation instead of the mouse, except for:
    • The store preview tool that launches from Management Center.
    • The Activity Builder in the Marketing tool.

    For a list of keyboard shortcuts, see Management Center keyboard shortcuts.

  • Each field, button, and widget in the user interface has a focus indicator when it is in focus.
  • All information is communicated independent of color.
Tip: Some Management Center properties views have a rich text editor for users to enter formatted text, such as product descriptions. To create accessible HTML content with the rich text editor, use the Display HTML function above the editor.

This accessibility statement for Management Center does not cover any additional tools that launch from Management Center, such as Sterling Order Management.

Sales Center
Communicates all information independent of color. In addition, Sales Center provides keyboard shortcuts. For more information about shortcuts, see:IBM Sales Center keyboard shortcuts
Configuration Manager
The Configuration Manager provides the following accessibility features:
WebSphere Commerce Accelerator, Administration Console, Organization Administration Console, and Workspace Administration tool
WebSphere Commerce browser-based tools provide the following accessibility features:
IBM Sterling Configurator Visual Modeler
The IBM Sterling Configurator Visual Modeler is not accessible, see IBM Sterling Selling and Fulfillment Suite.
IBM Sterling Configurator
The IBM Sterling Configurator is not accessible, see Install IBM Selling and Fulfillment Suite V9.1.
Third-party integration
To support certain functions, WebSphere Commerce occasionally provides integration with third-party software, including Facebook and Bazaarvoice. In these cases, the third-party tool might not meet IBM accessibility standards. Adding third-party content to your storefront can introduce accessibility concerns. For information about third-party accessibility compliance, see the documentation that is provided with the third-party software.

Feature Pack 4 or laterTo support integration with Facebook, Facebook code is used in the store. The Like, Send, and Connect to Facebook buttons are provided by Facebook and do not comply with IBM accessibility standards. In addition, a user cannot undo a Like with the keyboard. Facebook code might meet different levels of accessibility based on which feature pack you are using.