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

Unable to navigate to read only UI elements using NVDA



With Non Visual Desktop Access (NVDA) screen reader, accessibility users are unable to navigate to sections of the UI that are read only using the keyboard. The screen reader is able to vocalize these read only labels/fields only with a mouse over.

Error Messages

No Error Messages

Steps to Reproduce

1. Install accessibility framework/ruleset
2. Install open source screen reader (NVDA screen reader -
3. Create section with nothing but labels and read only fields with values
4. Attempt to navigate to labels/fields using the keyboard

Root Cause

The root cause of this problem is software use/operation error.
If you use the TAB key for navigation, that will only work for "actionable" or "focusable" elements on the form. It won't work for non-actionable read only UI elements. If you mock up a sample HTML and run it outside of PRPC, turn NVDA/JAWS screenreader ON. It behaves the same, it reads out only actionable elements when you use TAB.


Use the Up/Down arrow keys for the screenreader to be able to navigate through all the elements on the form editable/read only.

Published January 31, 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