Important:

          Term ‘Users’ in this blog refer to visually challenged users, who have up to 90% visual challenge.

Background: As part of my previous projects, I got an opportunity to work for accessibility requirements for visually impaired users. This was an unique project experience working on different set of requirements. I had to first understand the business requirements from a different angle( interpret disability of user) and provide appropriate solution. As part of requirement gathering process, Identify the business processes, SAP CRM WEB UI screens navigated by user. Solution should simplify the WEB UI screens with less cluttered information for smooth navigation and uninterrupted process execution. On one project I worked with IS Utilities customer service adviser user, accepting inbound calls, making outbound calls and successfully making sales. On another project I worked with Grantor Funding officer working in back office reviewing customer applications and approving funds.

Users navigated through SAP CRM WEB UI screens using keyboard short cuts and with help of screen reading software.

WEB UI Navigation:

  • Configure shortcuts for keyboard navigation
  • Making sure each UI element can be navigated by using ‘TAB’ key
  • Each UI element has appropriate text and can be read by the screen reading software
  • Making sure all the required information for the user is present on the same WEB UI screen, preventing forward and back navigation.

Screen reading software:

  • Every screen reading software has it own pros and cons, based on the application and OS they are used with
  • Internet Browser compatibility of screen reading software
  • There are some scripts written for JAWS software, which will be triggered as user starts using the software. Its a local deployment.

Custom Development/Changes:

  • Simplified UI screens, with only required information
  • Default the information wherever possible
  • Remove the hyper links

Challenges:

  • SAP CRM WEB UI Tables and table line navigation
  • Hyper links
  • Transaction launchers
  • Custom developed UI elements
  • UI Screen in display and edit mode
  • Attachments to SAP CRM Objects
  • Data loss pop ups
  • Screen reader software does not indicate the current position of the cursor
  • Forward/backward Screen navigation from hyperlinks
  • Un-necessary Messages (Error, Warning, Information)
  • Flickering of UI screen as soon as the screen reader software is activated

High Contrast Screens: High contract UI, typical combinations

  • White background and black text
  • Yellow background and black text
  • Pink background and black text
  • Blue background and black text

New high contract skins were developed

Fonts: Large fonts

Multi lingual: Other than English

Links for additional reading

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Anand S Bellad

    Hello Kapil,

    It’s good to land on this page where I can see actual experience with SAP CRM Accessibility.

    I am working for a client where they are planning to use JAWS with their SAP CRM 7.X and ECC 6.X. Looks like GUI should be fine but I am trying to gather little more details on CRM web UI. Please note they are upgrade from CRM 5.X to 7.X and they have bunch of transaction launchers (some are ECC tcode, some are FOPs and custom screens).

    Do you see a major problem with transaction launcher. And what are some key points one should keep in mind while working with JAWS.

    Thanks,

    Anand

    (0) 
    1. Kapil Patil Post author

      Hello Anand,

      Using JAWS for transaction launchers is bit of a challenge, specially keyboard navigation. A lot depends on how the transaction launcher is implemented. Recommendation is to launch within the WEB UI work space and not as pop up screen. Also, the number of fields displayed on the transaction launcher screen. More fields lead to more issues, affects user experience with respect to keyboard navigation.

      As your query does not indicate the scenarios user will be navigating using JAWS in your case, for me to answer specifically. But in general below are the key points may help you.

      – SAP CRM WEB UI Screen only has required information(WEB UI fields, Assignment blocks) for user to navigate smoothly

      – Less WEB UI table assignment blocks

      – Less scrolling (vertical/horizontal)

      I hope this helps.

      Thanks,

      Kapil

      (0) 

Leave a Reply