Case study · Passenger transport

A ferry booking flow nobody could finish without a mouse.

Ølundfærgen: Online ticket booking (demo). Audited against WCAG 2.2 AA on 26 October 2026.

  • 16 issues
  • 3 blockers
  • 3 high
  • Does not conform

Demo audit. Ølundfærgen is a fictional company. We built the site to copy patterns we often see on real Danish sites, then audited it the way we audit client work. Screen reader results are predicted from the accessibility tree and will be confirmed with NVDA and VoiceOver.

The brief

Why this site, and why it matters.

No one can book a ticket without a mouse today, and a car or family booking is blocked twice over. The three blockers are contained widget fixes worth about 3–4 developer days; with the top five done, the core booking journey becomes usable and the remaining issues are polish.

Ticketing for passenger transport is named explicitly in the European Accessibility Act, and regional ferry and bus operators are typically 50–250 staff with one booking flow carrying most of the revenue. The flow is modelled on common multi-step booking widgets: a custom date picker, a departures table, a drag slider for vehicle length and a payment hold timer.

Websites and e-tickets for passenger transport by water are services covered by the EAA (Article 2(2)(c)) and the Danish Accessibility Act. A booking flow launched or redesigned after 28 June 2025 must conform now; older services have until June 2030.

Sector
Passenger transport: regional ferry operator
Scope
8 templates and states, 3 journeys
Standard
WCAG 2.2 AA, mapped to EN 301 549
Result
Does not conform

Journeys

Could a person get through?

We ran each journey start to finish by keyboard and at 400% zoom. Screen reader results are predicted until we confirm them with NVDA and VoiceOver.

  • Book a foot-passenger ticket

    Route and date → departure → passengers → payment

    Keyboard
    Blocked
    Screen reader predicted
    Blocked
    400% zoom
    Completed with difficulty
    Outcome
    Blocked

    OF-001 date can't be chosen

  • Book with a car

    As above + vehicle type and length

    Keyboard
    Blocked
    Screen reader predicted
    Blocked
    400% zoom
    Completed with difficulty
    Outcome
    Blocked

    OF-001; OF-002 vehicle length slider is drag-only

  • Book for a family (2 adults)

    Passenger count on step 1

    Keyboard
    Blocked
    Screen reader predicted
    Blocked
    400% zoom
    Completed
    Outcome
    Blocked

    OF-003 passenger count can't be changed

The automated scan

What axe-core saw.

Of the 16 issues, 2 are fully detected by axe-core and 1 partly. The other 13, including all three blockers and the timer that wipes a booking, pass an automated scan.

16 issues found by testing by hand

2 fully flagged by axe-core

1 partly flagged

0/3 blockers fully flagged

Key findings

The barriers that stop people.

Every finding in a Doorwide report has the same parts: where it is, who it affects, how to reproduce it and a code-level fix. Effort runs S, M, L.

OF-001 · Step 1, “Udrejse” date picker

The travel date can't be chosen without a mouse

Blocker Effort M Not flagged by axe 2.1.14.1.21.3.1

Who it affects
Keyboard, screen reader, switch and voice control users
What happens
The date field is a <div> that opens a calendar of <div> day cells. Neither can be focused: Tab moves from “Rute” straight to “Find afgange”. The “Udrejse” label isn't tied to anything, and the accessibility tree shows only the text “Vælg dato”. Pressing “Find afgange” without a date just turns that text red.
Fix
Use <input type="date"> (well supported, gives a native picker on mobile). If a custom calendar is required, follow the WAI-ARIA APG date picker dialog pattern: a button that opens a dialog with a grid, arrow-key navigation and Escape to close.
<label for="date">Udrejse</label>
<input type="date" id="date" name="date" min="2026-11-03" required
       aria-describedby="date-hint">
<p id="date-hint" class="hint">Fx 12-11-2026</p>
Booking widget with the custom calendar open: a grid of November 2026 days. None of the days can be reached with the Tab key.
Evidence for OF-001

OF-002 · Step 3, “Køretøjets længde” slider

Vehicle length can only be set by dragging

Blocker Effort S Not flagged by axe 2.1.12.5.74.1.2

Who it affects
Keyboard users, people with tremor or limited dexterity, voice control users
What happens
The slider is a <div> knob that only responds to pointer drag. It has no role, no value for assistive technology and no keyboard support, and there is no text field alternative. The help text warns that a wrong length can mean a surcharge at check-in.
Fix
Use a number input in metres, optionally paired with a native range input. Both are keyboard and screen reader accessible and need no dragging.
<label for="len">Køretøjets længde i meter (inkl. cykelstativ og trækkrog)</label>
<input type="number" id="len" min="2" max="14" step="0.1" value="5" inputmode="decimal">
Step 3 with “Personbil” selected and the vehicle length slider showing 5,0 m. The slider has no text field next to it.
Evidence for OF-002

OF-003 · Step 1, “Voksne” stepper

Passenger count can't be changed by keyboard

Blocker Effort S Not flagged by axe 2.1.14.1.2

Who it affects
Keyboard and screen reader users travelling with others
What happens
The – and + controls are <span> elements with click handlers. They can't be focused and aren't announced, so a keyboard user can only ever book for one adult. The current count isn't tied to a label either.
Fix
Use real buttons and a live count, or a native number input.
<span id="adults-label">Voksne</span>
<button type="button" aria-label="Færre voksne">–</button>
<output id="adults" aria-labelledby="adults-label" aria-live="polite">1</output>
<button type="button" aria-label="Flere voksne">+</button>

OF-004 · Step 5, “Vi holder pladsen til dig i 10:00”

The booking hold expires silently and wipes the booking

High Effort M Not flagged by axe 2.2.1

Who it affects
Screen reader users, people with cognitive or motor disabilities who need more time
What happens
The payment step starts a 10-minute countdown. At zero the page reloads to step 1 and every entered detail is lost. There is no warning before it runs out and no way to extend it. Users of assistive technology routinely need longer than 10 minutes for a 5-step booking with payment.
Fix
Show a warning dialog at 2 minutes left with “Forlæng med 10 minutter”; announce it with role="alertdialog". If the hold lapses, keep the form data and only re-check availability.
<div role="alertdialog" aria-labelledby="t-h" aria-describedby="t-d">
  <h2 id="t-h">Din reservation udløber om 2 minutter</h2>
  <p id="t-d">Vil du have mere tid?</p>
  <button>Forlæng med 10 minutter</button>
</div>
Payment step showing “Vi holder pladsen til dig i 10:00”, a confirm e-mail field and card fields. There is no button to extend the time.
Evidence for OF-004

Fix first

The top five fixes.

Ordered by impact on the journeys, then by effort.

  1. OF-001Replace the date picker with a native date input or an accessible gridEffort M
  2. OF-002Swap the drag slider for a number input (with an optional range input)Effort S
  3. OF-003Turn the passenger stepper spans into buttonsEffort S
  4. OF-004Warn before the hold timer expires and let users extend itEffort M
  5. OF-005Name each invalid field in text and announce the errorsEffort M

All findings

All 16 issues.

3 blockers, 3 high, 9 medium and 1 low. The full report also has steps to reproduce, the WCAG and EN 301 549 mapping and a draft accessibility statement.

  • OF-001The travel date can't be chosen without a mouseBlockerNot flagged by axe
  • OF-002Vehicle length can only be set by draggingBlockerNot flagged by axe
  • OF-003Passenger count can't be changed by keyboardBlockerNot flagged by axe
  • OF-004The booking hold expires silently and wipes the bookingHighNot flagged by axe
  • OF-005Errors don't say which field is wrong and aren't announcedHighNot flagged by axe
  • OF-006Pages don't reflow at 320 px (400% zoom)HighNot flagged by axe
  • OF-007Step changes aren't announced, and the title never changesMediumPartly flagged by axe
  • OF-008The chosen departure is shown only by colour, and the price update is silentMediumNot flagged by axe
  • OF-009No booking summary before paymentMediumNot flagged by axe
  • OF-010E-mail is asked for twiceMediumNot flagged by axe
  • OF-011Passenger fields lack autocompleteMediumNot flagged by axe
  • OF-012Date of birth selects have no labelsMediumFlagged by axe
  • OF-013Primary buttons and the step bar fail text contrastMediumFlagged by axe
  • OF-014Input borders and control outlines are too faintMediumNot flagged by axe
  • OF-015Fixed price bar hides focused footer linksMediumNot flagged by axe
  • OF-016No skip linkLowNot flagged by axe

Your site

Can every customer finish your checkout?

A founding-client audit is 9,900 DKK for two key journeys. Ask us for the full sample report by email.