You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that other related specs have been moved into the repo here, so assuming that moving https://github.com/w3c/html-aria into here still allows for the github.io version of the editor's draft etc to be generated, I think it makes sense. Scott?
In case this helps decide, we've been using HTML-ARIA as a proof of how ARIA can handle the Process requirements for "evergreen" specs.
There's two parts of this still left:
Update ARIA WG Process to handle wide review for new or modified features (amendments) of evergreen specs, and
Update our tooling to avoid having to go through the painful process of annotating the amendments inline in the spec, and using some other tooling that allows for more granular (and more easily maintaineable) changelogs that are further process to satisfy the requirements around amendment annotation
I would advice waiting until these two are agreed upon and sufficiently tested to start moving this spec into the monorepo, mainly to avoid this extra noise in the monorepo.
when we discussed this in the past as a group (though, maybe it was just on the editors' call), we also determined that it wasn't really necessary for it to be part of the mono repo, since it's authoring and a11y tooling requirements/guidance, and doesn't have high dependencies on the other specs.
Activity
patrickhlauke commentedon Sep 26, 2026
I see that other related specs have been moved into the repo here, so assuming that moving https://github.com/w3c/html-aria into here still allows for the github.io version of the editor's draft etc to be generated, I think it makes sense. Scott?
pkra commentedon Sep 28, 2026
@spectranaut
Because html-aria was not with the ARIA WG at the time.
@patrickhlauke
Yes. Though after a recent change, those redirect to the main repo's gh-pages now, see e.g. w3c/html-aam#609.
daniel-montalvo commentedon Sep 29, 2026
Hi.
In case this helps decide, we've been using HTML-ARIA as a proof of how ARIA can handle the Process requirements for "evergreen" specs.
There's two parts of this still left:
I would advice waiting until these two are agreed upon and sufficiently tested to start moving this spec into the monorepo, mainly to avoid this extra noise in the monorepo.
[-]More html-aria into monorepo?[/-][+]Move html-aria into monorepo?[/+]scottaohara commentedon Oct 2, 2026
when we discussed this in the past as a group (though, maybe it was just on the editors' call), we also determined that it wasn't really necessary for it to be part of the mono repo, since it's authoring and a11y tooling requirements/guidance, and doesn't have high dependencies on the other specs.