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 heading title as expected



User has configured a section on one of our application screens to include multiple other sections. Every included section/dynamic layout, has the Heading Level configured. For example: 'Heading 2' and has a title specified.

When accessible users use JAWS to navigate through fields on this screen and they arrive at the included section/layout Heading, the heading is not read out as expected. JAWS reads - Region <Title> edit type in text.

The heading is not an editable field hence “type in text” is unjustified and misleading to the visually challenged.

Error Messages

Not Applicable

Steps to Reproduce

1. Use Internet Explorer 11. Do not use the PegaWAI ruleset.
2. Enable JAWS.
3. Launch the Case Manager portal.
4. Create a General Task work object and get to the Perform harness.
5. With JAWS enabled, after the page is loaded, use the TAB key to navigate through all elements on the page until you reach the highlighted heading. Listen to what JAWS reads.

6. Now navigate to the next highlighted heading. Listen to what JAWS reads.

7. If you use Shift+TAB and navigate back to highlighted heading, listen to JAWS.


Root Cause

Pega generally supports the JAWS version which existed when a particular version of Pega product is released. In this case, JAWS 18 did not exist when Pega 7.2.1 is released. So JAWS 16 and 17 are supported.

The below points lead us to believe that the reported issue is more to do with the JAWS product rather than Pega.
1. In Internet Explorer the behavior is very inconsistent - there are certain scenarios where in JAWS does not read "Edit type in text" for non-editable field and sometimes it does.
4. The markup generated by Pega in this scenario has all the necessary aria-attributes to call out the Heading.
6. Markup from the use case was tested outside of the Pega product as independent HTML, and one can see that JAWS behavior is still the same.


Given the above root cause, below are some of the recommendations to work around the problem:

1. Use the Chrome browser (the reported use case does not read "Edit type in text" for non-editable heading elements).
2. Engage the ARROW keys i.e. up and down arrows instead of TAB keys. JAWS reads the heading as expected.


Published December 14, 2016 - Updated October 8, 2020

Was this useful?

0% 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