Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Accessibility features

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

Pega Platform uses the WAI-ARIA technical specification to improve the accessibility and interoperability of web content. This extends the semantic information necessary to make content accessible to people with disabilities - for example, those who rely on screen readers or who cannot use a pointing device, such as a mouse.

Among the accessibility features that have been added or improved by enabling assistive technologies (ATs) in Pega Platform are the following:

Control/featureDescriptionAdded in
AutoCompleteAutocomplete controls support accessibility.7.1
ButtonsA unique ID for buttons has been added to support getting the focus.7.1
Collapsed textThe collapsed text area is non-editable.7.1
DynamicSelect and PromptSelect Loss of context upon selecting DynamicSelect and PromptSelect controls is avoided with the use of a Go button. 7.1
Error messagesPage error messages are readable by ATs.6.x
Field-level error messagesField-level error messages are readable by ATs when there is a change that displays the error, such as for a failed validation.6.x
Grid categorizationAT support added for the new grid categorization capability.7.1
Grid edit modesMade the click action for all edit modes accessible.6.x
Grid expand/embedGrid expand/embed and pane/show capabilities available to AT users.6.x
Grid filter and sortAT support added for grid filter and sort capability.6.2
Grid paginationGrid pagination features are available to ATs.6.2
Grid row presentationGrid row numbering and freeze header features are accessible.7.1
Grid table contentGrid table content is accessible to AT users.6.x
IconsThe icon control is accessible based on assigned actions.7.1
Modal windowsModal dialogs are clearly identified and work with ATs like JAWS.7.1
Multi-Select listsUsers can select more than one item from a list.7.3.1
New layouts Dynamic layouts and layout groups use the WAI-ARIA specification for full AT support.

Users can focus on the expand/collapse icon in a layout using the Tab key. Expanded/collapsed state is announced for those users that use screen readers.

Overlays Identification of overlays and working within them without needing a pointing device has been enabled.

Overlays are announced by assistive technologies and can be dismissed by hitting the Esc key. This applies to all overlays, and modal dialogs launched as local actions, and popovers that are part of the auto-generated UI, such as the grid filter panel.

Portal structural elementsThe screen layout (that is, the structural arrangement of any page or section) can be read and comprehended.7.1
Radio buttonsAll radio button options can be read by the screen reader.7.1
Read-write controlsRead-write controls provide proper labels or text alternatives.7.1
"Registry" of keyboard shortcutsTabs, arrows, and all modifier keys that are programmatically handled are stored in a single file location.7.1
Rich Text EditorRich text editor controls can be exited using the keyboard alone.6.x
Skip to content areaKeyboard-only and audio-assisted users can reach the main content area (that is, the work area/dynamic container) without having to repeat portal navigation each time.7.1
Smart infoHeader and content text is readable; keyboard tabbing works with actionable and editable items; the ESC key returns the focus to the element that invoked the smart info.7.1
Smart tipsSmart tip text is read by a screen reader; the focus remains on the invoking control.7.1
Wait indicator The wait indicator announces "Loading content" through an assistive technology as soon as the wait indicator is displayed, and announces "Loading completed" when it disappears.
  • Page load status

    The throbber, which indicates the status of a page loading, communicates the page load status to an assistive technology, such as JAWS. By default the content announced is "Loading content". This text is editable in the pyThrobberLoadingText property. The assistive technology is also notified when the loading process is complete. By default, the assistive technology will announce "Loading complete". This text can be edited in the pyThrobberLoadingCompletedText property.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us