Check on save

New problems usually arrive with new content. Check on save catches them at once: when an editor saves an article, a Custom module or a category, it is checked, and the editor sees what is wrong.

What happens on save

• The article, module or category is saved as usual. Check on save never changes or stops what was saved.
• If it has problems, a message above Article saved. says how many of each kind, such as Accessibility: this article has 1 image without useful alt text, 1 unclear link.
• Fix them now opens the Fix Queue with only that article’s problems. See The Fix Queue.
• The Fix Queue and the dashboard are updated for that item straight away, without a full scan. Problems the editor fixed by hand leave the queue.

If there are no problems, no message is shown.

An unpublished article is checked too, so the editor can fix it before publishing, but its problems join the queue only once it is published.

Editors who edit articles on the site’s front end see the message without the Fix them now link, because the Fix Queue is in the administrator. So do administrator users who are not allowed to use JS Accessibility Fixer.

Turning it on or off

Check on save is the plugin Content - JS Accessibility Fixer. It is turned on when you install. The dashboard shows On or Off in the Keeps working on its own card; click it to open the plugin.

To turn it off, go to System → Manage → Plugins, find Content - JS Accessibility Fixer and disable it. This also removes the Suggest alt text with AI button from the article editor.

No AI on save

Check on save only finds problems; it doesn’t ask the AI and costs nothing. In Pro, the nightly Suggest fixes on its own task gives these new problems suggestions, so they are ready in the queue the next morning.