Skip to main content
Accessibility.com, LLC
Category: Testing and Evaluation

axe Auditor

Also known as: Axe Auditor, axe Auditor®
Simply put

axe Auditor is a commercial accessibility testing tool from Deque Systems that guides testers through manual, step-by-step checks of digital properties such as websites, mobile apps, and documents. It is designed to help testing teams evaluate accessibility and produce reports and audit records. Because it emphasizes guided manual testing, it addresses issues that fully automated tools alone may not detect.

Formal definition

axe Auditor is a manual accessibility testing and reporting product developed by Deque Systems, distinct from Deque's automated axe rules engine. It provides a structured, step-by-step workflow for auditing websites, mobile applications, and documents, along with reporting and audit-trail capabilities intended to support testing teams performing manual evaluation. As a manual testing tool, it complements automated scanning, which detects only a portion of accessibility issues; comprehensive assessment generally also requires manual and assistive technology testing. Vendor descriptions characterize it as offering 'full-coverage' auditing, though such claims are marketing terminology and do not by themselves establish conformance to a specific WCAG version or level, nor legal compliance under frameworks such as the ADA or Section 508. This entry describes the tool as presented in the cited evidence and is not an endorsement; consult qualified counsel and current standards for compliance decisions.

Why it matters

Automated accessibility scanning is fast and scalable, but it detects only a portion of the barriers that affect people with disabilities. Many success criteria in the Web Content Accessibility Guidelines (WCAG) require human judgment, evaluating whether alternative text is meaningful, whether reading order makes sense, or whether an interaction works as expected with assistive technology. Tools like axe Auditor exist to structure that human work, guiding testers through step-by-step manual checks so that evaluation is more consistent and reproducible across a team.

Who it's relevant to

Accessibility engineers and QA testers
Practitioners who perform manual accessibility evaluation may use axe Auditor to bring structure and consistency to their step-by-step checks, and to complement automated scanning with human review of issues that automated tools cannot detect.
Accessibility and QA team leads
Those coordinating testing across multiple people or projects may value the reporting and audit-trail capabilities to standardize how manual audits are conducted and documented, supporting internal quality processes and remediation planning.
Compliance officers and program managers
Individuals overseeing accessibility programs may find documented manual testing useful for tracking work performed, while recognizing that completing an audit does not by itself establish WCAG conformance or legal compliance. Compliance conclusions should involve qualified counsel and current standards.
Product and development teams
Teams building websites, mobile apps, or documents may rely on manual audit results to prioritize and verify fixes, using guided testing as one input alongside automated scanning and assistive technology testing.
Legal counsel and risk stakeholders
Attorneys and risk managers should understand that manual testing tools support, but do not guarantee, an accessible experience or legal safety. Requirements under the ADA, Section 508, and related authorities evolve through regulation and case law, and this entry is not legal advice.

Inside axe Auditor

Guided Manual Testing Tool
axe Auditor is a manual accessibility testing product in the Deque axe family that structures human-led evaluation, guiding testers through a defined workflow to assess conformance against WCAG success criteria rather than relying solely on automated scanning.
Test Workflow and Checklists
It generally provides step-by-step procedures and checklists that map to WCAG requirements, helping testers apply consistent methodology across pages, components, and screens.
Assistive Technology and Manual Verification
Because automated tools detect only a portion of accessibility issues, axe Auditor is oriented toward the manual and assistive-technology testing needed to evaluate criteria that require human judgment, such as keyboard operability, focus order, and meaningful alternative text.
Documentation and Reporting
It commonly captures findings, evidence, and results in a structured format so that issues can be tracked, communicated to development teams, and referenced against the WCAG version and conformance level being targeted (often AA).
Relationship to the Broader axe Toolset
axe Auditor is part of a larger set of Deque axe products; it complements automated tools like the axe-core engine rather than replacing them, addressing the manual portion of a complete testing approach.

Common questions

Answers to the questions practitioners most commonly ask about axe Auditor.

Does using axe Auditor guarantee that a website is WCAG-conformant or legally compliant with the ADA?
No. axe Auditor is a testing tool that helps identify and document accessibility issues, but no tool can guarantee full WCAG conformance or legal compliance. Automated and guided testing detects only a portion of potential issues, and meeting technical success criteria does not by itself guarantee an accessible experience for all users or immunity from legal claims. Conformance, usability, and legal compliance are distinct concerns, and questions about legal exposure should be directed to qualified legal counsel.
Is axe Auditor a fully automated scanner that finds every accessibility problem on a page?
No. axe Auditor is a guided manual testing tool rather than a purely automated scanner. Automated checks can only identify a subset of accessibility issues, so comprehensive evaluation generally requires guided manual review and assistive technology testing in addition to any automated pass. Relying on automated results alone will leave certain categories of issues undetected.
How does axe Auditor fit into a broader accessibility testing workflow?
axe Auditor is commonly used as one component of a layered approach that may combine automated scanning, guided manual testing, and testing with assistive technologies such as screen readers. It can help testers work through checks in a structured way and document findings, but organizations generally supplement it with additional manual and assistive technology evaluation to cover issues that tooling cannot detect on its own.
Which WCAG version and conformance level should teams target when using axe Auditor?
The tool can be used to evaluate against WCAG success criteria, but the version (such as WCAG 2.0, 2.1, or 2.2) and conformance level (A, AA, or AAA) to target are decisions the organization makes based on its goals and any applicable obligations. Level AA is the level most commonly cited as a target. Teams should confirm which version and level apply to their context and consult current agency guidance or legal counsel where obligations are involved.
Who typically performs testing with axe Auditor?
Guided testing tools are generally used by people with some familiarity with accessibility concepts, such as accessibility engineers, QA testers, or designers, because interpreting results and completing manual checks requires human judgment. The tool structures the process, but the accuracy of the findings depends on the tester's understanding of WCAG requirements and assistive technology behavior.
How should findings from axe Auditor be documented and acted upon?
Findings are commonly recorded as issues mapped to the relevant WCAG success criteria, prioritized, and tracked to remediation. Because a single tool captures only part of the picture, teams often combine its output with results from other automated, manual, and assistive technology testing to build a fuller record. Documentation practices should reflect that identified issues represent detected problems, not a complete or final measure of conformance.

Common misconceptions

Running axe Auditor makes a site fully WCAG conformant and legally compliant.
Using a testing tool, even a strong manual one, does not by itself guarantee full conformance, an accessible experience for all users, or immunity from legal claims. Conformance, usability, and legal compliance are distinct, and requirements evolve through regulation and case law. Consult qualified legal counsel for compliance questions.
axe Auditor is an automated scanner that finds all accessibility issues.
It is oriented toward guided manual testing. Automated checks detect only a portion of possible issues, so manual evaluation and assistive technology testing are needed to assess many WCAG success criteria that require human judgment.
The tool's checklist reflects a single fixed legal standard.
It maps to WCAG success criteria, which differ across versions (2.0, 2.1, 2.2) and conformance levels (A, AA, AAA). WCAG is a technical guideline published by the W3C, not a codified legal mandate; the ADA does not itself specify a WCAG version, though settlements and agency guidance have often referenced WCAG as a benchmark.

Best practices

Use axe Auditor's manual and assistive-technology testing alongside automated scanning, treating each as covering different portions of potential issues rather than substituting one for the other.
Explicitly define the target WCAG version and conformance level (commonly 2.1 or 2.2 at Level AA) before testing, and confirm that checklist items map to that version.
Verify criteria that require human judgment through real assistive technology and keyboard testing, since these are not reliably detected by automated tools.
Document findings with evidence and reference the specific success criteria so results can be tracked, remediated, and communicated to development teams.
Retest after remediation and periodically thereafter, recognizing that conformance is not permanent and that content changes and evolving standards can introduce new issues.
Treat testing outputs as engineering and usability inputs, not as legal assurance; consult qualified legal counsel and monitor current agency rulemaking and case law for compliance decisions.