AXIA Framework
Structure before style.
People throughout.
An independent system of principles, rules and verifiable criteria for designing, building and evaluating digital experiences.
Technology-agnostic
A method you can take with you.
Independent by design
The Framework does not prescribe a programming language, rendering engine, editor or proprietary project format. Teams can apply its principles manually or through independent tools and generative agents.
Builder is one implementation tool. It is not a mandatory dependency. Audit is a separate evaluation tool; its checks are not automatically equivalent to the complete Framework.
Rules with a testable purpose
Semantic structure, navigation, content, color, interaction and portability have distinct responsibilities. Conformance needs evidence appropriate to each rule and condition.
WCAG 2.2 AA is the accessibility baseline. Higher text contrast is pursued when viable, without turning a contrast measurement into a claim of complete AAA conformance.
From principles to practice
Apply. Verify. Evolve.
Define the experience
Identify the purpose, users, content, routes, tasks and applicable components.
Build with explicit contracts
Connect semantics, layout, states, assets and interactions. Preserve meaning across implementations.
Collect evidence
Combine structural checks, real browser tests, contextual review and assistive technology evaluation.
Record limits and improve
Document exceptions and uncertainty. Historical rules awaiting reconciliation are not a certification checklist.