R6.3 Legacy code cleanup

[shunguoy]

The engine code has lots of legacy code with duplicated or similar functions that caused maintenance issues. We might need to change multiple places with a spec change or a fix to an issue, this is costly.

Epic Details

• Hill: Users will have an improved experience with the checker or tools because the code of engine rules will be cleaner, and run faster, and be more compliant with specs and 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: # of code functions are merged and fixed. 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.

• Update ARIA definition and calculation #1977

• Categorize the engine utility functions #1974

• Merge legacy NodeWalker to DomWalker #1971

• Resolve element role when multiple values are provided  #1973

What project/section is the Epic for?

• toolkit
• requirements
• checker
• 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

[MHoov]

Notes from Aug 9 call:

• Not possible to do it all during this release
• Tom suggests carving out a chunk, possibly Aria role definitions
• Primary goal is cleaning out the code, not necessarily performance improvements
• Tom looked at javadoc, trying to get a sense for what the problem is
• Shunguo will start his exploration after his vacation