Why some crosswalk buttons seem to do nothing
At many busy intersections, the traffic signal follows a preset schedule, cycling through directions whether or not anyone presses the pedestrian button. If the walk phase is already guaranteed, pressing the button cannot make it arrive sooner. The button may still be there because the signal equipment was built for locations where a pedestrian request matters—or because replacing every button would be costly and disruptive.
That can make a working button look like a fake. A button may register a request but have no visible effect if the crossing is already included in the next scheduled cycle. At some intersections, it only changes timing under particular conditions, such as quieter hours. The result is that people may press repeatedly without seeing any difference.
When a press changes the signal
At other crossings, the button sends a request to the signal controller. Depending on the intersection’s timing plan, that request can add a walk phase, bring it sooner, or ensure enough time for pedestrians to cross. Signals must balance pedestrian access with traffic flow, so a request does not necessarily mean an immediate walk sign.
Some buttons also provide an audible or tactile indication for people who are blind or have low vision. That function is separate from whether pressing the button changes when the walk signal appears. A button can serve an accessibility purpose even when it does not control the timing. The practical clue is the crossing itself: if the walk signal appears reliably without a press, the cycle may already be automatic.
