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.

Guidelines and design tips for accessible applications

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

The following list contains configuration guidelines and design tips developers should follow when building applications using existing Process Commander functionality intended to comply with accessibility standards.

  • Do not use px or px-fixed layouts — these layouts fix the width of windows and forms
  • Do not use inline styles — these styles fix fonts, colors and other style attributes
  • Do not use the deferred load feature
  • Avoid the use of AJAX-based displays — these typically require use of the mouse. Features to avoid include: conditional hide and show displays, onscreen calculations, and hover-over displays on worklists and harnesses
  • Avoid using multiple icons — initial focus will be placed on them and not on the first input field
  • Provide shortcut keys for frequently used buttons, fields, and actions

 

 

Related Topics

About the Accessibility Framework

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.

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

Close Deprecation Notice
Contact us