Journey Audit
Find out exactly what stops a keyboard or screen reader user in your checkout, sign-up or booking, and what to fix first.
1 to 2 weeks 7,500 DKK per journey
Accessibility testing for webshops and booking sites
A clean automated scan can't tell you. We test your key journeys with the tools disabled people use: keyboard, screen readers and 400% zoom. Then we fix what stops them, together with your developers, and give you documentation you can show under the European Accessibility Act.
Caught by your CIHundreds of small, mechanical checks. Useful, and only part of the picture.
Found by peopleWhether someone can actually get through: checkout, sign-up, contact.
The gap
Tools like axe-core are good at frequent, mechanical problems, and you should run them. But the barriers that stop someone finishing a checkout are mostly the ones a machine can't judge.
$ npx @axe-core/cli https://shop.example/checkout 0 violations found! // Not detected: // focus jumps behind the cookie banner // "Pay" opens a dialog that traps the keyboard // card errors appear in red, never announced // sticky basket bar covers the focused field
6/47 barriers fully flagged by axe-core in our three demo audits, and none of the 7 blockers
37/55 WCAG 2.2 A and AA criteria in our checklist that need a person to test
16/50 WCAG 2.1 AA criteria where automated tools can flag issues at all
Automation catches: some controls that can't take focus.
Needs a person: whether every task can be finished by keyboard, with no traps and a logical focus order.
2.1.12.1.22.4.3
Automation catches: most text on solid colour.
Needs a person: text on images and gradients, focus rings, icons and input borders.
1.4.31.4.112.4.7
Automation catches: buttons and fields with no label.
Needs a person: whether the label makes sense, and whether "expanded" or "selected" is announced.
4.1.2
Automation catches: missing labels and autocomplete.
Needs a person: clear error messages that are announced, with suggestions and no lost input.
3.3.13.3.33.3.7
Automation catches: a viewport setting that blocks zoom.
Needs a person: layout at 400% and 320 px wide, no clipped text, no sideways scrolling.
1.4.41.4.101.4.12
Automation catches: some target sizes.
Needs a person: sticky headers hiding focus, dragging alternatives, accessible login.
2.4.112.5.73.3.8
Sources: Deque Automated Accessibility Coverage Report (WCAG 2.1 figures) and Doorwide's own WCAG 2.2 AA checklist.
Services
A journey is one task from start to finish, like search to checkout, creating an account or booking a table. You pick the journeys that matter most, and the price is on this page.
Find out exactly what stops a keyboard or screen reader user in your checkout, sign-up or booking, and what to fix first.
1 to 2 weeks 7,500 DKK per journey
Every customer can finish the journey, proven by a retest. We fix it with your developers, in your components where we can.
1 to 3 weeks From 12,000 DKK per journey
Deliver accessible client work without hiring a specialist. Journey audits and pre-launch checks under your own brand.
White-label Partner pricing
Founding clients
9,900 DKK
Instead of 13,500 DKK, in return for letting us write up the work as an anonymised case study. Prices exclude VAT.
Included
Doorwide is new, so the first three clients get a two-journey audit for less.
Process
Every audit follows the W3C's evaluation method, WCAG-EM, so the results hold up. Then we test the way people use your site.
audit.jsWCAG 2.2 AA · EN 301 549
Why now
The European Accessibility Act has applied to new products and services since 28 June 2025. Websites and apps meet it by conforming to EN 301 549, and version 4.1.1, published in September 2026, adopts WCAG 2.2 AA. It is expected to become the harmonised standard for the Act at the end of 2026.
Many existing audits were done against WCAG 2.1, which leaves out the six new A and AA criteria in 2.2. We audit against 2.2 and map every finding to its EN 301 549 clause.
Who it's for
Danish and EU companies of 10 to 250 people that sell or take bookings online: webshops, travel and ferry booking, events, restaurants and clinics. You have your own developers or an agency, and you may already run automated checks.
Agencies that build those sites can buy the same audits under their own brand.
Doorwide is run by a frontend developer with a UX background, so findings come with code-level fixes your developers can use.
Learn
We share what we learn: how to check your own journeys, what the European Accessibility Act asks for, and the barriers we keep finding.
Writing
Automated checks fully caught 6 of 47 barriers in our demo audits, and none of the 7 that stopped people completely.
Article 3 min read
Case studies
A webshop, a ferry booking flow and a savings app, tested journey by journey the way we test client work.
Demo audits 3 sites
Method
The checks we run by keyboard, screen reader and zoom, and how each finding maps to WCAG 2.2 and EN 301 549.
Guide WCAG-EM
Not sure where to start? Tell us which journey brings in the most money, and we'll send a fixed price within one working day.