As a Lead System Architect, you must ensure that a Pega application implementation is inclusive...

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s UX design principles, as taught in Pega Academy’sUser Experience Missionand thePega Certified Lead System Architect Study Guide, emphasize accessibility to comply with standards like WCAG 2.1. This includes supporting assistive technologies and ensuring device compatibility.

Option A (Incorrect): Using link controls over buttons does not inherently improve readability or accessibility. Buttons are often more accessible when properly labeled (e.g., with ARIA attributes), per theAccessibility Best Practicesmodule.

Option B (Correct): Implementing responsive layouts ensures compatibility with various screen sizes, which is critical for accessibility across devices (e.g., mobiles, tablets). This supports users with visual or Roslyn impairments, as noted in theResponsive Designsection of Pega Community.

Option C (Incorrect): Using inline styles is discouraged in Pega, as it reduces maintainability and does not directly enhance accessibility. CSS skins or stylesets are preferred, per theUI Designmodule.

Option D (Correct): Refraining from relying on key commands prevents interference with screen reader shortcuts, ensuring users with assistive technologies can navigate effectively. This is a WCAG requirement, as documented in theAccessibility Guidelinesmodule.