Open amyjko opened 10 months ago
This issue should probably be broken down into smaller issues. I would consider this issue done once there are many other issues open for specific WCAG automated tests that we want to write.
It's the end of Winter! Please provide an update on this issue, including:
If you do plan to continue work on it, carry on. Otherwise, thank you for your contributions!
No reply :( Unassigning @MichelleGuan1128 @murbu @meepsterleapster @rf-uw.
Sorry, I ran into major trouble with my computer during the break. More importantly, while I am unlikely to be able to provide the same amount work as last quarter, I would be happy to answer any questions related to end to end tests with playwright that come up, as I spent a significant time using that system for testing for WCAG violations
I will be under the same name in discord, between here and there that is the best place to reach me regarding Wordplay
Apologies for the late reply - echoing what George said, I am unable to contribute this quarter in the same capacity but will be availible here or on Discord (ryder @ingwion) for questions about e2e accessibility testing with playwright/axe.
Not sure why this was closed, it's not resolved.
What's the maintenance need?
We need as many unit tests, end-to-end tests, and manual tests as possible to verify the entire user interface for WCAG 2.1 compliance. There are likely numerous issues lurking that we cannot see because we're not testing them. This project would involve the creation of many new tests.
Who benefits?
All creators with disabilities for whom Wordplay is not yet accessibile.