Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Setting accessibility configuration options

Updated on September 14, 2020
Note: This article is not compatible with Pega Platform™ 8.1 and later.

The PegaWAI RuleSet contains four controls that provide you with configuration options to disable specific elements of accessibility support.

The controls are shipped enabled to provide the respective support without the need for additional configuration. They are configured in the form of When Condition rules; when disabled, the respective options are removed as accessible user features.

 

Control Options

 

Error Handling Control — Rule Instance :[email protected]

This control enables the following accessible error handling features:

  • Client-side validation that displays validation error messages in a popup confirmation box
  • Error messages displayed at the top of the form with “Error Occurred” text added to the window title
  • The red X error indicator (with hover over error message) is replaced with the error message displayed next to the field
  • Shortcut key ALT/E that places focus on the error field and moves through the errors in field order sequence         

 

Style Control — Rule Instance: [email protected]

This control enables the sample accessible style sheet.

Date Control — Rule Instance: [email protected]

This control enables accessible Date and DateTime formatting.

Frames Control — Rule Instance: [email protected]

This control enables the display of action iframes without the use of iframes and provides accessible alternatives for the Take Action drop-down box.

Disabling Control Options

To disable a control option:

    1. Copy the When rule that is in the PegaWAI RuleSet to your RuleSet.

  1. On the Conditions tab, change the defaulted when condition from true to false.
  2. Save your changes.

Related Topics

About the Accessibility Framework

  • Previous topic Satisfying accessibility requirements in composite portals (6.1)
  • Next topic Using the Preflight tool to report accessibility compliance

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us