Loading content
AXE is an open-source toolkit for automated accessibility testing of web applications. It integrates into test and CI pipelines, evaluates pages against WCAG rules and provides reproducible findings with remediation guidance for developers. It supports browser and DOM-based checks, integrations with build/test tools and reporting APIs.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Usable application software: supports people in a task.
Concrete cog in the system that works inside larger relationships.
AXE is an open-source toolkit for automated accessibility testing in web applications and components. It checks DOM and browser states against rules and turns violations into reproducible findings for development, testing, and CI.
AXE comes from Deque's axe-core ecosystem. The dequelabs/axe-core GitHub repository describes axe-core as an "Accessibility engine for automated Web UI testing." The toolkit addresses the recurring problem of checking accessibility rules quickly, consistently, and within existing browser, testing, and CI workflows.
Think of AXE as a rule-driven inspection scanner at the edge of a live web interface. The application is loaded in a browser or test run, AXE inspects the current DOM structure, matches elements against test rules, and flags possible violations with context. The result is a repeatable technical pre-check that can be wired into build and CI steps.
A defined set of checks determines which patterns are detected and how they are assessed.
AXE examines the current document structure, attributes, and relationships between elements.
Checks can run in manual browser sessions, automated tests, and pipelines.
The output names the location, rule, and often an initial hint for remediation.
Machine-checkable issues are mostly structural; operability and use context still need additional evaluation.
AXE is useful for fast regression tests, pull requests, component-level checks, and repeatable quality control in build and CI pipelines. It shortens the search for common issues, but it does not replace manual usability checks or testing with assistive technologies; depending on context, false positives and gaps can remain.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.