Support Article

Read-Only fields are not accessible by TAB and are not read

SA-29812

Summary



A standard HTML field that is read-only(‘readonly’ attribute is set) is focusable via keyboard tab/shift+tab keys, it is also readable by a screenreader tool like Job Access With Speech (JAWS) and it also gets listed on JAWS Form fields pop-up.

In contrast, a Pega read-only field does not have the above features. Why?


Error Messages



Not applicable


Steps to Reproduce



1. Make a field readonly as below:



2. At runtime, the field is not focusable via keyboard tab/shift+tab keys, it is not readable by a screenreader tool like Job Access With Speech (JAWS) and it is not listed on JAWS Form fields popup.



Root Cause



This behavior has been reviewed and confirmed to be an expected behavior with Pega configured read-only fields.

Resolution



In Pega, a tabindex is applied for HTML element and is made focusable only when if there is any action to be performed through key.

As per design in Pega, a <span> element is generated for read-only control (same as label), which is why it is not focusable.

For accessibility purposes, user can still read read-only fields via arrow keys.

This issue was determined to be a product enhancement request.

An enhancement request, FDBK-17186, has been created for consideration by Pega Product Management. 

Published October 31, 2016 - Updated November 11, 2016


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.