Accessible ferry booking: what WCAG 2.2 AA means on the website, the ticket and the gangway
· 22 min read
What an accessible booking site, ticket and boarding desk look like, what EU, Spanish, Italian, US and Australian rules require of public buyers, and a checklist for tenders.

A ferry is often the only way off an island. When the booking site cannot be worked with a keyboard, when the ticket is a picture of text, when the help a passenger asked for at the counter never reaches the crew at the gangway, the person who loses is the one with the fewest alternatives. On inter-island routes that is not a small group. It is the older half of the population, the people who read slowly in the language of the website, the people whose phone makes calls and nothing else, and anyone whose eyes or hands do not match the designer's.
This article sets out what the Web Content Accessibility Guidelines 2.2 at level AA require of a booking site, a ticket and a boarding desk; which laws make that level mandatory for public buyers in Europe, the United States and Australia; what passengers with disabilities, elders and people without a smartphone actually need; and what a procurement officer should write into a tender. It ends with a checklist and a worked example of a passenger who books by phone and boards by tender.
Who a bad booking flow excludes
The World Health Organization estimates that 1.3 billion people, about 16 percent of the world, live with a significant disability. That figure is the start of the list, not the end of it. On islands the share is higher than the national average, because the people who stay when the young leave for the mainland are older, and age brings most of the impairments that matter on a screen. By sixty most people need two to three times as much light to read as they did at twenty, and small grey text on white fails them first.
- About 8 percent of men and 0.5 percent of women have a colour vision deficiency. A seat map that marks free seats green and taken seats red, with nothing else, is unreadable to one man in twelve.
- Between 5 and 10 percent of people have dyslexia. Dense justified paragraphs, long lines and decorative typefaces slow them down; a wider line, a plain typeface and a reading ruler help.
- UNESCO counts about 750 million adults who cannot read a simple sentence, and far more who read slowly in the language the website happens to use. On island routes the booking site is often in a second language: English for a Chuukese speaker, Spanish for someone raised in Catalan, Italian for a family whose grandmother reads dialect more easily.
- The GSMA's 2024 connectivity report counts about 3.1 billion people who live under mobile broadband coverage and do not use it. Many own a phone that makes calls and receives SMS. A ticket that exists only inside an app does not exist for them.
- A blind passenger uses a screen reader, which speaks what the page's structure says, not what the page looks like. A passenger with a tremor or arthritis cannot hit a 16-pixel checkbox. A deaf passenger cannot ring the agency.
Then there are the situations that disable everyone. A wharf at noon turns a low-contrast screen into a mirror. A baby on one arm leaves one thumb. Seasickness makes an animated carousel unbearable. A broken wrist makes the mouse useless for six weeks. Accessibility is usually introduced as a minority concern; on a ferry it is simply the condition of most passengers at some point in the year.
On an island the booking site is not one of several ways to travel. It is the way, and whoever it excludes stays ashore.
What WCAG 2.2 AA asks of a booking flow
The four principles, with ferry examples
WCAG is organised around four principles, and each has a direct reading on a ferry line.
Perceivable. Everything the page conveys must reach at least one sense the passenger has. The departure table cannot be an image of a table; seat availability cannot be colour alone; the QR code needs a text alternative; a video safety briefing needs captions; a map of the wharf needs a text description of where the ramp is.
Operable. Every action must be possible from a keyboard, without a time limit the passenger cannot extend, without flashing content, and with a clear way to find things. The date picker, the passenger count stepper, the seat plan and the payment form must all work with Tab, Enter, Space and the arrow keys. A ten-minute seat hold must warn before it expires and offer an extension.
Understandable. The language of the page is declared, forms are labelled, errors are explained in words and placed where they can be found, navigation is consistent between pages, and the passenger is given a chance to review the booking before money moves.
Robust. The page uses correct HTML and ARIA so that screen readers, voice control, switch devices and browsers that do not yet exist can interpret it. In practice this means semantic elements (button, label, table, nav) rather than styled divs, and a test with real assistive technology rather than an automated scan alone.
Most of what a booking site needs is in a short list of success criteria. The numbers below are WCAG 2.2 criterion numbers, which a procurement officer can quote in a tender and an auditor can check one by one.
Keyboard and focus
2.1.1 Keyboard and 2.1.2 No keyboard trap: every control works with a keyboard and the user can always Tab out of a widget. The classic ferry failures are the calendar (a grid of divs with click handlers), the seat or vehicle deck plan, and the custom dropdown for the route. 2.4.3 Focus order says Tab moves in a sensible sequence; when a dialog opens, focus moves into it, and when it closes, focus returns to the control that opened it. 2.4.7 Focus visible and the new 2.4.11 Focus not obscured require that the focused control is always visibly marked and never hidden under a sticky header or a cookie banner. A thick outline in a colour that reaches 3:1 against its background is the simplest correct answer. 2.4.1 Bypass blocks is the skip link: the first Tab on any page offers "Skip to content", so a keyboard user does not cross the whole menu to reach the search form. 2.5.8 Target size, new at level AA in 2.2, requires 24 by 24 CSS pixels for anything clickable unless targets are spaced apart; a 44-pixel target is what works on a moving deck. 2.5.7 Dragging movements says any drag, such as moving a vehicle onto a deck plan, must also be possible with clicks or keys.
Labels, errors and time
1.3.1 Info and relationships and 3.3.2 Labels or instructions: every field has a visible label tied to it in code. A placeholder is not a label; it disappears when the passenger starts typing and is usually too pale to read. 3.3.1 Error identification and 3.3.3 Error suggestion: when the date of birth is in the wrong format, the message says which field, what is wrong and what format is expected, and it is announced to screen readers and placed next to the field, not only in a red bar at the top. 3.3.4 Error prevention (legal, financial, data): a booking is a financial transaction, so the passenger must be able to review and correct the whole booking before confirming, or reverse it afterwards. A summary page before payment is not a courtesy; it is a conformance requirement. 3.3.7 Redundant entry, new in 2.2: do not ask twice for the same thing in one process. If the contact phone was entered on page one, offer it on page three. 1.3.5 Identify input purpose: the name, email and phone fields carry the autocomplete attribute so the browser fills them. 3.3.8 Accessible authentication: looking up a booking by reference and surname is fine; a CAPTCHA that asks the passenger to transcribe distorted letters is not, unless an alternative exists. 2.2.1 Timing adjustable is the criterion ferry sites break most often: a seat hold that expires silently after ten minutes fails it. The page must warn before expiry and let the passenger extend with one action, or the limit must be long enough (WCAG says twenty hours) to be irrelevant.
Contrast and motion
1.4.3 Contrast (minimum): body text at 4.5:1 against its background, large text (18 point, or 14 point bold) at 3:1. The pale grey on white that designers like for secondary text, around #999 on white, is about 2.8:1 and fails. 1.4.11 Non-text contrast: focus rings, input borders and icons that carry meaning need 3:1. 1.4.1 Use of colour: availability, status and errors carry a word or a symbol as well as a colour. 1.4.4 Resize text to 200 percent and 1.4.10 Reflow at 320 CSS pixels: the page must still work when a passenger zooms to 400 percent on a laptop, which produces a phone layout, with no horizontal scrolling and nothing cut off. 1.4.12 Text spacing: the layout survives wider line height, letter spacing and paragraph spacing, which is exactly what a reading preferences panel applies. 2.3.1 Three flashes: nothing flashes. 2.3.3 Animation from interactions is only level AAA, but respecting the system setting for reduced motion costs one CSS media query and spares passengers with vestibular disorders.
Reading preferences: on top of conformance, never instead of it
Many operators have been sold an accessibility overlay: a script that adds a floating button with contrast toggles and text resizing, and promises compliance. The Overlay Fact Sheet, signed by several hundred accessibility practitioners, explains why the promise is false: an overlay cannot add a missing label, repair a broken focus order or make a div behave as a button, and screen-reader users routinely report that overlays make pages worse. Regulators in Europe and the United States have treated overlay badges as no evidence of conformance.
A reading preferences panel is a different thing if it is understood correctly: a convenience built on a base that already conforms. The base gives structure, keyboard operation, labels and contrast. The panel lets the passenger adjust presentation beyond what the browser offers by default: four text sizes, a high-contrast theme, a dyslexia-friendly typeface, wider line and letter spacing, a reading ruler that follows the pointer, highlighted links, hidden images, a large cursor, reduced motion and read-aloud through the browser's own speech synthesis. None of this is required by WCAG and all of it is used by real people. Atkinson Hyperlegible, the typeface the Braille Institute released in 2019, is a sound default for the low-vision and dyslexia setting: its letterforms are deliberately distinguishable, so b, d, p and q are not mirror images, and it is free to embed.
Supaferry carries such a panel on the product site, the passenger site and the back office. The choices are stored on the device and never sent to the server, which keeps them out of the data protection scope, and they apply as attributes on the page root so the stylesheet does the work and the page's semantics stay untouched. The test of whether a panel is honest is simple: turn it off and run the site with a screen reader. If the site passes without the panel, the panel is a gift. If it only passes with the panel, it does not pass, because the screen-reader user never found the panel.
A preferences panel is the top floor of the building. It is worth nothing without the stairs.
Beyond the website: ticket, counter, phone and gangway
Tickets people can read
A ticket is a document, and documents have their own accessibility rules: clause 10 of EN 301 549 for non-web documents, PDF/UA for tagged PDF. The practical requirements for a ferry ticket:
- Real text. The ticket PDF contains text a screen reader can read and a search can find, not a rendered image. A passenger with a screen reader should hear the voyage, the origin, the destination, the date and time, the class and the fare without help.
- The code in letters. The QR code the boarding desk scans is printed with the same reference beside it in large, unambiguous characters, with no O against 0 and no I against 1. The officer can type it when the scanner fails, the passenger can read it over the phone, and a blind passenger can have it read by a relative.
- Large print. An 18-point version on A4 with the essential facts at the top is a setting, not a separate product. Thermal receipts fade and are small; A4 from a laser printer at the counter is what an elder keeps in an envelope.
- Email with the facts in the body. The message that carries the PDF repeats voyage, date, time, origin, destination and reference in plain text, because many mail apps on old phones do not open attachments and because the email itself may be read aloud.
- SMS for feature phones. A short message with the reference, the date and the departure time is a ticket for a passenger whose phone has no browser, as long as the boarding desk accepts a reference typed in.
- One page per passenger. A family booking produces one page per person, so the person boarding alone has the whole ticket.
The branded tickets Supaferry generates follow this pattern: one A4 page per passenger, the QR code with the reference in letters under it, the same facts repeated in the confirmation email body, and the operator's logo and colour applied as data rather than baked into an image of the ticket.
The counter and the phone are accessible channels
The best accessibility feature of a ferry booking service is a human being with the same system in front of them. On most inter-island routes the agency counter still sells more than half of the tickets, and the phone sells many of the rest. These channels are not a fallback for a failing website; they are part of the accessible service and must be designed as one.
That means three things. First, the counter uses the same booking record as the website, so a booking made by phone, held for the passenger and paid in cash at the counter the next day is the same object, with the same manifest row, the same ticket and the same assistance flag, as a booking made online. Second, the back office itself is accessible, because the agent at the counter may be blind or may work with one hand, and because the Web Accessibility Directive and the laws that transpose it cover the tools a public body gives its staff as well as its public site. Third, the phone procedure is written down: the agent reads the summary back, confirms the spelling of the name, states the fare and the hold expiry, sends an SMS with the reference, and the passenger pays at the counter or at a finance office before the hold expires. A deaf passenger must have a text channel to the same procedure, by SMS, email or a relay service.
Assistance declared once, visible at the gangway
In the European Union, Regulation 1177/2010 on the rights of passengers travelling by sea gives disabled persons and persons with reduced mobility the right to be carried on the same terms as everyone else and the right to free assistance in ports and on board, provided the carrier is notified at least 48 hours before departure. Similar duties exist under Australia's Transport Standards and under the Americans with Disabilities Act. On a small line the regulation is only as good as the moment the information reaches the crew.
The design answer is a special needs field on the passenger record, declared once, at booking, on any channel, and then visible everywhere the passenger is handled: on the manifest for the call where they embark, on the boarding desk row when the ticket is scanned, in the voyage summary the dispatcher reads before departure, and in the count the master uses to brief the crew. The field should be a choice with a free-text note, not free text alone, because a choice can be counted and translated: wheelchair user, cannot climb a ladder, blind or low vision, deaf, travelling with an assistant, medical oxygen, needs a seat near an exit, other. In Supaferry this is one of the operator-configurable passenger questions; when it is filled, the manifest row is highlighted, the voyage page shows a count of passengers needing assistance, and the check-in screen shows the note beside the name as the ticket is scanned, so the officer at the gangway knows before the passenger reaches the top of the ladder.
Two cautions. The field describes an operational need, not a diagnosis, and it is health-related data under GDPR Article 9, so collect the minimum, say what it is for, show it only to the roles that act on it and delete it with the manifest when the retention period ends. And the field is not a substitute for the 48-hour notice: the booking site should state the notice period and the contact for assistance on the same screen, and a booking made inside the notice period should tell the passenger that assistance will be provided where possible.
Procurement: what the law requires and what to ask for
Public operators, and private operators procured by a public body, do not get to decide whether to be accessible. The main instruments, by jurisdiction:
- European Union, public sector. Directive 2016/2102, the Web Accessibility Directive, requires the websites and mobile apps of public sector bodies to meet the harmonised standard EN 301 549, which incorporates WCAG 2.1 AA (a revision to align with 2.2 is in progress), to publish an accessibility statement with a feedback channel, and to accept monitoring by a national body. Directive 2014/24/EU on public procurement, Article 42, requires technical specifications to take accessibility for persons with disabilities into account, except in duly justified cases, and to use the mandatory EU accessibility requirements where they exist.
- European Union, private services. Directive 2019/882, the European Accessibility Act, applies since 28 June 2025 to e-commerce services and to the digital parts of passenger transport services: websites, apps, electronic tickets and ticketing services, and travel information. Urban, suburban and regional transport services are exempt from most of it, but their online ticket shop remains an e-commerce service and is covered. Microenterprises with fewer than ten staff and under two million euro turnover that provide services are exempt.
- Spain. Real Decreto 1112/2018 transposes the Directive, requires the accessibility statement and a responsible accessibility unit in each public body, and uses UNE-EN 301 549. Ley 11/2023 transposes the Accessibility Act. The public procurement law, Ley 9/2017, Article 126, requires technical prescriptions to include accessibility criteria and design for all.
- Italy. Legge 4/2004, the Stanca law, and the AgID guidelines on the accessibility of IT tools require public bodies to publish a dichiarazione di accessibilità on the AgID form each year by 23 September and annual accessibility objectives by 31 March. Article 4 of the law makes public contracts for websites that ignore the accessibility requirements null. Decreto-legge 76/2020 extended the obligations to private companies with turnover above 500 million euro, and Decreto legislativo 82/2022 transposes the Accessibility Act.
- United States. Section 508 of the Rehabilitation Act, as refreshed in 2017, requires federal agencies to procure and use ICT that meets WCAG 2.0 AA. The Department of Justice rule of April 2024 under Title II of the ADA requires state and local governments, including port authorities and public ferry operators, to meet WCAG 2.1 AA by April 2026 for populations of 50,000 and above, or April 2027 for smaller ones. Title III covers private operators as public accommodations.
- Australia. The Disability Discrimination Act 1992 has applied to websites since Maguire v SOCOG in 2000; the Disability Standards for Accessible Public Transport 2002 cover ferries and wharves; the Commonwealth Digital Service Standard points to WCAG 2.2 AA.
- Pacific and donor-funded projects. Most Pacific states have ratified the UN Convention on the Rights of Persons with Disabilities, whose Article 9 covers information and transport, and the Asian Development Bank and the World Bank expect disability inclusion in the projects they finance. A ticketing system bought with donor funds will be asked about accessibility at appraisal.
What a procurement officer should ask for
- A conformance claim against WCAG 2.2 level AA, and for EU buyers against EN 301 549, in the form of an Accessibility Conformance Report that lists every criterion as supported, partially supported or not supported, with remarks.
- An independent audit less than twelve months old, following the WCAG Evaluation Methodology, with the sample of pages tested (search, results, passenger form, payment, confirmation, ticket, booking lookup, back-office check-in), the browsers and assistive technologies used, and the per-criterion result.
- A test matrix with real assistive technology: a screen reader on Windows (NVDA is free), VoiceOver on iOS, TalkBack on Android, keyboard only, 400 percent zoom, and Windows high contrast mode. Automated tools find between a third and a half of failures; the rest need hands.
- An accessibility statement page on the live site, in the required national format, with a feedback channel and a stated response time.
- Coverage of documents: tickets, receipts and the manifests exported for the authority, in tagged PDF with real text.
- Coverage of the back office, because staff are users too, and of the counter and phone procedures, including training.
- A defect clause: known non-conformances listed with dates, new ones fixed within a defined period, and acceptance testing with a panel of disabled users before go-live.
- No reliance on an overlay badge as evidence.
Common failures an audit finds on ferry websites
- A date picker that opens on click and cannot be operated with the keyboard, while the field refuses a typed date.
- A seat or vehicle deck plan that works only by drag.
- Availability shown as green and red tiles with no text.
- Secondary text in light grey at 2.5:1.
- Placeholders used as labels, which vanish on typing.
- Errors listed only at the top of the page, in red, with no link to the field.
- A hold timer that expires with no warning and sends the passenger back to search.
- A CAPTCHA with no alternative on the booking lookup.
- A ticket delivered only as an image or only inside a native app.
- A modal dialog that does not take focus and cannot be closed with Escape.
- A language switch shown as flags with no text.
- An auto-playing hero carousel with no pause control.
- An overlay badge in the footer and nothing fixed underneath.
A checklist
- Skip link first on every page; focus always visible; Tab order follows reading order.
- Every control, including calendar, steppers and deck plans, works with the keyboard alone.
- Labels in code; errors in words, next to the field, announced.
- Review step before payment; hold timer warned and extendable.
- Text at 4.5:1, controls at 3:1, no colour alone; the page works at 400 percent zoom and with text spacing applied.
- No flashing; reduced motion respected.
- Language declared per page; plain words; a second language where the route needs one.
- Ticket as real text with the code in letters; the email body carries the facts; an SMS option exists.
- Counter and phone use the same record; procedures written; a text channel for deaf passengers.
- Special needs declared once, shown on the manifest, at the desk and at the gangway; the 48-hour notice stated.
- Accessibility statement published; feedback channel answered.
- Reading preferences panel on top, never instead.
Worked example: booked by phone, boarded by tender
Teresa is 76 and lives on an outer island where the ship anchors off the reef and passengers go ashore by tender. She has macular degeneration, reads large print with a magnifier, and owns a phone that makes calls. She needs to travel to the main island for a hospital appointment in nine days.
She calls the agency. The agent searches her island to the main island for the next voyage, finds one departing in six days with deck space, and enters her as a passenger: name, date of birth, home island, and in the special needs field the choice "cannot climb a ladder" with the note "needs the boarding chair at the tender". The agent reads the summary back: voyage code, departure day and time at her island, estimated arrival, the deck fare for 42 miles at the tariff's per-mile deck rate, and the hold expiry, which the operator has set at 48 hours before departure for counter payments. The system sends an SMS with the booking reference to her phone. Her nephew pays at the agency counter two days later; the agent enters the receipt number and the booking is confirmed. The agent prints the ticket on A4 at 18 point with the reference in letters under the QR code, and her nephew collects it.
On the morning of the call, the voyage page shows the dispatcher that one passenger embarking at Teresa's island needs assistance. The boarding officer in the tender has the manifest for that call on a tablet, with her row highlighted and the note beside her name. The crew rig the boarding chair before the tender leaves the ship. At the beach the officer types the reference from her ticket, because the QR code is in a plastic sleeve under the midday sun and the scanner cannot read it, and marks her boarded. The master's persons-on-board count after the call includes her, and the manifest exported for the authority carries the assistance flag as a count, not as a diagnosis.
Nothing in that story needed a smartphone, a mouse or good eyesight. It needed a system in which the counter is a first-class channel, the special needs field travels with the booking, the ticket has the code in letters, and the people at the gangway can see what the agent typed. That is what accessible ticketing means in practice, and it is what a tender should ask for.
Questions people ask
- Does WCAG apply to a PDF ticket?
- Yes. WCAG covers documents delivered through the web, and EN 301 549 clause 10 and PDF/UA set the rules for non-web documents. A ticket must contain real text in reading order, with a text alternative for the QR code and the reference printed in letters. An image of a ticket fails even if the website that produced it conforms.
- Our ferry line is regional transport. Is it exempt from the European Accessibility Act?
- Only partly. The Act exempts urban, suburban and regional transport services from its passenger transport provisions except self-service terminals, but an online ticket shop is an e-commerce service and is covered as such since 28 June 2025. A public operator is covered anyway by the Web Accessibility Directive and its national transposition.
- Is an accessibility overlay enough to comply?
- No. An overlay cannot repair missing labels, focus order or keyboard operation, and regulators do not accept its badge as evidence. A reading preferences panel is useful only on top of a site that already meets WCAG 2.2 AA when the panel is switched off.
- How long should the seat hold on the booking page be?
- Long enough to pay, and never silent. Fifteen minutes with a visible countdown in text, an announcement to screen readers before expiry and an Extend button meets WCAG 2.2.1. A counter hold for cash payment should be hours or days, printed as a date and time on the receipt.
- What should the accessibility statement contain?
- The standard claimed and the level, the parts of the service that do not yet conform and why, the date and method of the last evaluation, a feedback channel with a response time, and the national enforcement contact. Spain, Italy and the other EU states publish a mandatory model; the statement must be linked from every page.
- How do we test with no budget for consultants?
- Unplug the mouse and complete a booking with Tab, Enter and the arrow keys. Install NVDA, which is free, and book again with the screen off. Zoom the browser to 400 percent. Turn on Windows high contrast. Print a ticket and read it with a magnifier. These four tests find most of what an auditor would find; the audit then confirms it.
- Can a passenger without a smartphone use an electronic ticket?
- Yes, if the system treats the booking reference as the ticket. The reference goes out by SMS and is printed in letters on the paper ticket, and the boarding desk accepts a typed reference as well as a scanned code. The QR code is a convenience for the officer, not a condition of travel.