Accessibility

This chapter provides information about accessibility in your Web application. It includes the following topics:

Introducing Accessibility

Oracle's Siebel Business Applications are designed to meet the needs of users with disabilities, and conform to many of the guidelines specified by the Web Content Accessibility Guidelines (WCAG) 2.0.

Oracle is committed to improving support for accessibility features and uses popular WAI-ARIA compliant assistive technologies, such as screen readers, speech synthesizers, and alternative keyboards to test applications.

Oracle provides a large number of keyboard shortcuts (also known as access keys or hot keys) to enable all users to navigate Siebel CRM elements, such as applets and records, without using a mouse in addition to supporting those provided by screen readers.

For more information about Oracle's Accessibility Program, visit the Web site at: http://www.oracle.com/accessibility/

Accessibility in the Web Application

Where possible and practical, the design of your Web application meets the Web Content Accessibility Guidelines (WCAG) 2.0 AA level and US Section 508. Oracle shows leadership in not only attempting to meet mandates, but in providing very practical and usable business solutions for business users and consumers that require accessibility features. Accessibility is always enabled and requires no special tasks for users. No action is required to enable accessibility features outside of availability of appropriate assistive technology.

In order to address these accessibility standards, your Web application relies on the WAI-ARIA coding techniques (Web Accessibility Initiative - Accessible Rich Internet Applications). One example of WAI-ARIA t hat has been implemented are Regions, which allow users to navigate to various parts of a page such as the Menu, Toolbar and Applets using keyboard shortcuts provided by assistive technology that has also implemented WAI-ARIA.

Note: To fully leverage Accessibility in Web applications, end users must use browsers and assistive technologies that have implemented WAI-ARIA. Only a subset of accessibility features is available without support of WAI-ARIA.

For information about WCAG 2.0, visit the following website: http://www.w3.org/WAI/

For more information about US Section 508, visit the following website: http://www.section508.gov/

Keyboard Navigation in Accessible Rich Internet Applications

Your Web client application supports Accessible Rich Internet Applications (ARIA). ARIA define a way to make Web content and Web applications more accessible for people with disabilities and easier to use for all users. ARIA especially help in navigating within dynamic content and in using advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.

ARIA include a collection of common, semantic landmarks that apply to each navigable region in an application. These landmarks allow a person with disabilities to use an assistive-technology product, such a screen reader, to navigate in an application. Landmarks provide a consistent navigation experience in which a pointing device, such as a mouse, is unnecessary.

Examples of landmarks include: the application-level menu, the application toolbar, screen names, view names, lists, visibility filters, and forms. If you use a JAWS screen reader, press CTRL + INSERT+; (semicolon) to display a dialog box that describes the landmarks.

For information about ARIA, visit the Web Accessibility Initiative website at:

http://www.w3.org/WAI/

Utilities for Visually Impaired Users

In your Web client application, people with visual impairment can use screen magnification utilities to enlarge selected text and other on-screen elements for easier viewing. Several operating systems supply magnification utilities. You can also purchase these utilities from third-party vendors.

Your Web client application supports magnification utilities that work in browser-based applications. In your Web client application, people with visual impairment can use zoom features and high-contrast options for browsers to facilitate viewing.

Screen Readers

Your Web client application supports screen readers that work in browser-based applications. Screen readers provide an audible description of the field contents as you navigate through the user interface. It is recommended that you use screen readers that support Accessible Rich Internet Applications (ARIA).

Your Web client application supports screen readers that are browser-compatible because it is a standards-based Web application. Some browsers interpret Accessible Rich Internet Applications (ARIA) and Web Content Accessibility Guidelines (WCAG) 2.0 better than other browsers. Use the appropriate browser for your implementation. Consult with the vendor for your screen reader to use it with your Web application.

If you use a screen reader, then you hear the levels of the bar region that denote user interface areas. The following table shows the level of the bar region that corresponds to each user interface area that sighted users work with.

Table Levels of Bar Region for User Interface Areas

User Interface Area	Level of Bar Region
One of the following: The list that appears when you click the Side Menu. The screen tabs that appear across the screen, at the start of a page. The screen names that appear in tree format on the side of the screen.	First level
One of the following: The views that appear in the second level view bar. The views that appear in a link bar under the screen tabs. The view names that appear in tree format on the side of the screen.	Second level
One of the following: The views that appear in the third level view bar. The view tabs that appear lower on the screen.	Third level
One of the following: The subviews that appear in the fourth level subview bar. The subviews that appear in a link bar under the view tabs lower on the screen. The subviews that appear when you hover the cursor over a view tab lower on the screen.	Fourth level

Utilities for Physically Disabled Users

In your Web client application, people with physical disabilities can use utilities, such as soft keyboards, voice control, and StickyKeys, to work with data. The keyboard-usage model for the Web application client recognizes these utilities. For more information about using these utilities in browser-based applications, consult the vendor for the utility or the vendor for the operating system.

19Accessibility