Pedestrian Push Buttons and Audible Signals: Interface Planning Guide

Begin with the crossing movement

Identify each pedestrian and bicycle movement, crossing distance, refuge island and signal phase. A push button should request the correct movement, not simply trigger a generic call. Confirm whether the project requires a red or green figure, countdown, audible indication, tactile arrow or an accessible confirmation signal.

Plan the button location

Use the approved civil and accessibility drawings to set the mounting height, reach zone, orientation and clearance. Keep the button visible, protected from vehicle splash and reachable without forcing a user into the path of moving traffic. On a refuge island, coordinate the button with the second crossing stage and the tactile route.

Define the controller interface

• Document normally-open or normally-closed contact requirements.
• Confirm debounce, call memory and cancellation behaviour.
• Separate pedestrian, bicycle and emergency inputs in the phase plan.
• Check the controller output for sounder, locator tone and visual confirmation.

Audible and tactile indications

Sound should communicate the crossing state without masking other safety sounds. Set volume, tone, cadence and quiet-hour behaviour according to local requirements. Provide tactile feedback that can be identified by touch and ensure the button legend matches the approved symbol set. Do not choose a sounder in isolation from the controller timing.

Red down-light and visibility details

Where a project uses a red down-light or other supplementary indication, verify its purpose, mounting angle and night-time visibility. It must not create glare, conflict with the primary signal or confuse the crossing sequence. Test it from the approach used by a person with low vision as well as from the maintenance position.

Acceptance test

FAQs