-
Notifications
You must be signed in to change notification settings - Fork 23
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
Investigate adding automated accname tests in wpt/webdriver #174
Comments
ok! @accdc let's schedule some time to get on the same page about this and come up with an action plan. 👍 |
Implemented in Chromium and WebKit. Gecko tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1788867 |
Docs on running the WPT tests: https://github.com/web-platform-tests/wpt/blob/c478d0f4a1c3cd64a35b6f451679365dddbed8f5/README.md |
Taking assignment as this is likely to be part of the InterOp 2023 Accessibility Investigation. |
FWIW, the Mac configuration steps on the WPT site didn't work for me, so here's my variant of what worked. Setting up a new Mac system to run WPT tests
You should get some percentage of passes and failures. The specific passes/failures should match the results on WPT.fyi for the same test. Note: Watch out for double hyphens in CLI params. Depending on the text field you copy out of, autocorrect may convert them to en dashes (–) which can look identical in monospace. |
testdriver extension PR here: https://github.com/web-platform-tests/wpt/pull/38758/files |
Once that lands, you should be able to do:
|
It should work in Chromium, too. Gecko has the prerequisite webdriver support planned for the April/May timeframe. |
Firefox patch here: https://bugzilla.mozilla.org/show_bug.cgi?id=1585622#c21 🎉 |
Work continues in the following: Should we close this AccName #174 issue as completed? |
I think this is done now... There are currently 382 AccName tests among the other WPT Accessibility tests. Closing. |
all the accname tests should be able to be rewritten to use webdriver.
The text was updated successfully, but these errors were encountered: