In a standard end-user portal for a Pega application built in section-based UI (UIKit/Theme-Cosmos), automated accessibility testing tools may pick up on several duplicate ID attribute values in the DOM, such as “TABSPAN”, “PEGAGADGET”, "RULE_KEY" or "EXPAND-OUTERFRAME.”

The values of these IDs are internally used in Pega code for necessary functionalities in the section-based UI. The scope of addressing these IDs would require a redesign of current architecture and cause issues with backwards compatibility, so as such the product team is confident that any such elements containing a duplicate ID will not have an impact on individuals using assistive technologies. Any interactive elements and form fields that users directly interact with such as text inputs, radio buttons, checkboxes, etc. will all have their own unique id value generated.

In terms of WCAG, success criteria 4.1.1 Parsing is now obsolete. WCAG 2.2 indicates it as 4.1.1 Parsing (Obsolete and removed), along with a note. WCAG 2.1 and WCAG 2.0 now include this note from a conformance perspective: This Success Criterion should be considered as always satisfied for any content using HTML or XML.