AXIA Audit

Evaluate with evidence.
Improve with context.

An independent evaluation tool for web experience quality, combining HTTP evidence, controlled Chromium sessions, rendered DOM, accessibility-tree data and targeted probes.

Evaluation scope

Eight categories. Distinct kinds of evidence.

Explore the evaluation areas. Coverage depends on the inspected page, configured profiles and evidence available during a run.

Structure & Semantics

Review document structure, landmarks and semantic signals in the rendered page.

SEO & Discoverability

Inspect titles, metadata and indexing directives with their intended context.

Accessibility

Combine tested accessibility evidence with criteria that require human review.

Responsive & Visual

Inspect configured desktop, tablet and mobile profiles for layout and overflow evidence.

Performance

Collect observed loading, interaction and layout-stability measurements within the tested session.

Network

Inspect captured requests, failed resources and HTTP response evidence.

Console & Runtime

Surface captured exceptions, promise rejections and console messages for interpretation.

Security / Browser Safety

Inspect browser safety signals, secure context and mixed content within the observed scope.

Interpretation

A result is not a certification.

Accessibility with a defined scope

New Runs use WCAG 2.2 A/AA as their primary conformance scope, retaining AAA technical results outside primary counts. Automated evaluation does not establish complete criterion coverage or certification.

A stored Run’s policy snapshot determines interpretation. Historical Runs are not re-audited by the current engine.

Evidence and human judgment

Automated checks collect tested evidence. Assisted criteria can request human review. Observations provide context without an independent pass/fail status.

No aggregate AXIA Audit Score or AAA certification is implemented. Browser safety evaluation is not a penetration test.

Results & evidence

Read the evidence correctly.

Finding
An engine-classified issue supported by occurrence evidence. A heuristic finding is not automatically a standards violation.
Needs Review
Evidence requires human or contextual interpretation. It is neither an automatic failure nor a pass.
Passed
The tested condition passed in the observed state and available evidence.
Unable to Test
Required runtime, measurement or conclusive evidence was unavailable. This is not a pass.
Not Applicable
The current implementation did not identify an applicable condition in the inspected scope and state.
Observations / diagnostics
Contextual evidence stored separately from check results. It does not receive an independent check status.

Evaluation boundaries

Understand the scope.

Observed conditions

Viewports and interactions are sampled. Some measurements may be unavailable or inconclusive in the headless runtime. An unavailable measurement is not a pass.

Contextual interpretation

Optional SEO resources can be advisory. Human decisions are stored separately. Optional AI-assisted reports summarize supplied results; they do not execute additional tests.

AXIA