World Port Control
What does and does not work accessibly in this game, checked against what Apple, Google and WCAG 2.2 AA ask for.
Summary
This game does not fully meet WCAG 2.2 AA yet.
Apple features with Yes: VoiceOver, Voice Control, Larger Text, Dark Interface, Differentiate Without Color Alone, Sufficient Contrast, Reduced Motion.
WCAG 2.2 AA, 55 criteria: 26 meets, 13 partly, 0 does not meet, 0 not tested, 16 not applicable.
What does not work yet
- Collisions happen in real time: even with No time pressure, ships keep sailing while nothing is selected. Pausing is always possible.
- With very large text, the HUD on a narrow phone shows only ships and warnings; score, anchors and tide are then left out.
- A risky route and the state of a bridge show mainly through colour on the map; the bridge state is read aloud.
- The 2× and ? buttons are called Faster and the guide title for assistive technology.
- The Android version has not been released yet.
How to set it up
- Open Accessibility with the button at the bottom of the start screen, or via the card on first launch.
- Colour blindness: Standard, Red-green or Blue-yellow, always with symbols.
- Low vision: Larger symbols and lines, High contrast and Dark playing field (Auto, On, Off).
- Light and motion: Reduce flashing, Reduce motion (Auto, On, Off) and water animation.
- Pace and controls: Relaxed pace, No time pressure (Auto, On, Off; Auto follows VoiceOver, TalkBack or switch control) and extra vibration. With Relaxed pace or No time pressure, scores do not count for the leaderboards.
- No need to drag: tap a ship and then its quay, or a helper boat and then the ship.
- Auto follows your device. Sound and vibration are also buttons on the start screen, and sound is also in the pause menu.
What we checked
Apple asks that all common tasks can be done with a feature. These are the common tasks of this game.
- First launch: start logo, Accessibility card, playable tour or skip
- Settings: Accessibility, sound, vibration, language
- Choosing a harbour and level, starting Endless or the Daily harbour
- Core loop: dragging a route from ship to quay, or tapping the ship and then the quay; waiting; anchoring with a double-tap or the Anchor action
- Operating helper boats, bridges and smugglers
- Pausing, opening the guide, viewing the result, replaying or carrying on
- Opening the leaderboards (optional; there is no account and no purchase)
Apple: features on the App Store
A feature only gets Yes if you can do all common tasks with it. iPhone and iPad.
- VoiceOver Yes
Menus, buttons and counters are read aloud. On the playing field, ships, quays, helper boats, bridges and smugglers are buttons with a name and state: select a ship and then a quay, or use the To quay, To sea and Anchor actions. Notices are read aloud. With VoiceOver, No time pressure turns on by itself, so time stands still while a ship is selected.
- Voice Control Yes
Every ship and quay has its own name, such as Fishing boat 3 and Quay 2. Say 'tap Fishing boat 3' and then 'tap Quay 2' to send the ship; no dragging needed. Menu buttons work by their name.
- Larger Text Yes
Menus, cards and the HUD grow up to the largest accessibility size; if the counters no longer fit side by side, they stack. Text on the map (badges, clocks, points) grows up to 2 times.
- Dark Interface Yes
Menus, cards and the HUD are always dark. Dark playing field (Auto follows the device's dark mode) also makes water, land and quays dark, also by day.
- Differentiate Without Color Alone Yes
Every ship and its quay always carry the same symbol, in every colour mode. Limitation: a risky route and the state of a bridge show mainly through colour on the map; VoiceOver does read out the bridge state.
- Sufficient Contrast Yes
Text on the cards reaches at least 4.5:1: legend text is light and the red reason at game over is a lighter red. Rings and routes on the map have a dark edge and symbols use white or dark, whichever gives the most contrast. High contrast strengthens this further.
- Reduced Motion Yes
Ripples, pulsing zones and rotating lighthouses stop, notices and the tour bar fade instead of sliding, and no rain falls during storms and monsoons: a still dark layer shows that it is raining.
- Captions Not applicable
No video and no spoken content. In App Store Connect: do not tick.
- Audio Descriptions Not applicable
No video. In App Store Connect: do not tick.
Google: Android
Google asks, among other things, for descriptions for TalkBack, touch targets of at least 48 dp, enough contrast and text that scales.
This Android version has not been released yet. We checked the code.
- TalkBack Yes
Menus, counters and notices are read aloud. On the playing field, ships, quays, helper boats, bridges and smugglers are buttons with a name and state, with the To quay, To sea and Anchor actions. With TalkBack, No time pressure turns on by itself.
- Switch Access Yes
Ships and quays are ordinary buttons: select a ship and then a quay. With Switch Access, No time pressure turns on by itself.
- Voice Access Yes
Ships and quays have their own name, such as Fishing boat 3 and Quay 2: tap them by name to send a ship. Limitation: the 2× and ? buttons are called Faster and the guide title for assistive technology.
- System font size up to 200% Yes
Menus and the HUD follow the font size (the counters stack if they don't fit), and text on the map grows up to 2 times.
- Target size of at least 48dp Yes
Buttons, choices and the page dots in the guide are at least 48dp.
- Contrast Yes
The same colours as on iOS: text reaches at least 4.5:1, rings and routes on the map have a dark edge. You can also turn on High contrast yourself.
- Remove animations Yes
The setting is followed: decorative motion stops and no rain falls during storms and monsoons.
- Not relying on colour alone Yes
Ship and quay carry the same symbol. Limitation: a risky route and the bridge state show mainly through colour on the map.
WCAG 2.2 AA
WCAG was written for the web. For apps we follow the guidance in WCAG2ICT. Level AA has 55 criteria.
1. Perceivable
- 1.1.1 Non-text content Level A Partly
Buttons, counters, the guide pictures and the playing field (ships, quays, helper boats, bridges) have text. Harbour previews and some icons have no label of their own.
- 1.2.1 Audio-only and video-only (prerecorded) Level A Meets
No video. The silent drawings in the guide have a description and text beneath them.
- 1.2.2 Captions (prerecorded) Level A Not applicable
Does not exist in this game.
- 1.2.3 Audio description or media alternative (prerecorded) Level A Not applicable
Does not exist in this game.
- 1.2.4 Captions (live) Level AA Not applicable
Does not exist in this game.
- 1.2.5 Audio description (prerecorded) Level AA Not applicable
Does not exist in this game.
- 1.3.1 Info and relationships Level A Partly
On iOS only the headings in Accessibility, the guide and the intro card are marked as headings. Titles on start, pause and the harbours are not. On Android more titles are headings.
- 1.3.2 Meaningful sequence Level A Meets
The order in the code is the logical reading order on every screen.
- 1.3.3 Sensory characteristics Level A Partly
Some instructions rely on colour or position, such as 'the quay in the same colour', although the symbol is always shown too.
- 1.3.4 Orientation Level AA Meets
Portrait and landscape both work on iPhone, iPad and Android; the map rotates with the device.
- 1.3.5 Identify input purpose Level AA Not applicable
Does not exist in this game.
- 1.4.1 Use of colour Level A Partly
Ship and quay always have a symbol. A risky route and the bridge state are shown mainly with colour.
- 1.4.2 Audio control Level A Meets
Only short sounds of at most 1.4 seconds, and a button to turn sound off.
- 1.4.3 Contrast (minimum) Level AA Meets
Text on the cards reaches at least 4.5:1, also in the colour modes: legend text is light and the red reason at game over is a lighter red.
- 1.4.4 Resize text Level AA Meets
Menus and the HUD scale up to the largest accessibility size; text on the map grows up to 2 times.
- 1.4.5 Images of text Level AA Meets
Text is real text; only the logo is an image.
- 1.4.10 Reflow Level AA Partly
Menus scroll on small screens. There the HUD leaves out the score, anchors, tide and the ? button; these are not always available elsewhere.
- 1.4.11 Non-text contrast Level AA Meets
Waiting and warning rings and the white route have a dark edge, also with High contrast, and symbols on quays and ships use white or dark for the most contrast.
- 1.4.12 Text spacing Level AA Not applicable
Native app: players cannot set letter spacing.
- 1.4.13 Content on hover or focus Level AA Not applicable
No content that appears on hover or focus.
2. Operable
- 2.1.1 Keyboard Level A Meets
Everything works without dragging: with Full Keyboard Access on iOS and a keyboard or D-pad on Android you select a ship and then a quay, helper boat, bridge or smuggler.
- 2.1.2 No keyboard trap Level A Meets
Focus can always move away again; there are no custom keys that trap it.
- 2.1.4 Character key shortcuts Level A Not applicable
No keyboard shortcuts.
- 2.2.1 Timing adjustable Level A Meets
No time pressure turns off the waiting warnings and the ferry deadlines, and stops time while a ship or helper boat is selected. Pausing is always possible. Relaxed pace slows ships to 0.6 times and doubles the waiting time, also in the tour.
- 2.2.2 Pause, stop, hide Level A Partly
The game pauses with the button and water animation can be turned off. You cannot pause the animations in the guide and the map behind the menus without Reduce motion.
- 2.3.1 Three flashes or below threshold Level A Meets
The fastest blinking is about 2.8 times per second (beacon), on small areas, and the game has no lightning. Reduce flashing turns blinking off.
- 2.4.1 Bypass blocks Level A Not applicable
No repeated blocks within screens.
- 2.4.2 Page titled Level A Meets
The app and every screen have a clear title.
- 2.4.3 Focus order Level A Partly
Open cards are not marked as modal, so VoiceOver and TalkBack can reach the HUD or the menu behind a card.
- 2.4.4 Link purpose (in context) Level A Meets
Buttons have their own text or label.
- 2.4.5 Multiple ways Level AA Not applicable
Not a collection of web pages. The guide can be opened from several places.
- 2.4.6 Headings and labels Level AA Meets
Titles and labels describe their purpose.
- 2.4.7 Focus visible Level AA Meets
On iOS the system shows the focus ring; on Android the custom buttons have a visible focus ring.
- 2.4.11 Focus not obscured (minimum) Level AA Partly
Focus usually stays in view. A ship sailing under the HUD can have its focus ring partly behind the HUD.
- 2.5.1 Pointer gestures Level A Meets
The guide has buttons next to swiping, and you can also choose a route with two taps: ship and then quay.
- 2.5.2 Pointer cancellation Level A Partly
Routes and buttons work on release. Opening bridges and tapping smugglers happens as soon as the finger touches down.
- 2.5.3 Label in name Level A Partly
Most buttons are fine. The visible '2×' and '?' are called 'Faster' and the guide title for assistive technology.
- 2.5.4 Motion actuation Level A Not applicable
No control by moving the device.
- 2.5.7 Dragging movements Level AA Meets
Dragging is not needed: tap a ship and then its quay, or a helper boat and then the ship.
- 2.5.8 Target size (minimum) Level AA Meets
Buttons are at least 24 points; ships have a grab zone of at least 52 points.
3. Understandable
- 3.1.1 Language of page Level A Partly
The language follows the device. If you choose a language in the app itself, it is not passed on to the screen reader.
- 3.1.2 Language of parts Level AA Partly
Language names are in their own language, but without a language tag; a screen reader may pronounce them in the app's language.
- 3.2.1 On focus Level A Meets
Focus alone changes nothing.
- 3.2.2 On input Level A Meets
Settings change nothing unexpected; choosing a language changes the whole app, as requested.
- 3.2.3 Consistent navigation Level AA Meets
The back button and buttons are in the same place on every screen.
- 3.2.4 Consistent identification Level AA Meets
The same functions use the same components and names.
- 3.2.6 Consistent help Level A Partly
The guide is on the start screen and in pause, but the ? button drops out of the HUD on a narrow phone.
- 3.3.1 Error identification Level A Not applicable
No input that can be wrong.
- 3.3.2 Labels or instructions Level A Meets
All settings have a label and, where needed, an explanation.
- 3.3.3 Error suggestion Level AA Not applicable
Does not exist in this game.
- 3.3.4 Error prevention (legal, financial, data) Level AA Not applicable
No purchases, accounts or legal actions.
- 3.3.7 Redundant entry Level A Not applicable
Does not exist in this game.
- 3.3.8 Accessible authentication (minimum) Level AA Not applicable
The app has no sign-in of its own; Game Center and Play Games are optional and provided by the system.
4. Robust
- 4.1.2 Name, role, value Level A Meets
Menu items and the playing field (ships, quays, helper boats, bridges, smugglers) have a name, role and state.
- 4.1.3 Status messages Level AA Meets
Notices (warnings, storm, night) are announced to VoiceOver and TalkBack and stay for at least 5 seconds.
How we checked this
We reviewed the source code of the game on the date above. This is our own review, not an audit by an independent party, and we have not yet tested this on devices with assistive technology. That is why it says "Not tested" where the code alone gives no answer.
We update this page whenever the accessibility of the game changes.
Running into a problem, or is something wrong here? Email us at hello@studionolu.com.