Acquia AI checks a page for accessibility, readability, and spelling, returns a score with plain-language findings, and fixes reviewed accessibility errors. The agent takes no action without user approval, and low scores do not block publication.
Check coverage
Acquia AI evaluates pages against the following criteria:
Governance checks do not cover SEO or data protection.
Audit scope
Acquia AI audits publicly accessible pages regardless of site origin. The agent analyzes pages through Acquia Web Governance to reach public internet addresses.
Fix application maintains a narrower scope than audit checks. For additional details, visit the Fix scope section.
Prerequisites
Ensure that the setup meets the following requirements:
The account holds Acquia AI access and Work mode permissions.
The target page is accessible on the public internet.
To apply fixes, the page must reside on an Acquia Source CMS site connected to Acquia AI, and an administrator must assign that site to the project agent.
Run a check
To run a governance check:
Open Acquia AI and set the mode toggle to Work mode.
Name the check and specify the page address. For example: Run an accessibility check on https://example.com/autumn-campaign.
Specify alternative standards if non-default evaluation is required. For example: Check that page against WCAG 2.2 AA.
Review the results.
Interpret check results
Each check returns the following details:
A score out of 100, with a passing threshold of 80.
Categorized plain-language findings that group issue types instead of raw rule lists.
Scores below 80 do not prevent publication. Acquia AI does not restrict publication based on check scores.
Apply a fix
To apply a fix based on check findings:
Request that the agent resolve identified issues. For example: Fix the accessibility errors you found on that page.
Review the plan stated by the agent, then approve the plan or request changes. The agent takes no action until plan approval.
The agent applies modifications as a draft. Publication requires a separate approval.
The agent conducts a follow-up check to confirm resolution.
Fix recommendations apply exclusively to custom components on connected Acquia Source sites. When pages fall outside this scope, Acquia AI reports the restriction without modification attempts:
Custom components on connected Acquia Source sites: The agent fixes identified errors.
Elements outside custom components on connected Acquia Source sites: The agent reports findings without applying fixes.
Other public pages: The agent checks the page and reports findings only.
Acquia AI resolves a reviewed set of common accessibility errors rather than every detectable error class.
AI credit usage
Checks and fixes run in Work mode and consume AI credits from the general account allocation. Separate allowances for checks do not exist. For additional details, visit AI credits and usage.
Run a governance check and apply a fix
Acquia AI checks a page for accessibility, readability, and spelling, returns a score with plain-language findings, and fixes reviewed accessibility errors. The agent takes no action without user approval, and low scores do not block publication.
Check coverage
Acquia AI evaluates pages against the following criteria:
Governance checks do not cover SEO or data protection.
Audit scope
Acquia AI audits publicly accessible pages regardless of site origin. The agent analyzes pages through Acquia Web Governance to reach public internet addresses.
Fix application maintains a narrower scope than audit checks. For additional details, visit the Fix scope section.
Prerequisites
Ensure that the setup meets the following requirements:
The account holds Acquia AI access and Work mode permissions.
The target page is accessible on the public internet.
To apply fixes, the page must reside on an Acquia Source CMS site connected to Acquia AI, and an administrator must assign that site to the project agent.
Run a check
To run a governance check:
Open Acquia AI and set the mode toggle to Work mode.
Name the check and specify the page address. For example: Run an accessibility check on https://example.com/autumn-campaign.
Specify alternative standards if non-default evaluation is required. For example: Check that page against WCAG 2.2 AA.
Review the results.
Interpret check results
Each check returns the following details:
A score out of 100, with a passing threshold of 80.
Categorized plain-language findings that group issue types instead of raw rule lists.
Scores below 80 do not prevent publication. Acquia AI does not restrict publication based on check scores.
Apply a fix
To apply a fix based on check findings:
Request that the agent resolve identified issues. For example: Fix the accessibility errors you found on that page.
Review the plan stated by the agent, then approve the plan or request changes. The agent takes no action until plan approval.
The agent applies modifications as a draft. Publication requires a separate approval.
The agent conducts a follow-up check to confirm resolution.
Fix recommendations apply exclusively to custom components on connected Acquia Source sites. When pages fall outside this scope, Acquia AI reports the restriction without modification attempts:
Custom components on connected Acquia Source sites: The agent fixes identified errors.
Elements outside custom components on connected Acquia Source sites: The agent reports findings without applying fixes.
Other public pages: The agent checks the page and reports findings only.
Acquia AI resolves a reviewed set of common accessibility errors rather than every detectable error class.
AI credit usage
Checks and fixes run in Work mode and consume AI credits from the general account allocation. Separate allowances for checks do not exist. For additional details, visit AI credits and usage.
Source