What to test on an accessibility game controller

An accessibility game controller may use larger buttons, switches, a one-handed layout, or a mix of different inputs. Before relying on it in a game, check that the controls you use are recognized and respond consistently.

The Gamepad Test checks buttons, sticks, triggers, and vibration in your browser. It can help you tell whether an input reaches the computer, though it cannot decide whether a control is comfortable or easy for a particular player to use.

Test the controls you rely on

1. Open the Gamepad Test and connect or turn on the controller. Keep the test page active. If the controller does not appear right away, press one of its controls and wait a moment.
2. Press each button, switch, or accessible input you plan to use. Test them individually, then try combinations that matter in your game, such as holding one control while pressing another.
3. Move each stick slowly in every direction, then let it go. Watch whether its movement is detected across its range and whether it settles back near the center.
4. Press each trigger gradually, hold it briefly, then release it. Repeat several times to see if the response starts and stops reliably.
5. Run the vibration check if vibration is available and useful to you. If the controller has several vibration motors, note which sides you can feel and whether the result suits your needs.
6. If you use a different connection, profile, or controller layout for another game, repeat the checks in that setup. A controller can report differently after changing modes or reconnecting.

Test the controls that matter to the player, rather than assuming every button needs to be used. For example, a player who uses a switch interface may care most about those switches and their mapped actions, while a player using a stick may want to check its full movement and return to center.

What the result means

The controls register consistently

The browser is receiving those inputs from the controller. That is a good sign, but it does not prove that a specific game will accept them. The game may use a different layout, ignore an input type, or need its own button mapping.

One button or switch does not register

The input may not be reaching the computer, or the controller may be using a mode the browser does not recognize as a gamepad. Check the connection and controller mode, then try another port or device. If other controls work but the same physical input fails repeatedly, the button, switch, or its connection may be faulty.

A stick does not move smoothly or return to center

Check whether the movement is repeatable, not just a single small offset. A small resting movement can be a dead-zone or calibration issue, while jumps, gaps, or movement that continues after you release the stick may point to a setting or a worn control. The game may need a larger dead zone, which is the small range around center where stick movement is ignored.

A trigger responds only near the end of its travel

Some games treat a trigger as a simple on or off button, while others use its gradual range. If the test detects a press but the game does not respond as expected, check the game's trigger settings and mapping. If the trigger fails at the same point in repeated tests, the controller may need service.

Vibration is absent or feels uneven

Not every controller, connection type, browser, or device supports vibration through a web page. A missing test response alone does not prove that the motors are broken. Check whether vibration is enabled in the game and whether that controller model supports it over the connection you are using.

How to fix an input problem

1. Check the controller's connection and mode. Charge it, reconnect its cable, or pair it again. If it has a mode switch, select the mode intended for your computer or device.
2. Try another port or connection. Connect it directly to the computer instead of through a hub, or compare wired and wireless use if both are supported. This helps separate a controller fault from a weak cable or wireless link.
3. Check whether the computer sees it. In Windows 11, open Settings › Bluetooth & devices › Devices to check the connection. For input details, open Control Panel › Hardware and Sound › Devices and Printers, right-click the controller, choose Game controller settings, then open its properties. On macOS, check System Settings › Game Controllers if that section is available and the controller appears there.
4. Review the game's mapping. In the game, look under its Controls or Accessibility settings for remapping, input selection, stick sensitivity, and trigger behavior. Menu names differ by game. Confirm that the action is assigned to the button, switch, or stick you actually use.
5. Check controller options for the game. Some games offer a controller profile, dead-zone setting, or separate accessibility options. Change one setting at a time, then retest the same input so you can identify what helped.
6. Restart the game and reconnect the controller. Some games only detect a controller when they start, or do not update their input list after a controller reconnects.

For broader setup ideas, see Accessible gaming controls: what to set up.

When the controller may be faulty

If the same button, switch, stick, or trigger fails in the browser test and in more than one game, connect the controller to another compatible device if you can. A failure that follows the controller is stronger evidence of a hardware problem than one that appears in a single game. Check the warranty or ask the manufacturer about repair or replacement before opening the controller, especially if it is adapted or customized.

What a browser test cannot judge

The test checks whether the browser receives gamepad inputs. It does not measure how much force a button needs, whether the layout is reachable, whether a switch is comfortable to hold, or whether a particular player can use the controls without fatigue. Those checks need to happen in the player's real setup, using the games and input methods they plan to use.

Use the test results to identify which inputs reach the computer, then make final adjustments in the game and controller setup the player actually uses.