-
Notifications
You must be signed in to change notification settings - Fork 5
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
Document how to write accessibility tests #24
Comments
Could include some JSDoc-style generated documentation of any interfaces in aria-utils.js and other relevant files? |
That makes sense to me. I also think we should write a general guide. |
@boazsender I need to start on this a bit ahead of the ARIA F2F coming up on May 3rd. I know you mentioned someone from Bocoup may be interested in helping out. Is that still the case? |
I think yes, but probably not before the F2F, unfortunately. Sorry about that! |
No worries. I'll try to start something on the ARIA Wiki. |
Starting with updates to the ARIA Testing docs |
Basic starting docs at: @boazsender This isn't really a "how to" so if you want to take it further, please do. Otherwise, okay to close. |
I'm going to close this for now and open a new issue about adding howto information to this/integrating it http://web-platform-tests.org. |
I just skimmed the wpt doc, and I think it actually is a "how to". Great work! |
FYI, I'll be delivering an overview of WPT Accessibility testing at the ARIA F2F tomorrow May 3rd, at 10:30 AM Pacific. I'm not sure if @jnurthen or @spectranaut have a Teams link yet, but all interested parties are welcome. |
Updated: 10:30 AM Pacific, not 10 AM. |
Create a how to guide for the approach that has been established for writing accessibility tests.
The text was updated successfully, but these errors were encountered: