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 after the start of this release cycle..

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 to help teams make products and apps accessible (compliant with standards).

• 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 change summary2024 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.

Issues fixed: 13
Help files updated: 5
New issues triaged: 25
Versions released: 3 (v3.1.75, v3.1.76, v3.1.37) to the stores

• 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 communications, 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, but are part of the Comms..

1. ACT 46ca7f: Element marked as decorative is not exposed - Expected failed, but returned passed #1938
2. ACT b33eff: Checker rule element_orientation_unlocked marks failed test case #4 inapplicable  #1958
3. ACT: Add fail reason to img_alt_null for conflicts in attributes and map to ACT rule 46ca7f #2013
4. Create a spreadsheet in the builds with rule information #2004
5. Resolve element role when multiple values are provided  #1973
6. Update the element role calculation logic in the engine #1972
7. Merge legacy NodeWalker to DomWalker #1971
8. Categorize the engine utility functions #1974
9. Update ARIA definition and calculation #1977
10. [BUG]: False positive of no accessible name for img with alt text #2003
11. Add "ACT testing and mapping in the Checker" to the wiki #2029
12. Add new WCAG 2.2 rules to the default policy starting Oct 1. #2058
13. Revisit text_block_heading rule to fix issues #2037
14. Conflict cases when aria-autocomplete and autocomplete are used together #2052
15. Should the rule imagebutton_alt_exists contain the label check (label as parent or label for attribute)? #2057
16. [BUG]: The A11y tool looks for label/title for an element with role=presentation #2060
17. [BUG]: False positive for "The value "foo" of the 'for' attribute is not the 'id' of a valid <input> element" #2068
18. Rewrite accessible name module for the rule engine #2055
19. Fix ruleID target_spacing_sufficient for potential_overlap to ignore this kind of inline links  #2070
20. [BUG]: Differences between Chrome and Firefox #2028
21. Open issues for ACT implementation inconsistencies #2030
22. [BUG]: IBM Docs WFM Accessibility scanner flagging new violations that the in-browser scan does not find #2065

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

Lessons learned and observations

• Some issues require investigation with multiple browsers, such as Firefox vs Chrome, JAWS screen reader, and Carbon implementations.

[philljenkins]

Start reviewing this Epic. At the end of sprint 12 we should have the following documented in this Epic to share at the final Showcase:

Epic details

• Did you accomplish your Hill? If not, what is remaining?
• Will your final playback match what is recorded for Playback Demonstration?
• Collect your metrics
• Comm's

Definition of Done

• Indicate what has been completed
• Identify what needs to happen in the final sprint
• Lessons Learned about this activity or Release
  • Somme issues require investigation with multiple browsers, JAWS screen reader, and Carbon implementation.