R6.3 Rules

[philljenkins]

The Checker has some remaining issues in the backlog that need to be resolved as efficiently as possible. See Bug Epic for new issue that came in from our users.

Epic Details

• Hill:
  Users will have an improved experience with the checker 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 rules showcase template to explain the issue, including user impact, supporting standard(s), what's broken, fix, help, mapping, and test case(s) to show the issue and the fix.

• Metric: # of rules and help files that are fixed and merged. The Engine rules 2024 is updated after each new or fixed rule, help, or Engine change.

  • The end of the release will have Release outcome on Mural, including the number of rules created or updated and the number of issues or false positives/negatives fixed.
  • Each Checker version deployed to the stores also includes the Release Notes that includes the list of fixes and features that users read.

• Comms: The team's overall release notes posted to Slack, Office Hours, other developer meetings, etc. will contain the engine changes, especially the new Checker Rule Set deployment dates that will be an integral part of the checker and tools, such as the Rule Set Options in the Checker Settings. Note: Improvements to the UI and new features are not part of this Rules/Engine Epic.

• ACT 46ca7f: Element marked as decorative is not exposed - Expected failed, but returned passed #1938

• ACT b33eff: Checker rule element_orientation_unlocked marks failed test case #4 inapplicable  #1958

• ACT: Add fail reason to img_alt_null for conflicts in attributes and map to ACT rule 46ca7f #2013

What project/section is the Epic for?

• checker
• ACT Checker implementation report

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