How an AX Audit works
What Tityra checks, how to read the scores, and what happens before your website audit report is delivered.
Start with an agreed website scope
Choose a website and an audit package. We review your request and your authority to have the website audited before work begins. Page counts refer to pages scanned, not the length of the report.
The audit covers the agreed sample. A finding on sampled pages is not evidence that every page on the website has been checked. The first PDF discovered is reviewed where available; additional PDF reviews can be agreed separately.
Compare what agents receive
Our AX audits check against the AgentReady essentials as part of the assessment framework. We review discovery, access to content and how clearly that content can be understood within the agreed website scope. Each finding links the relevant checks to evidence. Reports do not certify a site, declare AgentReady compliance or award an AgentReady badge.
Website checks include HTML structure, Schema.org data and automated accessibility checks, together with available source, date and usage information. We compare the original HTML with the page after JavaScript runs to identify differences in the available content.
Findings connect an observation with its impact, affected resources and practical recommendations. Available evidence can include a URL, an excerpt, a location within a page and the check used. Each report is reviewed by a member of our team before release. Expert Review provides deeper investigation within an agreed scope.
Read scores alongside the evidence
Scores summarise the checks supplied for the audited sample. The report identifies its audit dimensions, evidence and methodology; dimensions without a supplied score should not be read as passing. A dimension score and a finding’s severity describe different things: the score summarises checks, while severity helps prioritise an issue.
A score is not a certification of accessibility conformance, a complete security assessment or a prediction of search rankings, AI citations or recommendations. Automated accessibility checks cannot establish full conformance; manual testing is needed. Compare repeat audits with their scope, checks and report revision in view.
Review, delivery and follow-up
Submitting a request acknowledges your interest; it does not start an instant scan, take payment or promise a delivery date. Timing depends on the agreed scope, access, review and availability. Contact us to agree a schedule before relying on a deadline.
Track the request and read your released report in the Tityra workspace. Reports bring together findings, recommendations and supporting evidence. Available downloads depend on the report. You can discuss findings and track remediation in the workspace. A customer marking an issue resolved does not mean Tityra has independently retested it.