Accessibility

We want Nomekop to be usable by everyone — however you browse, whatever you use. Here's where we're at, in plain English. No jargon, promise.

What we aim for

We're aiming to meet WCAG 2.2 level AA— the accessibility standard most of the web works towards. We're most of the way there, and we keep chipping away at the bits that aren't quite right yet.

Settings that help

Nomekop has a retro Game Boy look, but you don't have to keep it that way. Tap the settings button (the cog, top-right) and you can:

  • Switch to the High Contrast palette — the easiest-to-read colours, if the themed ones are hard on your eyes.
  • Swap the pixel font for a plain mono or sans-serif one that's easier to read.
  • Make the text bigger — several sizes, and the whole site also zooms normally in your browser.
  • Turn on reduced motion to calm the animations (we also follow your device's “reduce motion” setting automatically).
  • Mute the sound — nothing plays until you ask it to anyway.

What already works well

A few things we've put real care into:

  • Keyboard friendly— you can reach and use everything with the Tab key, and there's a clear outline showing where you are. A “skip to content” link is the first thing you hit.
  • Screen-reader friendly — buttons, toggles and menus announce what they are and their state, card pictures have descriptions, and every page has a clear heading structure.
  • Respects your preferences — reduced motion, text zoom and your light or dark setting all carry through.

What we're still working on

We'd rather be honest than oversell it. A few things aren't perfect yet:

  • Some of the retro colour themes have lower text contrastthan we'd like. If anything's hard to read, the High Contrast palette (or a plainer font and bigger text) in settings fixes it.
  • A few labels use a small pixel font. Switching the font in settings makes those much clearer.
  • We're polishing how forms (like the report form) announce errors to screen readers.

We test with automated accessibility checks and keyboard run-throughs as part of our normal work, so this list keeps getting shorter.

Found something hard to use?

Please tell us — it genuinely helps, and we read every message. You can report a problem with the form or email [email protected]. Let us know what you were trying to do and what got in the way, and we'll sort it.

Last reviewed: June 2026.