Incorporate Results from 508 Audit into CMS Backlog

[gracekretschmer-metrostar]

User Story or Problem Statement

The CMS team needs to take the results from the 508 audit and incorporate those results into the CMS backlog.

Description or Additional Context

The 508 office did a spot audit of CMS and to begin that work the office needs the most common user flows, test accounts, and sandbox environment. They have delivered the results back to the CMS team, so now we need to review those results and incorporate their findings into the accessibility backlog.

Steps for Implementation

• Review the findings from the 508 audit to understand what needs to be fixed in CMS and the timeline expected from the office for the fix.
• For each finding, understand if the fix for the defect should be owned by the CMS or sitewide team.
• Document the next steps (either discovery on how to fix or plan of action for fix) into the CMS backlog.

Acceptance Criteria

• For each finding in the 508 audit, a correlating ticket is represented in either the CMS or sitewide backlog that outlines the timeline and expectations from 508 Office for addressing the defect and next steps towards a fix.

[gracekretschmer-metrostar]

@srancour could you identify if there's are any issues that need to be owned by Sitewide by Wednesday (ahead of Sitewide Sync)?

[srancour]

@gracekretschmer-metrostar All issues are located in the Epic #18503 and I have added the sitewide label on each ticket that I see as being owned by them plus our team. While only #19374 came specifically frome a page they own, the ones I tagged them in affect pages they own as well as ones we own. The individual issues that are for both them and us are #19368 (which seems to be related to #19375 so part of the solution is most likely on us to fix before it can be fully fixed), #19370 which is broken into #19371 and #19372, and #19374 (although as I commented in that ticket, even though this is on a page they specifically own, it might be more on us from a global standpoint for all tables throughout the CMS since it's something that we've tagged before that exists elsewhere).