Skip to main content

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.

Using the Preflight tool to report accessibility compliance

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

When you build an accessible application, you want to ensure that you design your forms to comply with accessibility requirements and guidelines.

Design Tip: It is recommended that you use the auto-generated HTML option, allowing Process Commander to generate the HTML for a rule. The auto-generated HTML includes support for accessibility requirements. See supported features.

Then, to measure the accessibility compliance of your application, run the accessibility report from the Preflight tool. The accessibility report checks the value set in the Accessibility option for harness, flow action, HTML fragment, and HTML property reference rules in your application.

  • If the rule is auto-generated, the option is disabled and the level of accessibility is calculated based on the accessibility of its visual elements

  • If the rule is not auto-generated:
    • You set the option to “On” if you designed your HTML to comply with accessibility requirements
    • You set the option to “Off” if you did not design your HTML to comply with accessibility requirements

Note: When you use the Auto-generated option and allow Process Commander to generate the HTML for a rule, the rule is verified as accessible. When you set the option manually, it is up to you to test the code for accessibility. The report does not validate the code.


Running the Report

Select Application > Preflight. Then, select Accessibility Report from the list of Preflight reports.


Process Commander analyzes the calling relationships that are invoked at runtime from the top-level elements in your application. For each harness and flow action it calculates the accessibility and reports the compliance as a percentage.

For auto-generated rules, it is calculated as the number of visual elements on the form that are deemed accessible divided by the total number of visual elements. When including other auto-generated rules, counts are aggregated. Non-auto-generated rules are calculated as a single element. They are deemed accessible based on the value of the Accessibility option.


When a rule has a value less than 100%, expand the row to examine the calling relationships and to determine which visual elements are not considered accessible.

Place your cursor over the percentage to view a SmartInfo pop-up containing the accessible issue for a visual element.  You can open the rule by clicking on the link to review and edit it.


Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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