Accesibility in SAP: Is JAWS compatible with the SAP CRM webclient

[Former Member]

Hello,

For a customer project I am investigating if JAWS(screenreader tool) is compatible with the SAP CRM webclient. Neither help.sap.com or SCN provides information. Does anyone have experience with implenting JAWS for SAP CRM webclient and can you please share that? Including lessons learned?

Kinds regards,

Jeroen Zijlmans

[cris_hansen]

Hi Jeroen,

The CRM Web Client UI has to be compliant with the SAP Accessibility Standard 3.0 and the relevant international accessibility standards Section 508 and WCAG 2.0. Accessibility is mainly guaranteed by the Web Client UI framework since CRM 2006s/2.

As long as screens are developed by the UI Configuration Tool, an application developer need not worry about accessibility. In this case, the framework guarantees that the resulting screen is compliant with accessibility requirements.

For screens that are created without the UI Configuration Tool (for example, Java-Applets, ActiveX Controls, views that contain native HTML, or views that contain freestyle THTMLB), developers are responsible for making sure that the screen matches all relevant accessibility requirements.

Accessibility topic includes information about the following areas: Keyboard Support all interactive elements (links, fields, buttons, and so on) on a screen can be reached and executed by keyboard actions special navigational shortcuts to set the cursor focus to certain screen areas (via Personalization - Personalize Shortcuts) Support for Visually Impaired Users high contrast skinScreen Reader Mode screen reader mode can be switched on via Press linkPersonalize to open the Personalization pageIn blockSettings press linkPersonalize SettingsUnderScreen Reader Mode section check the checkboxEnable additional support for screen readersrecommended screen reader to use for the CRM Web Client UI is JAWS with version 8.0 (in virtual PC cursor mode) Features of Screen Reader Mode extended tool tips for most screen elementssome UI elements are rendered differently (for example, native dropdown list box, input field instead of date or time picker, no spinning wheel, no navigation bar slider, no table graphic (chart) feature, no column drag & drop in tables, dropdown list box instead of hover menu in central search iView in portal integration) to ensure that all elements have label, hidden labels are rendered for elements which do not have a label at the end of a form alert if there is a message in the message areafor layout tables (thtmlb:grid and chtmlb:configGrid) "DataTable=0" is rendered so that JAWS 8 and above recognize layout table (and do not announce the table), for normal tables ( thtmlb:cellerator/chtmlb:configCellerator) "DataTable=1" is rendered for an empty table to overcome a JAWS bug.

I hope this helps.

Regards,

Cris

[Former Member]

Thanks Cris this is what I was looking for.

[Former Member]

Good day,

Please assist with the below:

Is JAWS compatible with SAP CRM 5?

If Yes, please provide me with configuration steps....

Thank you.

Desmond