Epic: Bugs - High Priority Tool & Rule Issues from Backlog & Triages

[shunguoy]

The Checker has some remaining high-priority issues in the backlog and from in-release triages that need to be resolved in a timely manner. This Epic is for the issues remaining in the backlog and new issues that come from our users during this release cycle and are determined with priority during the triages.

Epic Details

Hill

Users will have an improved experience with the Checker because the engine rules will be more specific, 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.

Metrics

• Number 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.
• Each Checker version deployed to the stores also includes the Release Notes that include 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 communications, such as the Rule Set Options in the Checker Settings.

Issues assigned to this Epic:

1. Chrome and FF report differently for an input element #2081
2. Firefox skipped input checkbox accessible name check #2087
3. Chrome and Firefox report differently for link accessible name #2088

Other related Issues possible for this release

1. FireFox didn't report keyboard focus indicator visibility issue #2080
2. FireFox reports NR on elements visible text (false positive) #2082
3. Fix(input_label_visible) should not trigger when clipped 0,0,0,0 - different behavior in FF vs Chrome #2085
4. [BUG]: Spurious "Form control element <input> has no associated label" error #2103

What project/section is the Epic for?

• checker
• ACT Checker implementation report

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

Lessons learned and observations