Repository navigation
Restructuring wpt/html-aam directory #615
Description
Thank you for raising this @lolaodelola!
Creating a companion HTML-AAM issue to track the work around restructuring wpt/html-aam happening in this parallel Interop Accessibility issue: web-platform-tests/wpt#62897.
After speaking with @scottaohara at our weekly HTML-AAM editor's sync (Oct 9 2026), we discussed two possible directory structures:
- Having a single root top-level folder containing one file per HTML element. Each file would have all relevant WPTs (role, accname, attributes, etc.) for that specific HTML element
- Creating a subfolder for every HTML element; in each subfolder (e.g., button), relevant tests would be split out by feature (e.g., accname, role, attributes, etc.).
Metadata
Metadata
Assignees
Labels
No labels
Activity
css-meeting-bot commentedon Oct 15, 2026
The ARIA Working Group just discussed
Restructuring wpt/html-aam directory.The full IRC log of that discussion
<jugglinmike> subtopic: Restructuring wpt/html-aam directory<jugglinmike> github: https://github.com//issues/615
<jugglinmike> lola: The WPT directories are not always organized in a way that makes it easy to contribute (or extra results)
<jugglinmike> lola: Yes, there is metadata, but even with that, you can't add metadata to subtests
<jugglinmike> lola: I've been speaking with the interop group (James, Simon, and Valerie), and this is a proposal based on those discussions
<spectranaut_> whatever we do for html-aam, we should do for core-aam
<jugglinmike> lola: Currently, there are less than 10 files for all the behaviors for all the elements. I'm proposing one file/directory per element. That will make it easier to write tests
<spectranaut_> the current tests in core-aam are per entry in the mapping tables
<jugglinmike> lola: My preference is for the first of the two options that Rahim has listed
<jugglinmike> jamesn: This doesn't seem like it needs the entire group to discuss. Maybe it can be hashed out by those interested in WPT
<jugglinmike> Rahim: Thanks for raising this, Lola! This is just something we wanted the wider working group to have visibility into
<jugglinmike> jcraig: Part of the motivation is that we have talked about having one of the specs use Bikeshed... or if ReSpec one day offers WPT integration