disbanding the accessibility meetings until after a new governance structure is adopted

during our last minute we discussed what we could do to maintain the accessibility group. this was a beautiful discussion because everyone was interested in keeping the meetings going voluntarily; everyone wants accessibility to improve that much. unfortunately, i don't think its possible for us to improve jupyter accessibility on purely voluntary efforts. accessibility needs resources that we have at the moment so this issue proposes that we disband the accessibility meetings until new governance is formed.

the jupyter accessibility has been hosting bi-weekly [meetings] for nearly four years, since @isabela-pf started them in 2020. in that time, we have succeeded in raising community awareness and advocacy, but we've failed to produce an accessible version of intertactive computing for assistive technology users. we've had strong impacts on the developer community, but we haven't improved conditions for assistive technology users. we've had funding and made minor progress. we've failed to address professional jupyter [audits]. there are reasons for this and we should assess. unfortunately, there is zero [funding] for accessibility and that means we have little ability to improve conditions. i think we should save our energy and spirits.

jupyter has been working hard in recent years to mature its identity, it seems like the recent [linux foundation](https://github.com/jupyter/governance/issues/204) inquiry might provide the growth needed for a project of this size. i suggest that we disband our accessibility meetings and work asynchronously until jupyter establishes its new identity. when that time comes we can advocate for more accessibility resources, but until these changes happen i think we will be expending borrowed resources that might be better saved up until we understand the future of jupyter better.

if this effort does disbands and regroups in new governance structure then accessibility, if governance is serious about accessibility, should play a more central role in DEIA, physical/digital community events and all of the user interfaces under the jupyter umbrella.

cc: @ohrely @gabalafou

[funding]: https://jupyter-accessibility.readthedocs.io/en/latest/funding/index.html
[audits]: https://jupyter-accessibility.readthedocs.io/en/latest/audits/index.html
[meetings]: https://jupyter-accessibility.readthedocs.io/en/latest/community/meeting-minutes/jupyterlab-accessibility-meetings/2020/index.html

Start by reading the linked meeting minutes, funding and audit pages, and the Linux Foundation governance inquiry in issue 204. Assess whether the accessibility meetings should pause in favor of asynchronous work and what a future governance structure must provide. Done means the community has decided and documented the meeting status and transition plan.

Written by the indexing model from the issue text.