Plugin creator’s site: https://wordpress.org/plugins/editoria11y-accessibility-checker/
(Note: The plugin name is officially spelled with the numbers 11 instead of the letters LL, but for the sake of search I’ll write the word “Editorially” here in the body as well.)
This plugin is currently available by request on Publish.illinois.edu while we gather user feedback about its settings and behavior. However, it’s freely available from the WordPress plugin link above, so you can also install it on cPanel or a self-hosted WordPress (or Drupal) website if you like it.
What it does and doesn’t cover:
Even with the Illinois Theme and Editoria11y enabled, you can create inaccessible content that Editoria11y will not warn you about if you choose low-contrast colors, size overrides, or other visual matters outside the scope of the tool.
Editoria11y will check for text-structural questions like the proper order of headings and the existence of alt text. However, as of December 2025, it appears not to cover visual issues like color contrast. You’ll need other tools to perform additional checks for visual matters.
How to use:
On Publish.illinois.edu, request Editoria11y to be enabled for your Publish site. (On other hosts like cPanel, you may be able to install it yourself.)
In the Plugins list, search for Editoria11y (note the numbers 11, not the letters ll) and enable it.
Like any accessibility assessor, this plugin is not an automatic guarantee of accessibility, and it says so on the plugin creator’s site. A human will still need to assess the page and make contextually appropriate decisions.
But this plugin will highlight potential issues of concern for you to address in the Block Editor, the Classic Editor, and even Classic blocks embedded within a Block Editor page.
In addition, when you are logged in as a person with editor rights, it will also highlight issues of concern in the reading view of a page or post that you have editor permission to update as well.
If you would like more detailed guidance on what the plugin does and does not automatically check and how to address the highlighted results, check Princeton’s documentation for the plugin.
