Live scorecards and audio commentary

Follow cricket and football with live scorecards and spoken match updates.

Follow cricket and football with live scorecards, timelines, squads, insights, and optional device-local audio commentary for supported match events.

Cricket and footballOpt-in audioDevice-local playbackNo microphone required

Sport-specific live scorecards

Cricket viewers get batting, bowling, commentary, extras, and fall-of-wicket detail, while football viewers get scores, timelines, moments, insights, and squads.

Automatic event-by-event speech

Supported match events are assembled into spoken announcements from a bundled English audio pack as the canonical score changes.

Opt-in on each device

Commentary starts only after the viewer enables it and the browser allows audio playback, with a clear control to pause or turn it off.

Private device-local playback

The prerecorded clips play in the viewer's browser. Commentary playback does not require microphone access or send names to an external speech service.

Readable names and full score context

Player and team names remain visible in the scorecard. Arbitrary names are not dynamically spoken by the bundled commentary pack.

One source for every viewer

Text commentary, spoken updates, scorecards, broadcast graphics, and fantasy calculations all follow the same accepted match events.

Workflow

A proper process, not another spreadsheet.

01

Open public scorecard

02

Review the live score

03

Enable audio commentary

04

Browser prepares playback

05

New events are announced

06

Pause or turn audio off

FAQ

Is the audio commentary a human radio stream?

No. It is automatic event-by-event commentary assembled from bundled prerecorded clips for supported cricket and football events.

Are player and team names spoken?

Names remain visible in the scorecard, but arbitrary names are not dynamically narrated by the bundled audio pack.

Does commentary use the microphone?

No. Playback is device-local and does not require microphone access.

Why must a viewer tap to enable audio?

Modern browsers require a user gesture before starting sound. The scorecard keeps commentary off until the viewer explicitly enables it.