JAWS does not read CPM interaction driver as expected
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.
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.
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.
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.
100% found this useful