accessibility/canvas-fallback-content.html has been failing on Windows since it was added in r78789. See the URL for an example of the failure.
<rdar://problem/9016973>
we need to add a skip for this test for windows for now
Created attachment 82804 [details] Patch
Checked in expected failure results in r78829.
Comment on attachment 82804 [details] Patch I already checked in expected failure results for this test. Sorry for not mentioning I was going to do that!
Thanks for taking care of the test expectations, and I'm sorry I didn't do that as part of the original test! It looks like most of the accessibility tests (>75%) are already disabled on Windows, so it's not clear to me if I should try to fix this one. Options include: 1. If accessibilityController.focusedElement.allAttributes() is supported on Windows, modify the test to look for the appropriate Windows-specific attributes. 2. If not, modify the test to just check for the activeElement.id on Windows and ignore the role. 3. Or, do nothing for now until Windows a11y infrastructure improves.
Chris, do you know why so many accessibility tests are skipped on Windows? Are we missing some support in DRT? Are the tests inherently Mac-specific?
A quick grep shows that 43 of the tests (including this one) test for the Mac-specific accessibility attributes of an object in the render tree. (Anything starting with AX like AXRole or AXImage is Mac-only.) It might be possible to redo some of the test infrastructure to expose WebCore roles rather than platform-specific roles. We'd still want some platform-specific tests, but those could be moved to the appropriate platform subdirectories.
(In reply to comment #8) > A quick grep shows that 43 of the tests (including this one) test for the Mac-specific accessibility attributes of an object in the render tree. (Anything starting with AX like AXRole or AXImage is Mac-only.) > > It might be possible to redo some of the test infrastructure to expose WebCore roles rather than platform-specific roles. That might be a good idea. > We'd still want some platform-specific tests, but those could be moved to the appropriate platform subdirectories. Agreed. We should probably start by moving any existing platform-specific tests into platform subdirectories. We can (and should) do that right away without having to figure out a long-term strategy.
(In reply to comment #7) > Chris, do you know why so many accessibility tests are skipped on Windows? Are we missing some support in DRT? Are the tests inherently Mac-specific? Most of the top level AX tests are pretty mac specific, but have never been moved out. There are some platform agnostic tests but not that many. As a stop gap, I think people have just disabled tests on windows, since there are so few windows-accessibility devs
This doesn't apply anymore, the original patch that added it was reverted a long time ago.