-
Notifications
You must be signed in to change notification settings - Fork 842
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
[Meta][Docs] Add automated tests for all pages #2679
Comments
@myasonik what needs to be done for this? |
@anishagg17, PR #2995 by @ashikmeerankutty is a good example of what needs to be done. (You can find some more examples of the type of work that might need to be done in #2569 though it's a little bit muddled with some setup work that was done as well.) As this is a big ticket if you're going to work on it please comment on which pages you are working to add. Also, please feel free to add pages non-linearly as it's all controlled by an array of which pages to check. Feel free to push any range of pages onto that array to be tested. You can find docs on the accessibility testing setup on the wiki. |
okay @myasonik |
@myasonik |
Please recheck for Layout -> header |
Good catch! Removed! |
is anyone working on this issue i would like to. @anishagg17 @myasonik |
Hi @hetanthakkar1! This issue is quite large we (mostly @anishagg17) have been merging small PRs as they are ready to be able to make steady progress over time instead of no progress for a long time and then trying to roll out a big bang change. You can see in the description which pages are already done and you can see open PRs (such as #3077) linked in this thread as well. We're happy to look at any PRs for pages that aren't currently in progress! If you're worried about conflicting with work other devs might have locally on their machines but not yet pushed to a PR, feel free to shout out here what pages you are taking on so that others know not to tackle them. |
Closing this in favor of #6302 |
After #2569, the guideline pages could manually be added to run through axe to check for accessibility issues. After #3502, all guidelines pages were tested by default unless they were disabled.
Implementation note: To see the currently skipped pages, go to
scripts/a11y-testing.js
.Pages left to enable:
PRs so far:
The text was updated successfully, but these errors were encountered: