Re: "Accessibility Notification" process, suggested next steps

Voicing my support for all of Val’s administrative decisions listed below.

> On Jun 29, 2023, at 12:52 PM, Valerie Young <spectranaut@igalia.com> wrote:
> 
> Hi everyone,
> 
> In today's meeting, we spent some time talking about the accessibility notification API process. It was good to get everyone's thoughts, but let's lock down the process in this email thread so we can focus on the technical details of the proposal during working group time.
> 
> Short term suggestion: Keep the google doc for now. I added a "Process" section at the top and request that no one make comments in this document, and to instead use the ARIA discussion board. We did this because comments and edits in a google doc are not particularly accessible.
> 
> Notes about this proposal:
> 
> I change the document's access settings from "everyone is an editor" to "everyone can view". This can be undone by any of the current explicit editors, which includes me, Scott, Doug, Aaron, Cynthia, James Teh and Clinton.
> There was a suggestion to move this to the wiki -- to me this seems like unnecessary intermediary step, as we will just have to move it again to it's "final location". Let me know if there is disagreement with this.
> Longer term proposal: Move the work to a Web Platform Incubator Community Group (WICG -- pronounced "Y-C-G"): https://www.w3.org/community/groups/
> 
> Notes about this proposal:
> 
> In this scenario, we can create a new repo under the W3C organization and develop the specification there
> I'm not totally sure the steps involved to set up a new repo, if someone knows and could fill in the details please do -- but to start we can make a new community group here (name preferred: "Accessible Notifications"): https://www.w3.org/community/groups/propose_cg/
> I'd be happy to help with setting this up at a later date, I'd like to hear people weigh in on the priority of this.
> Please provide feedback if you have any!
> 
> Valerie
>