Method

Accessibility audit: what cost should you expect for your website?

The cost of an accessibility audit primarily depends on the scope, depth of testing, and the complexity of the site. An automated scan is significantly cheaper than a full manual audit, but it does not meet the same requirements.

The short answer

The cost ranges from a few hundred euros for an automated scan to several thousand euros for a full manual audit. The quote varies depending on the number of pages and components, the sample selected, the reference framework applied, the proportion of manual testing, and the inclusion of a counter-audit. To reduce the bill, start by detecting and correcting automatable defects before bringing in an auditor.

There is therefore no universal price applicable to all websites. Two services with the same number of pages may require very different levels of effort if one relies on a few simple templates while the other involves numerous interactive pathways. To obtain a realistic estimate, you must describe the functionalities, user profiles, environments to be examined, and the expected level of detail in the report.

What the price of an audit actually covers

A quote must specify the reference framework, the pages or screens examined, the testing methods, and the deliverables. The term “audit” can refer to a simple automated check or a thorough assessment including keyboard navigation, assistive technology testing, and human analysis.

• Definition of a representative sample
• Automated tests and manual checks
• Qualification and prioritisation of non-conformities
• Report usable by teams
• Presentation and potential discussions

Preparation accounts for a significant part of the work. The auditor must understand the service, identify common templates, select specific content, and create scenarios covering essential functions. This phase prevents testing identical pages multiple times while overlooking a critical user journey.

The report may also explain each defect, indicate the relevant criterion, describe the reproduction method, and suggest a correction approach. The more detailed the evidence and recommendations, the more directly usable the document is for design, development, and content teams. This level of documentation logically impacts the price.

The factors that influence the quote

The functional scope

A homogeneous showcase website requires less exploration than a service that includes forms, authenticated areas, payments, documents, and interactive components. The total number of URLs is less decisive than the actual diversity of user journeys and templates.

Elements produced by third-party services must also be identified. An interactive map, a booking module, a payment tool, or a consent window may introduce specific behaviors. Their inclusion in the audit must be clarified, particularly when the organization does not directly control their code.

The depth of the evaluation

A targeted sample provides useful insights without covering the entire service. A more extensive RGAA audit requires additional human checks, evidence, and documentation. A follow-up audit, conducted after corrections, also constitutes a separate service.

The level of coverage can range from a diagnostic aimed at guiding an initial correction phase to a formalized evaluation on a representative sample. The former primarily seeks to identify structural issues. The latter requires a more documented methodology, criterion-by-criterion results, and sufficient traceability to justify the conclusions.

Technical complexity

Single-page applications, dynamically updated interfaces, rich tables, editors, multimedia players, and custom components demand more extensive testing. The auditor must verify context changes, focus management, status messages, accessible labels, and behavior with different interaction modalities.

Tested environments and technologies

The cost may vary when multiple versions need to be examined: public website, authenticated area, mobile interface, or pre-production environment. The choice of browsers and assistive technologies must remain consistent with the reference framework, intended usage, and conditions specified in the quote.

Automation and manual audits are not equivalent

An automated tool quickly identifies certain reliably detectable flaws. It cannot alone assess the relevance of alternative text, the logic of a user journey, or the quality of screen reader output.

Automated checks are particularly useful for detecting missing attributes, certain structural errors, measurable contrast issues, or incorrect associations. They can be run regularly and integrated into the development cycle to prevent the reoccurrence of known flaws.

Human testing covers what code alone cannot determine. An image may have alternative text yet remain poorly described. A button may technically have an accessible name but be incomprehensible in context. A form may appear valid while navigation order or error feedback actually prevents its use.

A combined approach thus leverages each method where it is most effective. Automation speeds up initial detection and monitoring, while manual review provides the essential context for a thorough evaluation.

How to reduce costs without weakening the audit

The most rational lever is to reserve human expertise for issues that require judgment. A pre-scan allows you to first correct obvious errors and present the auditor with a cleaner scope.

• Group pages by template
• Inventory critical user journeys
• Fix automatable defects upstream
• Provide stable test access and data
• Clearly define the expected deliverable

Inclaria can provide a prioritised assessment before the manual audit. This step does not replace human expertise but helps reduce noise and better frame the service.

The stability of the environment is also essential. If screens change during the evaluation, some checks will need to be repeated, and evidence may no longer match the version examined. It is therefore preferable to plan a stable period, communicate planned changes, and provide functional test accounts.

Existing documentation can also save time: component inventory, interface library, list of templates, description of user journeys, and correction history. It helps the auditor understand the service more quickly and select a relevant sample.

Finally, a team can organise corrections by families of causes rather than page by page. Fixing a shared component, a generation rule, or an editorial template can resolve multiple occurrences at once. This approach not only reduces audit costs but also improves remediation efficiency.

Comparing quotes reliably

Compare the scope and methodology rather than the isolated amount. Check the pages included, the environments tested, the role of manual testing, the format of evidence, the reporting, and the conditions for a review after corrections.

Be wary of offers that equate an automated score with full compliance. A tool can support evaluation, but compliance cannot be deduced from a single score.

Ask whether the quote clearly distinguishes preparation, test execution, report writing, and reporting. Also, check the number of question cycles included, delivery deadlines, and the period during which findings remain open for discussion with the auditor.

A higher price may correspond to a more representative sample, more in-depth manual testing, or a better-documented report. Conversely, a cheaper offer may be sufficient for an initial diagnosis. The right choice depends on the objective: quickly identifying major obstacles, preparing a redesign, supporting compliance efforts, or verifying corrections already made.

Planning the correction budget

The cost of the audit represents only a part of the overall budget. Once non-conformities are identified, it is necessary to allocate the time required for their analysis, correction, testing, and any updates to shared content or components.

The cost of remediation depends on the nature of the defects. Adjusting colors or completing certain labels can be relatively quick. Redesigning an interactive component, a payment process, or a form architecture may require more design, development, and testing.

Clear prioritization helps manage this phase. Teams can first address blockages affecting essential functions, then common components, and finally more localized defects. The audit report should facilitate this organization without turning technical severity into legal advice.

Cadre juridique et limites

The European Accessibility Act has been applicable since 28 June 2025 to certain products and services within its scope. An organisation’s situation depends in particular on its activity, its status, and the service in question.

This content is for informational purposes and does not constitute legal advice. To determine your obligations in a specific case, consult the applicable regulations, the competent authorities, or a specialised lawyer.

The chosen framework, the potential publication of a declaration, and other associated obligations must be determined according to the actual legal framework applicable to the organisation. A technical audit provides useful findings, but it alone is not sufficient to establish the full legal situation.