WCAG accessibility audit for e‑commerce and websites

We do not quote a single price, because an audit is priced by its scope: the number of processes and views covered, the number of templates and components, whether third-party components sit in the checkout, the conformance level, and whether the scope includes assistive-technology testing and re-verification after fixes. We confirm the figure in the offer, once the scope is settled.

It depends on the number of views, templates and processes in scope, and on how many of them need manual testing. We write the indicative timing into the offer along with the scope. Evaluating a single journey is far shorter than auditing a whole store with its checkout and customer account.

Since 28 June 2025 the Polish Accessibility Act (opens in a new tab), implementing the European Accessibility Act, has been in force, and it covers e‑commerce services among others. That does not mean the obligation applies automatically to every store: the Act provides exclusions, and establishing whether it covers a particular company and service calls for a legal assessment.

The Act covers the products and services it names, e‑commerce services offered to consumers among them, and places obligations on the economic operators involved in placing them on the market or providing them. Whether a given company and a given service fall under it depends on the kind of activity, the status of the business and the scope of the statutory exclusions. That assessment belongs to a lawyer, not to a technical audit.

The rules provide an exclusion for services offered or provided by microenterprises. Microenterprise status itself depends on headcount and turnover thresholds, and the exclusion applies to services — so it is not a blanket release from every obligation in every situation. Confirming that the exclusion applies calls for a legal assessment.

We run the audit against WCAG 2.2 (opens in a new tab) at level AA, because that is the newest version of the standard recommended by W3C; level AA also covers the level A criteria. WCAG 2.2 adds nine success criteria over WCAG 2.1, among them focus not obscured, dragging movements, minimum target size, redundant entry and accessible authentication. In the report we separate the requirements arising from the current technical standard and the regulations in force from the additional WCAG 2.2 criteria.

No. Automated tools can detect some faults, but they will not assess every criterion or whether a user can actually complete a task. A tool on its own cannot confirm conformance with WCAG — an audit has to include manual testing, keyboard navigation and form verification as well. W3C says the same (opens in a new tab).

Yes, and they are usually the most important part of the scope. The checkout is the longest form in a store and the place where third-party components appear. The evaluation covers field labels, instructions, validation, error messages, the order of the steps, the choice of delivery and payment, and authentication during the purchase. An e‑commerce audit does not stop at the home page and the product pages.

A report in which every non-conformance is described by the same chain: the WCAG criterion, where it occurs, the problem, the impact on the user, the recommended fix and the priority. Along with steps to reproduce, supporting evidence, the owning area, a summary for decision-makers, and a description of the scope, the method and the limits of the evaluation.

Yes, and both are agreed separately from the audit. The scope of the remedial work and its estimate follow once the priorities are approved, and re-verification after the changes is booked as a separate evaluation. The report is written, though, so that your current team or another supplier can make the fixes without us.

The scope is agreed before the work starts. In a large e‑commerce site we usually examine representative templates, components and complete processes, among them search, the product page, the cart and the checkout. The number of views depends on the complexity of the site and on the goal of the evaluation.

A WCAG audit on its own is not legal advice. Assessing readiness for the act also requires establishing whether the company and the service fall under it, and which additional obligations apply.

Yes. The evaluation can run on a test environment, provided it contains all the components and processes in scope. Finding problems before publication usually reduces the number of later changes to a finished interface.

It covers those elements that take part in the user's process and fall within the agreed scope. The report distinguishes components controlled by the site owner from elements that depend on a third-party supplier.