Accessibility, localization and UI troubleshooting
Original learning guide · Pega ’25 path · Content v1.0.0
Learning objectives
- Explain accessibility, localization and ui troubleshooting in the context of a loan application.
- Identify the configuration decisions and test an expected outcome.
- Recognize a common mistake before it affects users.
Understand the concept
Accessibility requires labels, keyboard access, clear focus and understandable errors. Localization includes translated labels and appropriate date, number and currency formats. Diagnose UI issues using actual task and data conditions before changing a shared view.
Constellation organizes user experiences around views, fields, templates and supported patterns. Build views from the data and tasks a persona needs. Use conditional behavior for relevant information, and provide clear validation messages close to the affected field. Accessibility includes meaningful labels, keyboard operation and errors that do not rely on color alone.
Complete intake using only a keyboard. Check long labels, zoomed text and a locale with different numeric formatting. Record one issue and a concrete expected behavior.
A configuration example
Create an applicant-details view with contact and income field groups. Display employer information only when employment status makes it relevant. Explain validation in user language, such as “Enter an amount greater than zero.”
Application: Loan Origination Case type: Loan Request Learning focus: Accessibility, localization and UI troubleshooting Given: a known applicant and a documented policy When: the configured step or rule executes Then: compare actual data and routing with the expected outcome
Conceptual configuration plan, not an importable Pega rule. Labels and tools vary by release. Use the official mission environment to inspect current screens.
Try it yourself
Complete intake using only a keyboard. Check long labels, zoomed text and a locale with different numeric formatting. Record one issue and a concrete expected behavior.
Design a compact intake form. Tab through the fields in a logical order. Check required fields and conditional sections. Test the same task at a mobile width and with longer translated labels.
For this lesson, focus your notes on accessibility, localization and ui troubleshooting. Record the inputs, configuration choice, observed result and one alternative that you rejected.
Common mistake
Knowledge check
Should conditional visibility be used as the only control for sensitive information?
Check your understanding
No. Visibility controls presentation. Authorization controls whether a user is allowed to access data or perform an action.
Go deeper with official resources
Pega Academy System Architect mission
Official ’25 certification objectives
