R4.0.5 ACT Mapping

[marcjohlic]

Link to Squad 2 R4.0.5 MVP Mural

Epic Details

User Story: what does the user need – include some sort of WOW statement:

• Users want the Checker to align with industry standard (ACT) and to have fewer bugs and false positives

Playback Demonstration: what will you be able to show at the end of the release / point release to demonstrate how you accomplished your user story. If possible, list what you target to demonstrate for each sprint:

• Review ACT mapping (rules to Success Criteria (checkpoints) against Checker's and see if Checker has conflicts - where Checker disagrees, and decide if Checker wants to do anything about it. Review recommendations with Subject Matter Experts (SME Connection)
• ACT published and proposed rule - gaps
• ACT rule status sheet
• Take discrepancies to SME Connection to decide what needs to have a Git issue

Metric: how can Checker squad measure the impact of this change:

Comms: when completed who should you communicate this change to, what will you tell them (concisely), and where?:

• [ ] Slack poster
• [ ] Accessibility Update Call
• [ ] ACT Community

Definition of Done

• [ ] All content has been reviewed for grammar, spelling, style and technical accuracy
• [ ] All code committed to main branch
• [ ] All unit tests pass (including accessibility)
• [ ] Demo works in staging environment
• [ ] At least one performance metric / monitor constructed