jupyter / accessibility

A repository for ongoing work around making Jupyter's software accessible and inclusive
https://jupyter-accessibility.readthedocs.io/en/latest/
BSD 3-Clause "New" or "Revised" License
64 stars 33 forks source link

what would the accessibility subproject do if it had access to sustained resources #147

Open tonyfast opened 4 months ago

tonyfast commented 4 months ago

To move the conversation forward, what would the accessibility subproject do if it had access to substantial sustained resources, say in the tens of thousands of dollars a year (think maybe $20,000 - $50,000 per year)? What would be the most valuable things to do in the next 2 years?

If we move to LF, we're poised to have much more resources as a project. It would do well for us to collectively think ahead about how we might use such resources for the most valuable next steps in various areas of the project, especially valuable cross-project efforts that have had very little resources up to this point like accessibility and security.

Originally posted by @jasongrout in https://github.com/jupyter/accessibility/issues/146#issuecomment-2120627317