Open rahimabdi opened 8 months ago
Generally all sounds good. I think some of the non-accessibility-specific stuff you mentioned above may already be documented in the main WPT project... Any accessibility-specific docs could go here, along with pointers to the main WPT docs where relevant.
@rahimabdi @lolaodelola and I met and discussed a few additional ideas:
We also talked about our multiple audiences
Adding Agenda+ for docs discussion in the May meeting.
@boazsender @cookiecrook I've emailed you (and Lola) a link to the draft documentation I'm proposing. Your thoughts and feedback are welcome!
I've also added a tracker to the issue description with outstanding tasks/questions.
@chrishtr you took an action to review. Thank you!
Determine publication platform (likely our GitHub Wiki page)
@chrishtr asked me, and I think most of that document would make sense in https://github.com/web-platform-tests/wpt/tree/master/docs/writing-tests, as a new accessibility.md file most likely. It would then be published to https://web-platform-tests.org/.
Parts of the document are about the Accessibility Interop Group, and that I'd suggest putting right here in this repo's README where it's easy to find or stumble upon.
Some of the FAQ questions could probably be put into the main WPT docs and some others are about the Accessibility Interop Group. Splitting that and the overall doc would be shame in a way since it's useful as a rather self-contained resource. An option could to publish it as a whole in this repo as well, but just note which parts are also available on https://web-platform-tests.org/ and which is the source of truth.
Hope that helps.
Thanks for chiming in @foolip.
Splitting that and the overall doc would be shame in a way since it's useful as a rather self-contained resource. An option could to publish it as a whole in this repo as well, but just note which parts are also available on https://web-platform-tests.org/ and which is the source of truth.
Agreed, I would also vote for keeping it self-contained in this repo but could be split up otherwise.
Tracker:
@cookiecrook Consolidating general thoughts here on improving the quality/consistency of our WPT accessibility test files and providing supporting documentation for test authors (also to make it less daunting for WPT contributors). All feedback welcome! Happy to take this forward after you and other folks have provided input.
I know that detailed guidance is already captured here and this may be moved to
web-platform-tests/interop-accessibility
: Running the WPT Tests for ARIA and Related Specs..html
test files (usually after a spec's section)<div id="id" data-expectedtestname="someTest" data-expectedlabel="label">
, spacing and indentation, etc.id
naming scheme for elements/containers (e.g., many elements with uniqueid
s referenced viaaria-labelledby
)aria-utils
utility functions)aria-utils.js
and what it does