SA-15680

Summary

Pega 7.1.8 does not generate ARIA tags for autocomplete control. This causes screen reader to miss the following critical information:

• How to use the control. As it is not a conventional drop-down, it is required to guide the user to type and use “Up” and “Down” arrows to get matched results. Screen reader does not read this information to visually challenged users.
• When typing for Auto-control, it provides options below with matched text displayed in bold. Screen reader reads only the matched (displayed in bold) and not the whole result option.

Error Messages

Not Applicable

Steps to Reproduce

1. Create a screen with Autocomplete feature (using Pega Web Mashup) with good number of results.
2. Use a screen reader (such as JAWS) to know what it reads for the user.
3. When you reach autocomplete field, reader does not read any instructions about how to use it.
4. When you start typing in for the auto control field. Screen reader reads only the matched (displayed in bold) not the whole result option.

After fix:
Screen reader announces:

• To use arrow button to scroll through result set
• Reads out the text highlighted when scrolling through the result set (when using the up or down cursors)
• Announces text such as “Reached the end of the list” and “Reached the beginning of the list” when needed.

Root Cause

A defect in Pegasystems’ code or rules. The HTML generated by the Pega Web Mashup does not have the ARIA attributes. The PegaWAI ruleset was tested as a possible solution but it introduces too many elements that are not required, hence a HFix is used to generate specific ARIA tags.

Resolution

Apply HFix-24247.