Tony Fast

stoked to see work on this! thanks! so `pidgy` is basically a few ipython extensions in a trench coat. it ships an `IPyKernel` & kernelspec that only invokes a magic...

> Not sure what "your" means in this case... but can certainly image for a site that only has pidgy content in it... "plain old python" still doesn't quite work...

> > is a lite repl with the pidgy kernel > > Right: this is the advantage to a "real" kernelspec, etc. as this should _already_ work, provided a new-enough...

i am assuming if accessibility were critical to the LF transition someone would have talked to us. we have the steering council reps and accessibility that can act on any...

> I'm certainly open to a more explicit pause of some or all of accessibility group routines (like the meetings) @isabela-pf it's good to hear that this also makes sense...

> To move the conversation forward, what would the accessibility subproject do if it had access to substantial sustained resources thanks for those questions @jasongrout . i'll take some time...

* mark skip link as completed by https://github.com/jupyterlab/jupyterlab/pull/14597 which leaves extra space for me skip links * tab traps will be fixed by https://github.com/jupyterlab/jupyterlab/pull/14115 * using aria authoring practice guide...

> I can't reproduce it, on my side there is no "unknow" tab, even when the header is hidden. the tab order doesn't take me to any hidden elements either....

seems like a bunch of folks are reporting this message on the discourse board too https://discourse.jupyter.org/t/jupyter-notebook-zmq-message-arrived-on-closed-channel-error/17869/5

cool to see the progress in jupyter books. i can imagine this proposal maturing jupyter book to effectively, or eventually, become another jupyter front end with thebe in the mix....