Links may not function; however, this content may be relevant to outdated versions of the product.
Pega Platform extends support for accessibility to enable potential compliance with the Web Content Accessibility Guidelines (WCAG) 2.0 A and AA. WCAG is a product of the W3C Web Accessibility Initiative (WAI), an effort to improve web and browser accessibility for people with disabilities. This enhances the existing support for guidelines established by Section 508 of the United States Rehabilitation Act.
Disabilities can include blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity, and combinations of these.
In Pega Platform, accessibility features have been improved in the platform. An application that is implemented with the ruleset enables users with disabilities to access the full range of user interface capabilities. Developers can create work portals that are enabled for accessibility, using composite portals.
See Accessibility features for an itemized list of feature improvements.
- Accessibility and Pega Platform
Pega Platform uses the Accessible Rich Internet Application (ARIA) roles to support accessibility. WAI-ARIA roles are a World Wide Web Consortium (W3C) ontology that specifies roles, states, or properties for each element. WAI-ARIA roles provide semantic information about features, structures, and behaviors allowing assistive technologies to conve
- WAI-ARIA Roles
Pega Platform supports accessibility through the use of Accessible Rich Internet Application (WAI-ARIA) roles. The WAI-ARIA role indicates the type of content or functionality within the dynamic layout. Roles may be added to a dynamic layout specify the role of the dynamic layout. By default, WAI-ARIA roles are assigned to screen layouts and dynam
- Accessibility features
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.
- WAI-ARIA roles in a screen layout
Screen layouts include WAI-ARIA roles by default. The table below details the area of the screen layout and the corresponding auto-generated HTML tag and the WAI-ARIA role assigned to that area by default.
- Adding WAI-ARIA roles to a Dynamic Layout
WAI-ARIA roles are added to a dynamic layout to provide semantic information about the role of the dynamic layout on the page. The settings for WAI-ARIA roles appear on the General tab of the dynamic layout properties modal dialog. To add an ARIA role to a dynamic layout:
- Adding a main content link to a dynamic layout
A main content link allows a user navigating an application with the keyboard to tab through the interface to pass over non-essential elements and move directly to the most important area of the page. Tabbing past navigation, banners, and non-essential content saves the user time in reaching the main content area.
- Using the Accessibility report
Use the Accessibility report to assess your application's level of accessibility compliance. The report uses a chart to illustrate accessibility compliance by rule type and percent (%) of accessibility. You can drill down in the chart to display additional levels of detail about individual accessible elements within the rules.
Previous topic Accessibility and Pega Platform Next topic Accessibility features