I'm hoping that someone can do an accessibility review, identify any things that need to be updated, and add a section to the documentation about any features that need to be avoided or patterns that need to be followed in order to ensure that Pluto outputs meet Web Content Accessibility Guidelines (WCAG) 2.2 at level AA or better.

My understanding is that all large US universities will be required to have all their curricular materials meet this standard by April 24, 2026. So, in addition to the general desire to make outputs accessible, there is urgency to checking Pluto outputs against all the guidelines, so faculty are allowed to continue using Pluto in university settings.