demo · v151

Accessibility Impact

A simulator showing how auto-punctuation changes the experience for users dictating with motor impairments, voice-typing in second languages, and using screen readers. Toggle the policy and read the same dictated sentence aloud through the browser's speech synth.

Synth-backed simulator. Uses speechSynthesis to read each output panel. Auto-punctuation changes both the visible text and the prosody of the read-back, illustrating why the property matters for dictation and assistive workflows.

scenario 1 — long-form email dictation

"hi mark thanks for the update i think the deck looks great can you swap slide 4 for the v2 chart we discussed friday let me know if you need anything else"

without auto-punctuation

hi mark thanks for the update i think the deck looks great can you swap slide 4 for the v2 chart we discussed friday let me know if you need anything else

with auto-punctuation

Hi Mark, thanks for the update. I think the deck looks great. Can you swap slide 4 for the v2 chart we discussed Friday? Let me know if you need anything else.
screen-reader prosody
monotone vs natural rises and falls at clause boundaries
manual edits required
~12 (left)
0 (right)
assistive output quality
left is hard to parse audibly for an answering screen reader; right is intelligible at first pass

scenario 2 — clinical note dictation

"patient reports intermittent chest pain over the past two weeks pain is left-sided and described as squeezing no associated shortness of breath ekg shows no acute changes will schedule stress test next week"

without auto-punctuation

patient reports intermittent chest pain over the past two weeks pain is left-sided and described as squeezing no associated shortness of breath ekg shows no acute changes will schedule stress test next week

with auto-punctuation

Patient reports intermittent chest pain over the past two weeks. Pain is left-sided and described as squeezing. No associated shortness of breath. EKG shows no acute changes. Will schedule stress test next week.
regulatory record quality
left rejected by most EHR systems
sentence boundaries
readable list of findings vs single 35-word run-on

scenario 3 — voice command (counter-example)

"play playlist evening jazz"

without auto-punctuation (RIGHT for commands)

play playlist evening jazz

with auto-punctuation (corrupts the match)

Play playlist: Evening Jazz.
command matcher
"play playlist evening jazz" → matches
command matcher (right)
trailing "." breaks startsWith / exact-match logic
guidance
disable unspokenPunctuation on the voice-command code path

see also

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗