Auditzo combines automated observation, controlled browser testing and human verification to document website privacy, tracking, consent and accessibility behaviour within an agreed scope.
The methodology is designed to produce clear technical findings, supporting evidence and remediation-oriented observations for engineering, privacy, business and counsel review.
Technical evidence and findings only. Auditzo does not provide legal advice, certify compliance or guarantee that every possible issue has been identified.
Technical findings are useful only when the tested scope, evidence source, verification method and limitations are clear enough for another team to understand and act on.
Findings are meaningful only when reviewed pages, environments, states, journeys and exclusions are clearly documented.
Technical observations should connect to screenshots, requests, storage records, affected pages, components or reproduction steps.
Automated output should not automatically become a confirmed privacy, tracking or accessibility finding.
A point-in-time review should state what was tested, what was excluded and what may vary by location, browser, session or website change.
Each review path provides a different level of coverage and evidence. Automated reviews are no-interaction; manual consent-state and accessibility testing are separately scoped services.
A quick automated, no-interaction review of observable cookies, browser storage and third-party requests during the initial public-page session.
Coverage boundary: No human verification, Accept/Decline interaction or downloadable raw evidence package.
A completely automated, no-interaction review that provides expanded structured observations beyond the free scan.
Coverage boundary: No human review, consent-banner interaction, separate Accept/Decline testing, HAR download, cookie export or raw evidence package.
A human-reviewed audit of agreed pages, journeys and consent states with evidence collected for the defined scope.
Coverage boundary: Can include screenshots, HAR and request evidence, cookie and browser-storage comparisons, cache-related observations and consent-state records.
Automated candidate discovery combined with human keyboard, semantic, visual, responsive and component-level verification.
Coverage boundary: Includes verified findings, supporting evidence, WCAG-oriented mapping and developer-focused remediation guidance.
The exact activities depend on the selected audit, but the core methodology follows a documented sequence so findings remain understandable and traceable.
Confirm domains, pages, journeys, regions, browsers, states, deliverables, exclusions and review objectives.
Record the browser, location, date, profile state and other relevant test conditions for the reviewed session.
Observe requests, cookies, storage, consent behaviour, screenshots or accessibility interactions included in the scope.
Reproduce candidates and confirm, reject, downgrade or classify them based on observed behaviour and available evidence.
Connect findings to affected pages, evidence, technical priority, remediation guidance and documented limitations.
Repeat relevant observations after changes or monitor meaningful privacy and tracking activity over time.
Auditzo confirms what is being reviewed before evidence collection begins.
Scope can include domains, representative pages, critical user journeys, geographic environments, browsers, consent states, accessibility coverage, third-party components, deliverables and known exclusions.
A clear scope prevents findings from being interpreted as if every page, user state or platform variation was tested.
A recorded environment helps explain why a specific request, consent state or accessibility behaviour was observed during the reviewed session.
The testing region is recorded because consent interfaces, tags and third-party behaviour may differ by location.
The browser family and version are documented where they are relevant to reproducing the observed behaviour.
Fresh or isolated browser states are used where required so previous cookies or choices do not unintentionally affect a session.
Audit evidence records when the website behaviour was observed because website and vendor implementations can change.
Access restrictions, regional differences, dynamic content and third-party platform limitations are recorded with the review.
Homepage-only scanning can miss tracking, consent and accessibility behaviour that appears only after search, form interaction, product selection, cart actions, checkout or embedded-service use.
Scope boundary: Auditzo reviews the pages and journeys included in the agreed scope. Findings should not be assumed to represent untested pages or authenticated areas.
Consent-state testing is performed only in applicable manual privacy audits. The Free Privacy Scan and Automated Detailed Review remain no-interaction reviews.
Observe what loads before the visitor interacts with the consent interface.
Record observable website activity after the visitor accepts the available consent choice.
Record what remains after non-essential consent is declined or rejected.
Where included, review behaviour after preferences are modified or consent is withdrawn.
The evidence package depends on the agreed manual scope and the behaviour available during the recorded sessions.
The presence of a request, cookie or script does not by itself establish a legal violation. Purpose, configuration, consent signals and applicable law may require privacy or counsel review.
Manual privacy findings can be linked to the page, consent state, screenshot, HAR file, request record, cookie comparison or browser-storage evidence that supports the observation.
HAR and raw evidence files are not included in the Automated Detailed Review. They are available only where included in an applicable manual audit scope.
Explore Manual Evidence AuditsClassification helps technical, privacy and business teams understand the likely role of observed domains and services.
Classification is based on observable technical context and available vendor information. It should be reviewed alongside the website owner’s implementation purpose and legal assessment.
Accessibility audits combine automated candidate discovery with manual verification. Automated results are treated as candidates, not automatically confirmed findings.
Candidates are reconciled, reproduced and reviewed before they are reported as verified findings.
Findings are conservatively mapped to relevant WCAG success criteria based on the observed behaviour and available evidence.
Auditzo does not turn scanner output directly into compliance claims. Candidates are reviewed, reproduced and assigned an appropriate status before report delivery.
An automated tool, manual review or evidence comparison identifies a potential issue.
The behaviour is reviewed again under the relevant page, state or interaction.
Screenshots, requests, storage records or interaction evidence are connected to the observation.
The candidate is confirmed, rejected, downgraded, marked for review or recorded as a limitation.
Confirmed findings receive a stable reference for remediation, discussion and retesting.
Not every candidate becomes a confirmed finding. Statuses help separate verified issues, observations, limitations and items that require more context.
Technical review priority helps teams plan remediation. It is not a legal conclusion, statutory penalty assessment or compliance certification.
Issues that prevent access, completion or meaningful use generally require earlier review.
Consistently reproducible behaviour provides a stronger basis for prioritization and remediation.
Business-critical journeys such as checkout, signup, booking or form submission may require higher priority.
One shared template or component issue may affect many pages and users.
Observable activity involving user data, consent choices or third-party destinations may need prompt technical review.
Fix timing and ownership may depend on platforms, plugins, apps, vendors or embedded services.
Auditzo checks the relationship between scope, findings, evidence, wording and limitations before a manual report is finalized.
The purpose is to reduce missing evidence, duplicated findings, unsupported claims and unresolved draft content.
Deliverables vary by selected service and agreed scope. Raw evidence files are available only in applicable manual audit engagements.
A concise overview of scope, key observations, priority themes and important limitations.
Structured findings with stable IDs, affected pages, evidence references and recommended next steps.
Cookie, browser-storage, cache-related and request comparisons across scoped consent states.
HAR, domain and network evidence where included in a manual privacy audit scope.
Verified findings, screenshots or interaction evidence, WCAG references and remediation guidance.
A follow-up record showing whether selected observations were resolved, changed or remained visible.
A retest repeats relevant observations in a recorded environment after selected fixes or configuration changes.
Safe retest wording focuses on what was reproduced. For example: “The original technical observation was no longer reproduced in the recorded retest environment.”
Discuss RetestingPrivacy monitoring should not be interpreted as continuous WCAG validation. Accessibility retesting is generally performed after relevant design, content or code changes.
These examples show how Auditzo adapts the review method to accessibility, consent-state and multi-domain scopes without presenting technical observations as final legal conclusions.
Seven representative pages were manually reviewed across keyboard access, semantics, responsive behaviour and embedded components, resulting in 29 verified findings.
Initial, Accept and Decline sessions were reviewed across product, cart and checkout journeys with screenshots, HAR, cookies and browser-storage evidence.
A consistent technical baseline was prepared across seven international brand websites using automated reports and manual fallback where access was restricted.
Use these pages to compare automated visibility, manual evidence, accessibility review and remediation support.
Start with automated visibility into observable cookies, storage and third-party requests.
Explore the expanded automated, no-interaction report path and its coverage boundaries.
Request controlled consent-state and user-journey testing with human-reviewed evidence.
Review the human-verified accessibility audit path with evidence and remediation guidance.
Move from privacy and tracking findings to implementation support and selected verification.
Prioritize verified accessibility findings and prepare developer-oriented fix guidance.
Auditzo provides technical observations, supporting evidence and remediation-oriented findings within a defined scope. Limitations are part of the methodology, not hidden after delivery.
Start with automated privacy visibility or define a human-reviewed tracking, consent or WCAG accessibility scope with evidence suited to your team’s needs.