[BUG]: Reported in Slack - Potential mis-assignment of error to 2.4.3 Focus Order rather than 2.1.1 Keyboard

[maryjom]

Project

Checker engine - rule mappings

Browser

All

Operating system

All

Description

~~Don't know the project, browser, or OS as this is an issue based on Slack question regarding a particular rule's error message and help.~~

Rules affected:

widget_tabbable_exists widget_tabbable_single

It appears that the rule may be citing an incorrect WCAG success criterion for the particular message it provides (a mismatch). The following is my Slack message which contains a link to the original user's question:

In looking at this question posed in #accessibility-at-ibm, I'm wondering why this error is being reported against 2.4.3 Focus Order rather than 2.1.1 Keyboard. Seems if a tablist doesn't have an element in the tab order at all, it should have one and it would fail 2.1.1 Keyboard. Then you'd have to manually check that the tab/focus order is correct within the tablist for 2.4.3.

Steps to reproduce

Contact the originator of the question in the Slack #accessibility-at-ibm channel to see if they can provide code for you to reproduce the error.

or simply:

1. Run the test cases for the rules and check the mapping
2. Review the mapping in the Checker rule set for the rules mapped to 2.1.1 and 2..4.3. The mapping is also available in the Actions -> Artifacts: Rule listing (generate are runtime)

[philljenkins]

Current mapping:

2.4.3 Focus Order (A)

If content can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

• widget_tabbable_exists: Component must have at least one tabbable element Needs review Component with "{0}" role does not have a tabbable element
• widget_tabbable_single: Certain components must have no more than one tabbable element Needs review Component with "{0}" role has more than one tabbable element

[philljenkins]

Current Help:

About this requirement

• IBM 2.1.1 Keyboard
• ARIA practices - Developing a Keyboard Interface
• ARIA specification - Widget Roles

[shunguoy]

Triage: this mapping is related to KCM for sequential navigation of the browser extension.
widget_tabbable_single: map to 2.4.3 and 2.1.1 widget_tabbable_exists: map to just 2.1.1

Make sure both the code and help are changed accordingly.

[philljenkins]

1. Add the following "toolkit testing" reference to the widget_tabbable_single help: Check tab or navigation order Maintaining user's point of regard

~~2. Update the style & text of the group message of aria_keyboard_handler_exists: Interactive ~~WAI_~~ ARIA ~~UI~~ components must provide keyboard access~~

~~3. Update help for aria_keyboard_handler_exists by replacing onkeydown and onkeypress with arrow keys~~

[philljenkins]

prioritize lowest in release

[marcjohlic]

This is a P3 issue that we discussed adding to the current R6.1 Release. Tackle this one AFTER scheduled Release items are completed. We don't want this to impede any of the Release items.

[philljenkins]

Rescheduling this to next sprint to continue working on AccessU outline

[shunguoy]

branch: dev-1834 https://github.com/IBMa/equal-access/tree/dev-1834

[shunguoy]

PR: https://github.com/IBMa/equal-access/pull/1899

[shunguoy]

PR: https://github.com/IBMa/equal-access/pull/1899

[philljenkins]

Changes made to mapping and help "Why is this important" and "About this requirement" references