-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Reported in Slack - Potential mis-assignment of error to 2.4.3 Focus Order rather than 2.1.1 Keyboard #1834
Comments
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.
|
Current Help: About this requirement |
Triage: this mapping is related to KCM for sequential navigation of the browser extension. Make sure both the code and help are changed accordingly. |
|
prioritize lowest in release |
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. |
Rescheduling this to next sprint to continue working on AccessU outline |
branch: dev-1834 |
PR: #1899 |
PR: #1899 |
Changes made to mapping and help "Why is this important" and "About this requirement" references |
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:
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:
The text was updated successfully, but these errors were encountered: