Skip to content

who it’s for

verified July 2026

Gandr for accessibility teams.

Accessibility is where a meter does its quietest damage. Every affordance is extra characters — the longer image description, the confirmation read back, the error explained rather than announced — and each one is a small saving that adds up to a product someone cannot use.

01

Where the meter edits the experience

The pressure is always toward saying less, and it never arrives as a decision anybody would defend out loud. It arrives as a prompt that says be concise, applied to the text a screen-reader user depends on.

On a seat the extra sentence costs nothing, so the question returns to what a person actually needs to hear.

02

What matters technically

  • Spell tags read codes and reference numbers character by character — the difference between a usable read-back and a guess.
  • A low temperature holds a steady, predictable delivery, which is what a voice someone listens to all day should do.
  • Break tags let structure be heard: a real beat between a heading and its content.
  • 24 kHz mono by default, so the audio is full-rate rather than the compressed telephony band.

03

Notes — an engineer's checklist

01Is this a screen reader?

No — it is the synthesis layer a screen reader or an application calls. Navigation, semantics and focus handling stay in your product or in the assistive technology someone already uses.

02What sample rate does audio come back at?

24 kHz mono PCM by default. Set output_sample_rate if your playback path wants something else.

See also — related sheets

A key and one seat to size it on, before anyone talks about a fleet.

Request access for your stack