R6.1 Rules

[MHoov]

Epic Details

• Hill: Users will have an improved experience with the checker or tools because the engine rules will be more specific and easier to understand, and more compliant with community test cases (ACT). Overall, IBM will have better and more compliant accessibility tools.
• Playback Demonstration: Each sprint replay will use replay template to explain the issue, including user impact, supporting standard(s), what's broken, fix, and test case(s) to show the issue and the fix.
• Metric: The issue will be fixed based on the defined priority. The Engine rules 2024 is updated after each new rule or fix. The end of the release will have Release outcome, including the number of rules created or updated and the number of issues or false positives/negatives fixed.
• Comms: The overall release notes, update calls, other developer meetings, etc. will contain the engine changes that will be an integral part of the checker and tools.

What project/section is the Epic for?

• toolkit
• acs
• a11y central
• acr
• requirements
• special airplane
• checker
• carbon
• standards
• other

Definition of Done

• Results are added to the Release Mural with a description of what was accomplished, KPIs, etc
• 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
• The Engine rules 2024 is updated.