Re: [w3c/charter-html] HTML AAM should remain a joint deliverable (#133)

One of the challenges of a joint deliverable is the administrative overhead it introduces for both WGs.

Either one WG needs to assume working responsibility for the deliverable (driving work forward etc.), or a TF has to be created so the responsibility is shared equally. WPWG prefers to work asynchronously, and with both ARIAWG and WPWG being incredibly busy, finding time (and chairs) for a TF would seem impractical.

The deliverable also has to go through the process motions in both WGs. This is a duplication of work across both WGs, and it often adds significantly to the time needed to progress a spec to Rec.

To this end, the WPWG chairs would like to offer to take the HTML AAM as a WPWG deliverable. We would of course expect the ARIAWG to be closely involved (and would be happy to include charter words to this effect), but it would push the admin overhead onto WPWG for the most part.

We think this addresses the point made by @richschwer (that the AAM should not be pushed off into accessibility space). We also hope it will send out a positive message across W3C.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/charter-html/issues/133#issuecomment-241272577