What is ACAI?
ACAI is Accessibility Cloud’s digital accessibility testing technology. Rather than relying on a single test engine, ACAI combines multiple components into a unified testing framework capable of driving other established test technologies, such as axe-core and QualWeb, alongside its own purpose-built tools.
ACAI utilizes multiple engines, tests with its own rules, and adds artificial intelligence driven tests on top, delivering unparalleled WCAG coverage in a single scan.
ACAI is available for free in all Accessibility Cloud plans, including the free plan. Free plan users have access to all ACAI components except AI-powered tests.
Architecture and Components
ACAI is made up of both internal components developed by Accessibility Cloud and external components from established open-source test engines.
Internal components
ACAI-AI uses artificial intelligence to detect accessibility issues that traditional rule-based engines cannot reliably identify, such as misleading alternative text, language mismatches, and other context-dependent problems.
ACAI-engine is a new rule-based test engine developed by Accessibility Cloud, drawing on years of experience monitoring websites across Europe. It extends WCAG coverage beyond what existing engines offer on their own.
ACAI-mobile will bring ACAI’s testing capabilities to mobile platforms. Launching later in 2026.
ACAI-API will allow you to run ACAI tests programmatically without using the Accessibility Cloud interface, enabling integration into your own workflows and CI/CD pipelines. Launching later in 2026.
External components
axe-core is a widely adopted open-source accessibility testing engine maintained by Deque Systems.
QualWeb is an open-source accessibility evaluation engine developed at ISCTE, University Institute of Lisbon.
ACAI is capable of driving these external engines as part of its testing process, combining their results with its own for broader and more accurate coverage.
What can ACAI test for?
In addition to the rules provided by axe-core, QualWeb, and the ACAI-engine, ACAI-AI introduces a set of AI-powered tests that target issues which are difficult or impossible for traditional rule-based engines to detect. New tests are added frequently.
AI-powered tests
Alternative text must be accurate
acai-alt-text-inaccurate – WCAG 1.1.1
Detects alternative text that does not correctly describe the content of an image. Alternative text exists to provide a textual equivalent for users who cannot see visual content, whether due to visual impairments, slow internet connections, or disabled images. When alternative text is inaccurate or invalid, it becomes misleading rather than helpful, failing to convey the intended information and undermining accessibility for a significant portion of users.
Alternative text must be descriptive
acai-alt-text-nondescriptive – WCAG 1.1.1
Alternative text should clearly describe the content it represents. Identifies alternative text that is too vague or generic to be useful, such as “logo”, “image”, “picture”, “photo”, or “flag”. These terms fail to convey meaningful information and do not help users understand the content of the image.
Alternative text must be in the correct language
acai-alt-text-lang-mismatch – WCAG 3.1.2
Flags cases where the alternative text is written in a different language than the one specified in the containing element’s lang attribute or the document’s language. When there is a mismatch, screen readers may mispronounce the alternative text, making it difficult or impossible for users to understand.
<html lang="sv">
<img src="office.jpg" alt="Our head office in downtown Stockholm" />
Alternative text must not contain symbols that cause screen reader noise
acai-alt-text-symbols-noise – WCAG 1.1.1
Identifies symbols or special characters in alternative text that produce unwanted or confusing output when read aloud by screen readers. This includes repeating punctuation marks such as “—” or “***” and decorative separators like |, /, and –. Such characters create unnecessary audio clutter for screen reader users, distracting them from the main content. These symbols should not appear in alternative text unless they are part of the actual visible text in the image.
Data visualizations must be described in alternative text
acai-alt-text-chart-undescribed – WCAG 1.1.1
Detects charts, graphs, and other data visualizations that lack meaningful alternative text. Without a text description, users who cannot see the visual content have no way to access the data being presented.
Alternative text must not contain typos or grammatical errors
acai-alt-text-typo – WCAG 1.1.1
Detects spelling and grammar mistakes in alternative text. Such errors can confuse screen reader users, reduce clarity, and make images harder to understand. Correct, clear alternative text ensures accurate interpretation for people relying on assistive technologies.
Alternative text must not repeat brand name or marketing slogans
acai-alt-text-brand-spam – WCAG 1.1.1
Identifies alternative text that has been used to insert brand names, marketing slogans, or other promotional content rather than providing a genuine description of the image. This gives users no meaningful visual information, making the alternative text useless for screen readers and reducing understanding for people who rely on them.
Algorithmic tests (rule based)
Text alternative must be meaningful, not derived from the filename
acai-alt-text-filename – WCAG 1.1.1
Identifies alternative text that appears to be a filename rather than a genuine description of the image. Using a filename as alternative text is a common malpractice in web development, often done to suppress accessibility warnings under the assumption that the filename is a good enough description. It never is. Filenames such as “IMG_2045.jpg” or “header-banner-v2.png” provide no useful information, and because they contain characters such as dashes and underscores as well as file extensions, they cause additional problems for screen reader users who must listen to them being read aloud.
Text that differs from the document language must be declared using the “lang” attribute
acai-document-lang-mismatch – WCAG 3.1.2
Detects when text on a page is written in a different language than the one declared for the document, without the language change being explicitly indicated using the lang attribute. ACAI detects the language of each text block in the document body and compares it to the document’s declared language. Text blocks that differ from the declared language and are not wrapped in an element with the correct lang attribute are flagged as issues.
<p>Wir sind ein führendes...</p>
<p>We are committed to...</p>
<p>Wir sind ein führendes...</p>
<p lang="en">We are committed to...</p>
Value of the “lang” attribute must match the content language
acai-element-lang-mismatch – WCAG 3.1.2
Detects when the declared language of a specific element does not match the actual language of the text within it. When an element uses the lang attribute, the specified language must accurately reflect the content. ACAI detects the language of each text block in the document body and compares it to the declared language of its containing element, flagging mismatches that could cause screen readers to mispronounce the content.
<p>Reach out to our local offices...</p>
<p lang="fr">Nuestra oficina en Madrid...</p>
<p>Reach out to our local offices...</p>
<p lang="es">Nuestra oficina en Madrid...</p>
Alternative text must not contain redundant phrasing
acai-alt-text-redundant – WCAG 1.1.1
Detects alternative text that includes phrases such as “image of” or “picture showing”. These phrases are redundant because screen readers already announce images. Including them adds noise, slows navigation, and makes content less efficient for users relying on assistive technology.