Accessibility
What works today, and what does not. Both lists are meant to be read.
Novus Striker is a browser game, so accessibility here has two halves that behave very differently: the site around the game, which is ordinary HTML and can be made to work well, and the game itself, which is a Unity WebGL canvas and has real limits. We would rather name those limits than let you find them.
What works today
Full parity across three input schemes
Every action — move, dash, pass, charged shot, challenge, switch, Power Strike, pause — is on keyboard and mouse, on a controller, and on touch. No move is locked to one device.
Touch controls you can resize and fade
The in-game Settings menu turns touch controls Auto, On or Off, and adjusts their scale and opacity, so the pads can be made larger or moved out of the way.
Camera shake can be turned down
Camera shake is a setting, not a fixture. If motion is a problem, turn it off before kick-off.
No account, no timer, no purchase
Nothing to sign up for, nothing to remember, no daily login and nothing to buy. You can stop mid-match and close the tab with nothing lost but that match.
Failures say what happened
If the game cannot start — an unsupported browser, a truncated download, a device that ran out of memory — the page says so, in words, with a reload and a cache-clear to try. It does not sit on a frozen progress bar.
A light theme and a dark one
Both ship, and the switch is in the header on every page and at every width. The choice is remembered and applied on the server, so a returning visitor never gets a flash of the theme they did not pick.
A keyboard path through the site
Every page starts with a skip link, focus is visible, headings are real headings, and the game canvas is reachable by tab.
Nothing loads itself
No autoplaying video, no interstitials, and no third-party embed until you ask for it — the map on the feedback page stays behind a button, and analytics stay off until you accept cookies.
Known gaps, stated plainly
None of these are secrets, and none of them are fixed by an apology. They are here so you can decide whether the game is playable for you before you spend a download on it.
The game itself has one look
The site has a light and a dark theme, switchable from the header. The game inside the canvas does not — it renders one way whichever theme the page is in.
Controls cannot be remapped in-game
The bindings on the features page are the ones the game ships with. Remappable controls are on the list; until they land, an operating-system or controller-level remapper is the reliable route.
No colourblind-safe team palettes
Teams are told apart by colour, and there is no alternative palette or pattern yet. This is a known gap and a planned one.
No reduced-effects mode
Bloom, match effects and pitch dressing are always on. Camera shake is the only motion setting today.
The game itself is a canvas
A Unity WebGL build draws into a single canvas element. A screen reader cannot navigate inside it, its text does not grow with your browser's text-size setting, and browser zoom scales the whole picture rather than reflowing it. That is a property of how the game is built, not an oversight we can fix with markup.
WebGL 2 is required
Devices and browsers without WebGL 2 cannot run the game at all. The page detects this before downloading anything and tells you, rather than leaving you waiting.
Standards
We aim at WCAG 2.2 level AA for the site pages and we are not there on colour: an automated scan still finds contrast failures in the small, low-emphasis text on several pages, and those are a real defect rather than a passing grade. We do not claim conformance for the game canvas, and we would not be able to substantiate it if we did.
This page is a statement of where things actually stand, reviewed when the site changes. It is not a legal accessibility conformance report.
Tell us what you need
If something on this page blocks you, that is worth an email — it moves the item up the list far more reliably than our guessing does. Write to striker@novusstreamsolutions.com or use the feedback page. Telling us your browser, your device and your input method makes it much easier to reproduce.