CMS Remediation Agent Overview
Summary
The CMS Remediation Agent lets you fix accessibility issues found in Siteimprove Page Report directly in your WordPress or Drupal CMS, from within Siteimprove.
Start by generating a suggested fix with AI Remediate. When you select Analyze in CMS, the agent finds where the affected content is stored in your CMS and shows you the proposed change. Nothing is written to your CMS until you approve the change in Siteimprove. When you approve it, Siteimprove writes the change to your CMS for you.
In WordPress, approving a change to published content publishes it, and the change goes live immediately. In Drupal, the change is saved as a new revision, and whether it is published depends on your content moderation workflow. Every change is recorded in your CMS revision history.
Availability and permissions
- Available with Accessibility Pro or Accessibility Advanced.
- You need access to AI Remediate and available AI Remediate credits to generate the suggested fix.
- The connected CMS account must have permission to edit the relevant content.
Siteimprove access and CMS access are separate. Siteimprove permissions control access to the remediation workflow. The connected CMS account determines which content the agent can access and change.
CMS requirements
These requirements apply to both WordPress and Drupal:
- The CMS must be reachable over HTTPS.
- A dedicated service account for the Siteimprove connection, with permission to edit the supported content in scope.
Use an account with only the permissions needed for this connection. Don’t use an employee’s personal account or an Administrator account. Ask your CMS administrator to confirm the required permissions.
Connect a CMS
- Go to Settings > AI management.
- In Site access and CMS connections, find the Siteimprove site you want to connect and select Add CMS connection.
- Choose WordPress or Drupal and enter the connection details.
- WordPress: Enter the site root as the WordPress base URL (for example, https://example.com). The REST API must be reachable at /wp-json/wp/v2/. Enter the username of a dedicated WordPress account and an Application Password generated in WordPress under Users > Profile > Application Passwords.
- Drupal: Enter the site root as the Drupal base URL (for example, https://example.com). The JSON:API module must be enabled at /jsonapi. Enter the username and password of a dedicated Drupal account with permission to edit the relevant content types.
- Save the connection.
Configure one connection per Siteimprove site. If a website uses more than one CMS, configure the relevant Siteimprove sites and connections separately.
CMS credentials are encrypted and stored by Siteimprove. They are not displayed after saving. To replace a credential, select Edit connection for the site. To remove the connection, select Delete connection. To revoke access, revoke the credential or block the connected account in the CMS.
WordPress
- Self-hosted WordPress 5.6 or later.
- The WordPress REST API available over HTTPS, normally at /wp-json/wp/v2/.
- A WordPress username and Application Password for an account with permission to edit the supported content in scope.
Create an Application Password specifically for the Siteimprove connection. Don’t use the account’s main password or reuse the Application Password for another integration. The Application Password uses the capabilities assigned to its WordPress account; it doesn’t provide a separate, narrower permission scope.
The agent supports the Block editor (Gutenberg) and Classic editor for supported content. Page builders that store content in proprietary formats are not supported for in-place fixes. WordPress.com-hosted sites that require OAuth authentication are not supported by this connector.
Drupal
- Drupal 10 or later.
- The JSON:API core module enabled, normally at /jsonapi/, and configured to permit updates.
- HTTP Basic Authentication enabled.
Ask your Drupal administrator to configure JSON:API write access and the content and workflow permissions the service account needs.
Supported fixes
The CMS Remediation Agent supports the same accessibility issues as AI Remediate. Whenever AI Remediate generates a suggested fix for an issue, you can use Analyze in CMS. For the list of supported issues, see How to use AI Remediate to fix accessibility issues.
Fixes can be applied only to page-specific content stored in your CMS. Whether a fix can be applied on a given page also depends on your CMS configuration and the connected account’s permissions.
For example, unclear link text in a paragraph you wrote on a page can be fixed. A “Read more” link that your theme adds to every post on a blog listing page cannot, because it comes from theme code rather than page content. The same type of issue can therefore have different remediation options on different pages.
When a fix cannot be applied
For issues in theme or template code, scripts, unsupported page builders, or content the agent cannot confidently locate, the agent does not suggest a change. Instead, it explains why and provides remediation guidance, such as a suggested issue location, that you can share with your developers.
How to use the agent
- Open the affected page in Page Report and identify the accessibility issue you want to fix.
- Use AI Remediate to generate a suggested fix for the issue.
- Select Analyze in CMS when it becomes available. The agent searches the connected CMS for the affected content.
- Review the current content, proposed replacement, and CMS destination.
- If the proposal is correct, select the action to apply it and confirm when prompted. Cancel if the proposal is incorrect.
- Verify the resulting content and publication status in your CMS. The change appears in the CMS revision history under the connected account. For published WordPress content, the approved update is live immediately. For Drupal, complete any review or publishing steps required by your moderation workflow.
- After the public page reflects the change, re-check it in Siteimprove to confirm whether the accessibility issue has been resolved.
Applying a CMS change and re-checking the page are separate steps. A successful CMS update does not confirm that Siteimprove has scanned the new content.
Credits and usage
Each Analyze in CMS uses one credit from the AI credit pool shared with AI Remediate. The credit is used when the analysis runs, including when the agent finds that a fix cannot be applied. Approving and applying the fix does not use an additional credit. Check your Siteimprove account for your current allowance and usage.
Security and change history
Protect the connected account’s credentials and revoke access when it is no longer needed. In WordPress, delete the connection’s Application Password. In Drupal, block the dedicated account or change its password as appropriate.
Review changes using the CMS’s native revision or content history where available. Siteimprove does not replace the CMS’s editorial, change-history, or rollback controls.
Related information
How to use AI Remediate to fix accessibility issues
WordPress Application Passwords
Did you find it helpful? Yes No
Send feedback