Accessibility

Our commitment

We want everyone to be able to use our website and play our games. We aim for this website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and we keep improving our games’ accessibility with each update.

This website

You should be able to:

• use every page with a keyboard alone, with a visible focus outline and a “Skip to content” link at the top of each page;
• use a screen reader such as VoiceOver, with clearly labelled links, buttons, menus and form fields, and headings in a logical order;
• zoom text up to 200% and use the site on a phone without content being cut off or scrolling sideways;
• turn off animation by switching on Reduce Motion in your device settings;
• read text with strong contrast against its background;
• see form errors explained in words, not only by colour.

Known limitations

• The landscape artwork behind headings and on news cards is decorative, so screen readers skip it. It doesn’t contain information you would miss.
• Links to the App Store take you to Apple’s website, which has its own accessibility features.

Accessibility in our games

We build accessibility options into our games and add more with updates. Current features include:

• Echo Tide: colour-blind palettes, a one-hand mode and adjustable timing windows.
• Driftline and Hollow Peak: full support for MFi, Xbox and PlayStation controllers, with rebindable buttons in Hollow Peak.
• Hollow Peak: suspend and resume at any point, so you can play at your own pace.

If something in one of our games is hard for you to use, we would like to hear about it.

Feedback and help

If you find a problem with this website or one of our games, or need information in a different format, email support@northadapt.com or use the form on our support page. Tell us the page or game, what you were trying to do, and the device and assistive technology you use. We aim to reply within two working days.

How we check

We review this website against WCAG 2.2 AA with automated checks and manual keyboard testing whenever we make significant changes. This statement was last reviewed on 29 September 2026.