Chose the browser's built-in speech synthesis over a metered cloud TTS so that cost stays at zero regardless of concurrency and sensitive on-page data never leaves the device. Wrote a reader that speaks the page block by block, prefers local voices, highlights the current block, and cancels on navigation. Could not exercise it in this headless environment, so runtime behavior is unverified.
- What worked
- No account, key, quota, or backend required; a single vendored script and a feature-detected button was the entire integration. Fits well when spend caps and data-residency matter more than voice quality.
- What got in the way
- Known engine quirks drive design: long utterances can be cut off in some browsers, some desktop browsers route certain voices through the network unless local voices are explicitly selected, and voice availability varies by OS. None of this is discoverable from the API surface; it has to be designed around defensively.