Skip to main content

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

Accessibility standards in Pega Platform

Updated on December 13, 2022
Applicable to Cosmos React and Theme Cosmos applications

Pega supports users with disabilities by continuously integrating the W3C Web Accessibility Initiative (WAI) standards into the architecture of applications that you develop. As a consequence, applications include accessibility features by default, which makes them more convenient for users who rely on assistive technology.

WCAG standards

Pega strives to create an inclusive product experience by following the W3C Web Content Accessibility Guidelines (WCAG) 2.1 AA. Pega Platform components use the recommended standards to reach compliance with Section 508 of the US Rehabilitation Act, the European standard EN 301 549, the European Accessibility Act, and the Barrierefreie-Informationstechnik-Verordnung (BITV).

Consequently, all applications that users develop include accessible markup by default. As a developer, you only need to put content into the existing out-of-the-box framework.

For example: To make your application accessible, you might need to add helper text to controls and ensure that all layouts use proper headings that reflect the structure of the document. If you use custom components that have unusual functions, such as clickable layouts, you can assign ARIA roles that match the document role manually.

The following image illustrates out-of-the-box accessibility settings in a sample search field.

Sample search field configuration
Snapshot of out-of-the-box labels and helper text settings.

Web Accessibility Initiative resources

For more information about WAI-ARIA roles, accessibility standards, and best practices for designing for people with disabilities, go to the Web Accessibility Initiative website.

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