Skip to main content

Accessibility features

The UI components of Pega Platform™ support W3C Web Accessibility Initiative (WAI) standards. Web Accessibility permits users with visual or other impairments to leverage assistive technologies, such as screen readers and keyboard navigation. 

Pega Platform automatically inserts ARIA (Accessible Rich Internet Applications) attributes into its UI content. There is no need for additional configuration settings, such as manually including the PegaWAI ruleset and enabling accessibility for access groups. Accessibility features are available within Cosmos React and Theme Cosmos applications.

Accessibility features

Accessibility is a design principle rather than a set of options that the user can enable or disable. Many accessibility features are included by default in the architecture of Pega Platform applications. For example:

  • Keyboard and screen reader navigation – Reach and operate any UI element by keyboard alone.
  • WAI-ARIA roles – Provide additional information about your application to assistive technologies.
  • Labels – Labels, placeholders, and alternative text help users understand the UI and visualize the tasks that they must complete.
  • Table navigation – Optimized table layouts support WAI-ARIA keyboard navigation standards.
  • Skip links – Skip links provide users with tools to navigate to the most important parts of the application.
  • Error alert management – Assistive technology reads error messages and moves the focus to the field containing the error.
  • PDF/UA files – Content that can be generated as PDF files can optionally be generated to comply with the accessible PDF/UA ISO standard, thus improving accessibility comprehension.

For more information on the default accessibility features available in Pega Platform, see Out-of-the-box accessibility features.

Customizable accessibility features

Apart from Pega Platform's default accessibility features, there is also the flexibility to change default settings to support any particular business needs. This helps by providing flexibility when building UI features, but involves more maintenance.

For more information on customization of your UI, see Custom configuration options for accessibility.

Special considerations

If you upgrade an application from a previous version, you must remove the PegaWAI ruleset from the list of production rulesets for the application and all of its access groups.

With the Accessibility Inspector tool, you can identify and rectify some of the accessibility issues within your application. The Accessibility Inspector is available in both App Studio and Dev Studio. For example, Accessibility Inspector includes a color confusion simulator that helps you check whether the colors that you use in your application are readable to users with color blindness.

For more information on accessibility features in Pega Platform, see the following Pega Community and Pega Academy content:



This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

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 Academy 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