Skip to main content

Accessibility Cloud Automatic Test Coverage: Web

Last updated

Every scan runs one engine: axe-core, QualWeb, or ACAI, which orchestrates the other two alongside its own tests and merges the results.

230 rules across three engines

Rules the engines mark experimental or deprecated are excluded.

ACAI, or preferred open-source engine

ACAI orchestrates the other two alongside its own tests and merges the results.

Each headline figure counts the rules that report by default: WCAG level A and AA. Every engine also supports AAA and best-practice rules, and QualWeb supports a second category of WCAG technique rules on top of its ACT rules. Their findings stay hidden until you turn them on in the options menu.

Partial WCAG 2.2 coverage counts the success criteria an engine’s default rules test for, out of the 55 at level A and AA. Automated rules can only test part of a criterion, not all of it, and the three engines overlap heavily, targeting highly encountered accessibility errors that are also testable automatically.

Engine contributions to ACAI

ACAI runs 78 of those 230 rules.

    Accessibility Cloud is grateful to Deque Systems and University of Lisbon for axe-core and QualWeb, respectively, for their enormous contributions to building a more accessible internet.

    ACAI

    What ACAI’s rules test

    Conformance level, user impact and how the test is implemented, across the combined scan.

    Conformance level

    User impact

    Test type

    Every rule

    All 230 rules across the three engines. Filtering by ACAI shows everything a combined ACAI scan returns, including the axe-core and QualWeb rules it drives.

    Filters
    Rule ids link to each engine’s own documentation.
    IDRuleEngine TypeCategorySC LevelImpact In ACAI

    Source: the ac-assets rule data for axe-core, QualWeb and ACAI. Impact is the value Accessibility Cloud stores per rule.