Website accessibility audits that tell you exactly what to fix

Automated scan plus manual keyboard and screen-reader testing against WCAG 2.2 AA. A prioritised report in plain language and an accessibility statement draft. Scan from €490, full audit from €1,200.

from€490quick audit, excl. VAT 25.5%. Manual WCAG 2.2 audit from €890, full audit from €1,200. Fixed price, written quote within one working day. proposed

Try the contrast checker: it uses the same WCAG 2.2 formula as the audit.

Test a colour pair

Try:

Book your appointment today

Book your appointment today

Book your appointment today
Contrast ratio3.35:1
Normal text (AA, 4.5:1)Fail
Large text (AA, 3:1)Pass
Controls and icons (3:1)Pass
Nearest text colour that passes: #262626 at 4.50:1

What the audit covers

Eight areas, each tested on desktop and on a phone. Every finding names the WCAG 2.2 success criterion it fails, so your developer can look it up.

Automated scan

Every agreed page template run through automated rule checks for what machines can find: missing alternative text, empty links and buttons, contrast failures, ARIA misuse.

Keyboard

Every menu, form, dialog and carousel used without a mouse: no traps (2.1.2), logical focus order (2.4.3), a visible focus (2.4.7) that is not hidden by sticky bars (2.4.11).

Screen readers

Landmarks, headings, labels, live messages and error text tested for sense, not only presence, with NVDA on Windows and VoiceOver on macOS and iOS.

Forms and checkout

Labels and instructions (3.3.2), clear errors (3.3.1), no re-typing what you already entered (3.3.7) and log-in without memory puzzles (3.3.8).

Colour, zoom and reflow

Text contrast 4.5:1 (1.4.3), controls 3:1 (1.4.11), reflow at 320 CSS px wide, the same as 400% zoom (1.4.10), and custom text spacing (1.4.12).

Touch and pointer

Targets at least 24 by 24 CSS px or well spaced (2.5.8), and a single-pointer alternative to every drag, such as sliders and map pins (2.5.7).

Media and documents

Captions for video (1.2.2), text alternatives for audio, and the PDFs your customers must read: tags, reading order and form fields.

Statement draft

A draft public accessibility statement: what conforms, what does not yet, the fix plan and how people can report a problem. You publish it; see this site's own.

What WCAG 2.2 added, and how I test it

WCAG 2.2 became a W3C Recommendation in October 2023. It keeps everything in 2.1, removes 4.1.1 Parsing, and adds nine success criteria. These six are at levels A and AA, the level European rules point to; the other three are AAA.

Level A and AA criteria new in WCAG 2.2. Criterion numbers and names as published by the W3C.
CriterionLevelWhat it asksHow I test it
2.4.11 Focus Not Obscured (Minimum)AAA focused element is not entirely hidden by sticky headers, cookie banners or chat widgets.Tab through each template with the cookie banner and sticky bars showing.
2.5.7 Dragging MovementsAAAnything done by dragging can also be done with single taps or clicks.Sliders, sortable lists, maps and carousels operated with clicks only.
2.5.8 Target Size (Minimum)AAPointer targets are at least 24 by 24 CSS px, or have enough space around them.Measured on the phone layout: filters, pagination, quantity steppers, close buttons.
3.2.6 Consistent HelpAHelp links, contact details or chat appear in the same order on every page that has them.Compared across templates, including checkout and account pages.
3.3.7 Redundant EntryAInformation already entered in the same process is filled in or selectable, not typed again.Full checkout run: shipping to billing address, account creation after purchase.
3.3.8 Accessible Authentication (Minimum)AALogging in does not depend on a memory or puzzle test unless an alternative is offered.Log-in, password reset and CAPTCHA checked with a password manager and paste allowed.

Three findings from a sample report

Each finding has the same parts: the criterion, how serious it is, where it is, the evidence, the fix and the effort. Ranked so the first fixes help the most people.

example-shop.fi / WCAG 2.2 AA / fix list sample, not a client
Effort figures are examples
01
A11Y-001

Checkout fields have no programmatic labels

Criteria
1.3.1 Info and Relationships, 3.3.2 Labels or Instructions, 4.1.2 Name, Role, Value
Severity
High blocks screen-reader users at payment
Where
Checkout, step 2, all address fields
Evidence
<input type="email" placeholder="Email">
Screen reader: "edit text, blank"
Fix
<label for="co-email">Email</label>
<input id="co-email" type="email" autocomplete="email">
Effort
About 2 hours for the template example
02
A11Y-002

Keyboard focus is invisible across the theme

Criteria
2.4.7 Focus Visible
Severity
High keyboard users cannot see where they are
Where
Global stylesheet, every page
Evidence
*:focus { outline: none; }
Fix
:focus-visible { outline: 3px solid #4A4FB5; outline-offset: 2px; }
Effort
About 1 hour including a check on dark sections example
03
A11Y-003

Cookie banner covers the focused link

Criteria
2.4.11 Focus Not Obscured (Minimum)
Severity
Medium until the banner is dismissed
Where
Footer links on every page while the banner is open
Evidence
Tab to footer: focused "Returns" link sits under
the fixed banner (bottom 0, height 140 px).
Fix
html { scroll-padding-bottom: 160px; }  /* while banner open */
Effort
About 1 hour example

Want to know where your site stands? Start with the scan.

Get a free quote

The European Accessibility Act, in plain language

Since 28 June 2025 the European Accessibility Act sets accessibility requirements for many products and consumer services sold in the EU, including e-commerce. Whether it applies to you depends on what you sell, who you sell to and the size of your business.

  • In forceSince 28 June 2025, with transition periods for some existing services and products.
  • Often in scopeOnline stores and other consumer services sold to people in the EU.
  • Exemption to checkMicro-enterprises providing services: fewer than 10 staff and an annual turnover or balance sheet of no more than €2 million.
  • Technical yardstickThe harmonised standard EN 301 549, which builds on WCAG at level AA.

This is not legal advice. Check your own obligations with the supervising authority or a lawyer. Finnish information on the requirements is at saavutettavuusvaatimukset.fi. A store-focused scope check is coming on its own page. coming

How the audit works

Read-only access is enough. Nothing on your live site changes until you decide what to fix.

  1. 1

    Scope

    We agree the page templates that represent the site: home, listing, product, cart, checkout, account, a form, a PDF.

  2. 2

    Test

    Automated checks, then keyboard and screen-reader testing on desktop and a phone.

  3. 3

    Report

    Plain-language findings with criterion, evidence, fix and effort, ranked by impact.

  4. 4

    Fix

    Fix it yourself, with your developer, or with me at €95 per hour excl. VAT.

  5. 5

    Retest

    Confirm the fixes and finalise the statement draft.

When I would not sell you an audit

An audit is worth paying for when its findings will be fixed. Sometimes something else comes first.

  • 01Your site is about to be rebuilt. Build the new one accessible from the start, on the websites or ecommerce route, then scan it before launch.
  • 02You need a legal opinion on whether the law applies to you. That is a question for a lawyer; I test the site, not your obligations.
  • 03You want a badge or an overlay widget to make the problem go away. I do not sell either: overlays do not change the code that fails, and no audit is a certificate.

Packages

Fixed prices in euros, excluding VAT 25.5%. You own the report and every account.

Quick audit

Where do we stand? A fast first view.

from€490one-off, excl. VAT proposed
  • Up to 3 page templates
  • Automated scan and keyboard check
  • Summary of main issues
Get a free quote

Manual WCAG 2.2 audit

Keyboard and screen-reader testing on your key templates.

from€890one-off, excl. VAT proposed
  • Up to 5 page templates
  • Manual keyboard and screen reader testing
  • Prioritised fix report
Get a free quote
Recommended

Full audit

A complete WCAG 2.2 AA review.

from€1,200one-off, excl. VAT proposed
  • Up to 8 page templates
  • Manual and screen reader testing
  • Prioritised fix report
  • Draft accessibility statement
Get a free quote

Fix support

Help implementing the fixes.

from€95per hour, excl. VAT proposed
  • Code and content fixes
  • Retest after changes
  • Work in your CMS or repository
Get a free quote

Template counts per package owner to confirm

Questions about accessibility

What does an accessibility audit include?

A WCAG 2.2 AA review of the page templates we agree: an automated scan, manual keyboard testing, screen-reader testing, colour and zoom checks, and your forms and checkout. You get a prioritised report in plain language, each issue with its location, criterion, fix and effort, plus an accessibility statement draft.

Is my website legally required to be accessible?

Possibly, so check your own obligations. Since 28 June 2025 the European Accessibility Act covers many consumer services sold in the EU, including e-commerce, while micro-enterprises providing services are exempt. Public-sector sites have separate rules. I can show where your site stands against WCAG 2.2 AA; whether the law applies is for an adviser.

Can you fix the issues too?

Yes. I fix issues in WordPress, WooCommerce, Shopify, Magento, OpenCart and custom PHP themes at €95 an hour excl. VAT, or a fixed price per batch, and retest afterwards. If your own developer prefers to do the work, the report is written so they can follow it without me.

Book an accessibility audit

Send your website address and roughly how many different page types it has. You get a written fixed price within one working day.

Prefer email? Write to hei@pikselipolku.fi

An audit reports how your site measures against WCAG 2.2 AA. It is not legal advice or a certificate of compliance.

Audit requestReply within one working day

Optional: slow pages, lost rankings, a deadline, a law you need to meet.

About 2 minutes. Helps me send a firmer price.

Reply within one working day

Or email me: hei@pikselipolku.fi

Made in Tampere. The path ends here.61.4978° N, 23.7610° E

Tell me what you need. I reply within one working day.

About these landmarks
  • Näsinneula tower, Tampere, 1971. Opened in 1971, with an observation deck and a revolving restaurant at the top.
  • Finlayson mill, Tampere, 1820. Cotton mill founded in 1820 by James Finlayson; the red-brick mill and chimney still stand by the Tammerkoski rapids.
  • Tampere Cathedral, 1907. National Romantic granite church by Lars Sonck, with frescoes by Hugo Simberg.
  • Helsinki Cathedral, 1852. White neoclassical church with green domes above the Senate Square steps, designed by Carl Ludvig Engel.
  • Parliament House, Helsinki, 1931. Eduskuntatalo, built of red granite behind a front row of tall columns.
  • Temppeliaukio Church, Helsinki, 1969. The Rock Church: cut into solid bedrock and roofed with a copper dome.
  • Suomenlinna sea fortress, Helsinki, 1748. Island fortress begun in 1748 at the entrance to Helsinki harbour; a UNESCO World Heritage Site.
  • Olavinlinna castle, Savonlinna, 1475. Medieval castle with three round towers, built on a rock island between two lakes.
  • Sauna by a frozen lake, UNESCO 2020. Finnish sauna culture is on UNESCO’s list of the intangible cultural heritage of humanity.
  • Lapland: spruce, reindeer and a fell, North. The northern end of the journey: spruce forest, a reindeer and a snow-capped fell.
© 2026 Pikselipolku, Tampere, FinlandBusiness ID [Y-tunnus]Built to WCAG 2.2 AABack to top