-
Notifications
You must be signed in to change notification settings - Fork 249
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
3.3.9 Redundant Entry out of order #2764
Comments
Nice catch! Which is the file to edit to make this correction? |
guidelines/index.html Not sure if the Understanding/toc.html also needs to be updated. |
Changes here would impact the following PR and the other supporting documents, like understanding. Considering that users are now used to SCs being out of order, I wonder how important this change is. |
@yatil it does help a bit in quickly determining whether an individual SC is from 2.0/2.1/2.2 |
OK. (FWIW: I have stopped contributing to WCAG 2 due to exhaustion and mental health concern and had unsubscribed from all issues. I would prefer to be not tagged in the future.) |
3.3.7 is Level AA, 3.3.8 is Level AAA, and 3.3.9 (redundant entry) is Level A. We have been ordering new SC so that Level A are first, then AA, then AAA. This seems to be the only instance where this isn't followed.
The fix would be to make 3.3.9 Redundant Entry into 3.3.7 Redundant Entry and adjust the other two SC.
The text was updated successfully, but these errors were encountered: