The Read Highlighted Text (RHT) Player is the GSpeech listen mode for a selection, not for the whole article. Highlight a sentence or paragraph; the player reads that span. It is the current form of Listen to Selected Text, which GSpeech shipped in 2012.
This page is only about RHT: views, templates, translation on a selection, and how to publish the widget. For a full-article bar see the other player types. Setup on WordPress: how to add text-to-speech. Product overview: website TTS.
What the Read Highlighted Text Player does
A Full Page player narrates the isolated article. RHT waits until the visitor marks text. That is useful on docs, long posts, and product specs when nobody wants the whole page spoken - only the bit they just pointed at.
RHT is not a screen reader. Assistive tech stays under the visitor’s OS. RHT is an on-page GSpeech widget: Cloud Processing, No Server Load, Unified AI Voice Engine on commercial plans, No API Keys Required.
Any passage on a published page can become audio without a dedicated player stacked on every heading.
The same idea, now with 16+ templates, three views, and Real-Time Audio Translation on the selection in commercial plans.
View 1, View 2, and View 3
RHT ships with 16+ built-in templates. Views change how much UI is open by default:
- View 1 - a compact popup circle. Extra controls sit under the options tab.
- View 2 - language and text panels are open so the visitor can follow the spoken span.
- View 3 - the same expanded panels, tuned for translation on the selection. Commercial Real-Time Audio Translation can speak the marked text in another language without a sitewide language switch.
How to enable RHT in the Cloud Console
- Connect the site (WordPress: GSpeech → Cloud Console, One-Click Activation). Other platforms use the embed from the same console.
- Open Widgets → RHT Player. Set Status to Published.
- Pick a template and view. View 2 and View 3 are the advanced layouts with translation and text panels.
- Keep Intelligent Content Isolation on the rest of the site so a Full Page player, if you also use one, still skips menus. RHT only speaks what the visitor highlighted.
widget: "Read Highlighted Text (RHT) Player"
views: "1 compact, 2 panels, 3 translate"
path: "Cloud Console → Widgets → RHT"
keys: "No API Keys Required"More screenshots: GSpeech WordPress TTS. Live layouts: demos.
Try it on this page
Select any paragraph in this article. If RHT is published on gspeech.io, the player should appear on the selection. That is the whole product demo: no extra install on your side for this URL.
For visitors with low vision or reading fatigue, RHT is a listen shortcut on the exact block they care about. It does not replace a screen reader, and it does not claim that audio alone is WCAG compliance. It is one more way to hear the words already on the page.
Read Highlighted Text Player FAQ
Short answers for the selection player only.
-
What is the GSpeech Read Highlighted Text (RHT) Player?
RHT plays the text the visitor highlights. It grew out of Listen to Selected Text (2012). Full Page, Button, and Circle players narrate a larger isolated block; RHT is for a marked span.
-
What is the difference between View 1, View 2, and View 3?
View 1 is a compact circle with extra controls in options. View 2 and View 3 open language and text panels. View 3 is the layout built around translating the selection. Template colors (including Red) are independent of the view.
-
Can RHT translate a highlighted sentence?
On commercial plans, Real-Time Audio Translation can speak the selection in another supported language. You do not have to switch the whole site language first.
-
Do I need API keys for RHT voices?
No. No API Keys Required. Gemini, OpenAI, and Google Cloud families in the Unified AI Voice Engine run through the GSpeech Cloud Console.
RHT is the selection player, not the article player
Publish the RHT widget when you want highlight-to-listen. Pair it with a Full Page player when the whole post should also have a bar. Same Cloud Console, same Generate Once, Keep and Play files for stored audio, same No API Keys Required path.
