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.

ARCHITECTURE ACAI Components INTERNAL COMPONENTS ACAI-AI AI-powered accessibility tests ACAI-engine Rule-based test engine ACAI-mobile Coming 2026 Mobile app testing ACAI-API Coming 2026 Programmatic access and integrations ACAI EXTERNAL COMPONENTS axe-core Open-source engine by Deque Systems QualWeb Open-source engine by ISCTE, Lisbon External engines are driven by ACAI as part of the unified testing process

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.

example.com/about
🐱
!
<img src="cat.jpg" alt="A golden retriever playing in the park" />
Correct alternative text
<img src="cat.jpg" alt="An orange tabby cat sitting on a windowsill" />
Inaccurate alternative text
The image shows a cat, but the alternative text describes a golden retriever. The alternative text must accurately describe the visual content of the image.

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.

example.com/gallery
🏔️
!
<img src="mountain.jpg" alt="image" />
Correct alternative text
<img src="mountain.jpg" alt="Snow-capped mountain range at sunset" />
Non-descriptive alternative text
The alternative text "image" is too generic and does not describe the content. Screen readers already announce that an element is an image, so the alternative text should describe what the image actually shows.

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.

example.se/om-oss
🏢
!

<html lang="sv">
<img src="office.jpg" alt="Our head office in downtown Stockholm" />
Correct alternative text
<img src="office.jpg" alt="Vårt huvudkontor i centrala Stockholm" />
Alternative text language mismatch
The document language is set to Swedish (sv), but the alternative text is written in English. This mismatch can cause screen readers to mispronounce the text, making it difficult for users to understand.

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.

example.com/services
🌟
!
<img src="banner.jpg" alt="*** Our Services | Best in Class ***" />
Correct alternative text
<img src="banner.jpg" alt="Our services" />
Symbols causing screen reader noise
The alternative text contains repeating asterisks (***) and a pipe character (|) that create unnecessary audio clutter when read aloud by screen readers. Remove decorative symbols and separators from alternative text.

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.

example.com/report/2025
📊
!
<img src="chart.png" alt="chart" />
Correct alternative text
<img src="chart.png" alt="Bar chart showing quarterly revenue: Q2 $2.1M, Q3 $1.8M, Q4 $2.4M" />
Data visualization not described in alternative text
The image contains a chart or graph, but the alternative text does not describe the data being presented. Users who cannot see the visualization have no way to access the information. Alternative text for data visualizations should summarize the type of chart and the key data points.

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.

example.com/team
👩‍💼
!
<img src="ceo.jpg" alt="Potrait of the cheif exective officer" />
Correct alternative text
<img src="ceo.jpg" alt="Portrait of the chief executive officer" />
Typos in alternative text
The alternative text contains spelling errors: "Potrait" should be "Portrait" and "cheif exective" should be "chief executive". Typos can confuse screen reader users and reduce clarity.

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.

example.com/shop
!
<img src="latte.jpg" alt="BeanBrew Co. - Taste the Difference" />
Correct alternative text
<img src="latte.jpg" alt="A freshly prepared oat milk latte" />
Brand name or slogan used as alternative text
The alternative text contains a brand name and marketing slogan instead of describing the image. This gives screen reader users no meaningful visual information. Alternative text should describe what the image actually shows.

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.

example.com/news/2025
🎉
!
<img src="IMG_4827.jpg" alt="IMG_4827.jpg" />
Correct alternative text
<img src="IMG_4827.jpg" alt="Employees celebrating the company's 10th anniversary" />
Alternative text derived from filename
The alternative text "IMG_4827.jpg" is a filename, not a description. Filenames contain characters such as underscores and file extensions that screen readers will read aloud, creating a confusing experience. Replace the filename with a meaningful description of the image.

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.

example.de/uber-uns
lang="de"
Über uns
Wir sind ein führendes Unternehmen im Bereich der digitalen Barrierefreiheit.
We are committed to making the web accessible for everyone around the world.
<html lang="de">
<p>Wir sind ein führendes...</p>
<p>We are committed to...</p>
Correct markup
<html lang="de">
<p>Wir sind ein führendes...</p>
<p lang="en">We are committed to...</p>
Document language mismatch
The document language is set to German (de), but the second paragraph is written in English without a lang attribute. Screen readers will attempt to read the English text using German pronunciation rules. Add lang="en" to the element containing the English text.

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.

example.com/contact
lang="en"
Contact us
Reach out to our local offices around the world.
lang="fr"
Nuestra oficina en Madrid está abierta de lunes a viernes.
<html lang="en">
<p>Reach out to our local offices...</p>
<p lang="fr">Nuestra oficina en Madrid...</p>
Correct markup
<html lang="en">
<p>Reach out to our local offices...</p>
<p lang="es">Nuestra oficina en Madrid...</p>
Element language mismatch
The element declares lang="fr" (French), but the text content is written in Spanish. The lang attribute must match the actual language of the text. Change it to lang="es" so screen readers use the correct pronunciation.

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.

example.com/products
👟
!
<img src="shoe.jpg" alt="Image of a grey running shoe" />
Correct alternative text
<img src="shoe.jpg" alt="Grey running shoe" />
Redundant phrasing in alternative text
The alternative text begins with "Image of", which is redundant because screen readers already announce that the element is an image. Remove the prefix and describe the content directly.