Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

JAWS does not read CPM interaction driver as expected

SA-5547

Summary



With JAWS active, when a developer tries to test using the keyboard to navigate through the Customer Process Manager (CPM) interaction driver on a CPM end user portal, he is unable to engage the TAB key to get to/launch intents. Navigating with the arrow up/down keys works.



Error Messages



None


Steps to Reproduce



1.Open a CPM end user portal
2. Arrive at the Interaction driver screen.
3. Try to engage JAWS key strokes or TAB key to navigate through the interaction driver.


Root Cause



In the CPM framework v07.12, the new default implementation of the interaction driver is based on PRPC controls which are navigable using the TAB key.



It was found that the Developer is using the old CPM implementation of the interaction driver which is based on handwritten HTML code that does not have markup to support accessiblity.


Resolution



The explanation for this behavior is as follows:

Use the new implementation of the CPM Interaction driver in CPM 7.12 that is based on PRPC controls that have accessibility support.

 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us