How to Set Up Text-to-Speech on School Chromebooks (2026 Guide)

Chromebooks dominate K-12 education — over 60% of devices shipped to U.S. schools are ChromeOS. If you're an IT administrator responsible for providing text-to-speech accommodations, you need to know how to configure TTS on managed Chromebooks at scale. This guide covers everything from built-in ChromeOS accessibility features to deploying third-party Chrome extensions through Google Admin Console.

This guide is tool-agnostic. Whether you're deploying ReadingVox, Read&Write, or just enabling ChromeOS built-in features, these steps apply.

Option 1: Built-in ChromeOS Text-to-Speech

ChromeOS ships with two TTS features that require zero additional licensing. They're worth understanding even if you plan to deploy a third-party tool, because they're always available as a fallback.

Select-to-Speak

Select-to-Speak lets students highlight any text on screen and hear it read aloud. It works across the entire operating system — web pages, PDFs, Google Docs, even system menus.

To enable via Google Admin Console:

Sign in to admin.google.com
Navigate to Devices > Chrome > Settings > Users & browsers
Select the organizational unit (OU) containing your student Chromebooks
Scroll to Accessibility (or search for it)
Set Select-to-Speak to Allow user to enable Select-to-Speak

Once enabled, students activate it by going to Settings > Accessibility > Text-to-Speech > Select-to-Speak, or by pressing Search + S. They then click and drag to select text, and ChromeOS reads it aloud with basic word highlighting.

Limitations: Select-to-Speak uses the built-in ChromeOS TTS engine, which sounds noticeably robotic. There's no vocabulary support, no reading speed memory, no per-student settings, and the highlighting can lag on longer passages. It's a functional baseline, not a full reading accommodation tool.

ChromeVox (Screen Reader)

ChromeVox is a full screen reader designed for students with visual impairments. It reads everything — buttons, menus, headings, all page content — and is controlled entirely by keyboard. It's a critical accessibility tool, but it's not what most teachers mean when they ask for "text-to-speech for struggling readers." Don't enable ChromeVox district-wide unless you specifically need screen reader functionality; it will confuse students who just need TTS reading support.

Option 2: Chrome Extensions via Google Admin Console

For a full-featured TTS experience — natural-sounding voices, word-level highlighting, reading tools — you'll want a Chrome extension. Here's how to deploy one to managed Chromebooks.

Step 1: Choose Your Extension

Popular TTS extensions for K-12 include:

ReadingVox — Neural TTS with word-level highlighting, AI vocabulary simplification, OpenDyslexic font, screen mask, translation. $1/student/year.
Read&Write by Texthelp — TTS plus writing tools (word prediction, speech-to-text). ~$2.20–2.50/student/year.
ReadSpeaker — Enterprise TTS with language support. Pricing varies.
Natural Reader — Free tier with basic TTS, paid tier for natural voices.

For any extension, note the Chrome Web Store extension ID. You'll find it in the URL when viewing the extension in the Chrome Web Store — it's the long string of letters after /detail/.

Step 2: Force-Install via Google Admin Console

Force-installing ensures the extension appears on every student Chromebook in your target OU without students needing to install anything. Students cannot remove force-installed extensions.

Sign in to admin.google.com
Navigate to Devices > Chrome > Apps & extensions > Users & browsers
Select the appropriate organizational unit — typically your student OU or a specific grade-level OU
Click the yellow + button in the bottom-right corner
Select Add from Chrome Web Store
Search for the extension by name, or paste the extension ID
Click Select
In the extension's settings panel, set the Installation policy to:
- Force install — Extension is installed automatically and cannot be removed
- Force install + pin — Same as above, plus the extension icon is pinned to the toolbar (recommended for TTS tools so students can find it)
Click Save

The extension will deploy to all Chromebooks in that OU within the next policy refresh cycle — typically within an hour for online devices, or at next login.

Step 3: Configure Extension Policies (If Applicable)

Some extensions support managed configuration through Google Admin. This lets you pre-configure settings so students don't have to — for example, setting the default voice, reading speed, or license key.

For ReadingVox, you can push the site license key as a managed policy so students never need to enter it manually:

In the extension's settings panel in Google Admin, look for Policy for extensions (or Managed configuration)
Enter the JSON configuration provided by your vendor. For ReadingVox, it looks like:

{
  "licenseKey": {
    "Value": "your-site-license-key-here"
  }
}

Save the policy

This means that when a student opens their Chromebook and clicks the ReadingVox icon, it's already activated. Zero friction.

Step 4: Configure Allow/Block Lists (Optional)

If your district restricts which extensions can be installed, make sure your TTS extension is on the allow list:

In Google Admin, go to Devices > Chrome > Apps & extensions > Users & browsers
Under Additional settings, find Allow/Block mode
If set to Block all, allow some, add your TTS extension ID to the allow list
If set to Allow all, block some, no action needed

Step 5: Test Before Full Deployment

Before rolling out to the entire district:

Create a test OU in Google Admin with a small group of devices (5-10 Chromebooks)
Apply the extension policy to the test OU only
Verify the extension appears on test devices after policy refresh
Have a teacher and a student test the extension on common classroom sites: Google Docs, Google Classroom, your LMS (Canvas, Schoology, etc.), and any curriculum websites (Newsela, CommonLit, etc.)
Check for conflicts with other extensions — some TTS tools conflict with Grammarly, ad blockers, or other accessibility extensions
Verify the extension works on your district's content filter/proxy if you use one (Securly, GoGuardian, Lightspeed, etc.)

Common Issues and Troubleshooting

Extension Doesn't Appear on Student Devices

Check OU placement. Is the student's device or user account actually in the OU where you applied the policy? Use Devices > Chrome > Devices to verify.
Force a policy refresh. On the Chromebook, go to chrome://policy and click Reload policies. Or have the student sign out and back in.
Check the extension's status. On the Chromebook, go to chrome://extensions and verify the extension is listed and enabled.

Extension Conflicts

If TTS audio doesn't play or the extension behaves unexpectedly:

Temporarily disable other extensions to identify conflicts
Common culprits: other TTS extensions (Select-to-Speak can conflict with Chrome extension TTS), ad blockers that strip page content, and content filters that inject scripts into pages
If your content filter modifies page content (like injecting a toolbar), it can interfere with extensions that read page text

Audio Doesn't Play

Check volume. Sounds obvious, but Chromebook volume is often muted or set to zero by students.
Check audio output. If headphones were unplugged, audio may be routing to speakers (which might be muted by admin policy in some deployments).
Check network. Extensions that use server-side TTS (like ReadingVox) require internet access. If the Chromebook is offline or behind a restrictive firewall, audio won't load.
Check firewall/proxy rules. Ensure the TTS service's domains aren't blocked. Each vendor will provide a list of domains to whitelist.

Domains to Whitelist

If your district uses a firewall or content filter, you may need to whitelist domains for your TTS extension to function. Here are common ones:

ReadingVox: *.readingvox.com, *.amazonaws.com (for audio delivery)
Read&Write: *.texthelp.com, *.rwglobal.com
General Chrome extension requirements: clients2.google.com, chrome.google.com

Contact your specific vendor for a complete list.

Recommended Deployment Strategy

Based on what we've seen work across hundreds of school deployments:

Start with one school. Don't go district-wide on day one. Pick a school with enthusiastic teachers and a responsive principal.
Deploy to all students, not just IEP/504. At $1/student/year (ReadingVox pricing), universal deployment costs less than selective deployment costs in IT labor. And it removes the stigma — when every student has TTS, no one is singled out for using it.
Train teachers, not just students. Students figure out extensions in about 30 seconds. Teachers need to understand when and how to encourage TTS use — during independent reading, on assessments (if accommodation allows), on homework.
Pin the extension. Force-install plus pin to toolbar. If students can't see the icon, they forget it exists.
Collect usage data after one grading period. Most TTS extensions provide usage analytics. Use this data to justify expansion or identify which student populations benefit most.

Summary

Setting up text-to-speech on school Chromebooks comes down to three decisions: whether built-in ChromeOS features are sufficient (they usually aren't for true reading accommodations), which extension to deploy, and how to manage it through Google Admin Console. The actual deployment process — force-install, configure, test — takes about 30 minutes once you've made those decisions.

If you're evaluating ReadingVox for your school, request a free trial license and follow the deployment steps above. Your students can be using it tomorrow.