Google's AI changes degrade Chromebook spell-check

A Vermont reading interventionist wrote in a letter to VTDigger that the Google spell-check feature "no longer works effectively" on student Chromebooks, and that recent AI-driven suggestions now offer sentence rewrites and related links instead of simple orthographic corrections. The author, who identifies as dyslexic, says spell-check has been an essential accommodation for students and describes Vermont schools as paying "millions of dollars a year" for Chromebooks and Google software, leaving districts with limited alternatives, per VTDigger. The letter urges state action, including withholding payments to Google until the issue is fixed. Editorial analysis: this episode highlights accessibility and procurement risks when vendor UX changes undermine basic assistive features.
What happened
A Vermont reading interventionist wrote in a letter to VTDigger that the Google spell-check feature "no longer works effectively" on student Chromebooks. The author says that instead of correcting spelling, Google's artificial-intelligence features now frequently offer to rewrite sentences or surface related links, which the author argues displaces basic spell-check functionality. The letter states Vermont schools spend "millions of dollars a year" on Chromebooks and Google software licenses and urges the state to stop sending money to Google until the issue is fixed, per VTDigger.
Editorial analysis - technical context
Providers that layer generative or suggestion-oriented AI onto text inputs often surface higher-level rewrite prompts and contextual recommendations that can crowd out or change the behavior of legacy features like orthographic correction. Industry-pattern observations: when suggestion engines are prioritized over deterministic spell-check, the user experience can shift from explicit correction to optional rewriting, potentially reducing the reliability of an assistive tool.
Editorial analysis - context and significance
For practitioners: this is primarily an accessibility and procurement issue. K-12 deployments that standardize on a single vendor expose large populations to UX regressions when fundamental utilities change. Students with dyslexia and other learning differences are especially sensitive to regressions in dependable spelling correction, because those features function as accommodations in daily instruction and testing.
For practitioners - what to watch
Monitor vendor release notes and admin controls that affect spell-check behavior, accessibility setting exposure in Chrome management, district procurement reviews that mention feature regressions, and any public response from Google or education technology administrators. Observers should also watch whether other districts report similar functional changes and whether policy or contract language begins to require preservation of core assistive features.
Scoring Rationale
This is a localized but practically important accessibility and procurement story for education technologists and accessibility teams. It does not introduce new technology or large-scale policy yet, but it flags meaningful operational risk for districts and vulnerable users.
Practice interview problems based on real data
1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with.
Try 250 free problems

