A controller appearing in your device settings confirms a connection, but does not prove that a browser game supports it. Check the game's own control instructions before troubleshooting buttons.
Three separate links must work
The device must recognize the controller, the browser must expose its input, and the game must implement controls for it. MDN describes how the Gamepad API lets applications read buttons and axes. Some browsers require interaction with a controller before exposing it to a page. A keyboard-only game will not automatically gain controller support because the browser can detect a gamepad.
Try the steps
- Connect the controller and check that the operating system recognizes it.
- Open the game, activate its player, and press a controller button if its instructions advertise gamepad support.
- Compare a documented keyboard or touch action. Record which inputs work before changing settings.
Do the linked games guarantee controller support?
No. They are games to explore, not a compatibility list. If a game documents controller support but ignores it, report the controller model, connection type, browser and failed action. Reinstalling the browser is not the first useful test.
