Editoria11y Accessibility Checker

Editoria11y is meant to supplement, not replace, these tools. Editoria11y is...spellcheck: a seamless, automatic and intuitive integration for content authoring. It:

• Does not require training before use.
• Eschews obfuscation and techno-legal jargon. It explains what the issue is in plain language, with a simple explanation of how to fix it. "This image needs alternative text" with a short explanation of what alternative text is makes sense without prior technical knowledge; "Failure of WCAG 1.1.1 Level A: Non-text Content" does not.
• Deliberately excludes tests for theme and plugin issues, like invalid HTML tags and ARIA attributes. Testing is critically important for themers and developers, but it is work for themers and developers, not content editors. For ongoing quality assurance, Editoria11y provides people with a tool that fits their role, so they only receive alerts for things they can fix.

Editoria11y's test suite is quite similar to Sa11y. Editoria11y began as a Sa11y fork, and the maintainers collaborate on new tests and optimizations. The look, feel and features outside the core test suite are a bit different. At a high level:

• Sa11y provides a broader test suite:
• A legibility scoring library is included
• A contrast checking library is included
• The end-user can override appearance and test coverage settings from the results panel
• Editoria11y provides live-editing feedback and server-side tools:
• Editors receive feedback while editing.
• Findings are synchronized to a site-wide reporting dashboard
• Manual-checks marked as "OK" are dismissed for all users, not just the current user
• All configuration is managed in the plugin settings

Overlays are scripts that make untested modifications to your site's themes and content, claiming these automated changes will better meet the accessibility needs of your users. Overlays may do things like override your theme's font sizes or colors, or modify its heading tags and buttons. This differs from buttons that make potentially the exact same changes to a specific site -- the key difference is in whether the button has been tested with that specific theme, or attempts to work in any context without testing. You should familiarize yourself with the assistive technology compatibility problems untested overlays may introduce before assuming these changes will be helpful, as any untested code can break existing accessibility features or introduce new invisible errors. If you choose to install an overlay, you should test each of its features on your site using assistive tools or pay for a professional accessibility test. Editoria11y is not an overlay. It does not modify the site viewed by not-logged-in-users in any way. It is an editor-facing testing tool that helps your site editors create accessible content.

Editoria11y's default settings will work great for most sites. Your first task after installation should be clicking through a representative sampling of the main pages of your site. This will start to populate your dashboard report, and give you a chance to look for issues to fix or dismiss. If you notice anything amiss, experiment with these settings:

1. Pick a "Theme for tooltips" that looks nice with your site's colors.
2. If the checker is flagging issues that are not relevant to content editors, either use "Check content in these containers" to constrain checks to the parts of the page with editable content, or "Exclude these elements from checks" to skip over certain elements, regions or widgets.
3. Editoria11y also provides an "as-you-type" issue highlighter that works inside the Block Editor/Gutenberg. If you find live correction annoying rather than helpful, change "Check inside the block editor" to unset "always show tips," or chose "Do not check while editing."
4. If you do not want PDF or other document types flagged for manual checks, provide a shorter selector list or set "Document types that need manual review" to false
5. If your theme has done something very unusual with its layout, such as setting the height of the content container to 0px, you may see confusing alerts when opening Editoria11y tips saying that the highlighted element may be off-screen or invisible. If that happens, disable "Check if elements are visible when using panel navigation buttons." This is disabled by defaults on any WordPress themes we have noticed this on, so if you find a theme

Editoria11y's WordPress plugin is maintained by Princeton University's Web Development Services team:

• John Jameson: Editoria11y JS and CMS integrations
• Jason Partyka: Devops
• Brian Osborne: Code review
• Michael Muzzie: Wapuu photos