Question

Accessibility Report in Pega 8.2

In Pega 7.x there was an option to run an Accessibility Report described here:

https://community.pega.com/sites/default/files/help_v72/tools/applicationpreflight/accessibilityreport.htm

In 8 this looks to have been removed and replaced with the Accessibility Inspector. The tool seems to audit individual pages while being viewed in the application. We have a need to create a report of the Accessibility findings for every form/step in our application. How can we create this in Pega 8.x?

***Edited by Moderator Marissa to update platform capability tags****

Correct Answer
October 17, 2019 - 1:42pm

It does look like it was removed. However DevHelp seems to still have references to it
https://community1.pega.com/community/pega-support/question/accessibility-report-pega-82

So this looks like a documentation bug now. (Unless the report still exists somewhere buried in the menus and I cannot find it. But I believe this no longer exists)

Historically this report served a purpose but the product and accessibility standards quickly outgrew this. So the report was misleading in terms of providing you some sort of accessibility/compliance score.

For this reason, and others the report was removed from the product at some point.

Accessibility standards/testing have many levels of compliance and subjectivity around it. So it is best to have an unbiased tool, which can also be updated as standards change. Think in terms of third party tools such as FireEyes, etc.

---

I would like a product owner to confirm my assessment here though.

Comments

Keep up to date on this post and subscribe to comments

October 17, 2019 - 1:42pm

It does look like it was removed. However DevHelp seems to still have references to it
https://community1.pega.com/community/pega-support/question/accessibility-report-pega-82

So this looks like a documentation bug now. (Unless the report still exists somewhere buried in the menus and I cannot find it. But I believe this no longer exists)

Historically this report served a purpose but the product and accessibility standards quickly outgrew this. So the report was misleading in terms of providing you some sort of accessibility/compliance score.

For this reason, and others the report was removed from the product at some point.

Accessibility standards/testing have many levels of compliance and subjectivity around it. So it is best to have an unbiased tool, which can also be updated as standards change. Think in terms of third party tools such as FireEyes, etc.

---

I would like a product owner to confirm my assessment here though.

October 30, 2019 - 9:00am

The issue with the new solution is that we need to step through every page of every process to make sure that we're evaluating all of the rules. Removing the report really adds a lot of labor to testing complex Pega solutions, since the report would automatically check every area of the application. Of course, if this is the new solution going forward, we'll just have to bake the testing time into our deliverable timelines.

Thanks for following up, having an answer that's not ideal is better than no answer.