LinkedIn
Copied!

Table of Contents

Building an accessible UI

Version:

Only available versions of this content are shown in the dropdown

Build a UI that supports a more inclusive approach to users with disabilities. Accessibility features take advantage of ARIA roles that provide additional information about your application to assistive technologies, such as screen readers.

  • 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

  • Understanding accessibility

    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 establi

  • 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.

  • 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

    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 Inspector
  • Sections

    Use sections in conjunction with harnesses to define the appearance of user forms, rule forms, or composite portals.

  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

  • Setting PDF file versions

    Align the format of the files in your application with the needs of users who rely on assistive technology. Use this setting to improve accessibility by defining what type of PDF files your application generates.


100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.