Scenario 1: iframe is missing title attribute
Pega mashup generates <iframe>
elements without title attribute. This throws an accessibility compliance issue on assistive technologies such as screen readers.
Explanation
Web accessibility compliance recommends that <iframe>
elements must have a title attribute to support assistive technologies. However, Pega web mashup code creates <iframe>
elements without title attribute. Therefore, users find it difficult to determine whether <iframe>
elements contain relevant information.
Environment
The issue is reported in Pega Platform version 8.7.4 on-premises.
Solution
Perform the following local change in Pega mashup code:
<script async="false"> window.addEventListener("load", (event) => { var iframeEle = document.getElementById("PegaGadgetIfr"); iframeEle.title = "title here"; }); </script>
Scenario 2: <iframe> element is incomprehensible
Users are concerned about <iframe>
elements that are used in Pega applications because of accessibility compliance standards.
Explanation
It is difficult to predict where <iframe>
elements are being used in Pega applications. <iframe>
elements are generated by Pega UI engine and are used in Pega web mashup.
Environment
The issue is reported in Pega Platform 8.6.1 on client cloud.
Solution
In Pega applications, when <iframe>
elements are created, they automatically have the title attribute defined. Hence, <iframe>
elements become accessible to users who use assistive technologies such as screen readers.
Scenario 3: 508 accessibility compliance issue
Values of multiple id attributes of active DOM elements are found to be non-unique. This throws 508 accessibility compliance issues while testing applications.
Explanation
The values of id attributes of immutable DOM elements such as <iframe>
or <div>
are generated automatically and are internally used in Pega application code for functionality support. An attempt to edit id attributes of these elements can degrade application performance and cause backward-compatibility issues.
Environment
The issue is reported in Pega Platform version 8.6 on-premises.
Solution
In Pega applications, web mashup code generates <iframe>
or <div>
elements and adds them to the existing DOM structure. The newly generated DOM elements are immutable. It is expected behavior in some scenarios.