WordGlide

WordGlide moves a guide through the words of the page you are already on, at a pace you set. Nothing is extracted and nothing is re-rendered: the layout, the images, the links and the code stay exactly where the author put them. Only your attention moves. Click the toolbar button on any article or GitHub README, pick a word to start from, and press Space. THREE GUIDE STYLES · Cursor — a marker under the line, sweeping the whole word and the gap after it · Highlight — the word lit behind, one to four words at a time · Outline — the word ringed, for dense or technical text THE CURSOR, YOUR WAY Hand, dot or arrow. Size and stroke to taste. The dot leaves a short fading trail so a fast pace still reads as one motion. COLOUR THAT READS Auto senses the article's own background and picks a dark or a pale green to suit it, so the guide stays visible on a light page and on a dark one. Or choose green, blue, purple, red, orange or black yourself. PACE 60 to 1000 words per minute. Natural pauses give a comma a longer beat than a word, a sentence longer than a comma, and a paragraph break longest of all — so it reads like reading rather than a metronome. Auto-scroll keeps the line you are on in a comfortable band and stops the moment you scroll yourself. YOU CHOOSE THE PASSAGE Start at the top, or click any word. Set an end. If it grabs the wrong block, point it at the right one. Space plays and pauses, Esc pauses, and the arrow keys step a word at a time. IT GETS OUT OF THE WAY The on-page panel collapses to a small circle you can drag anywhere, or hide entirely while the guide keeps running. A WALKTHROUGH ON A REAL PAGE The first time you open it, the tutorial runs on the page you are actually on rather than a mock-up. It waits for you to pick a word, change the speed and press Space — and the speed you set during it is a real setting, not a rehearsal. PRIVACY No account, no tracking, no analytics, no reading history. Article text is never sent anywhere, because there is nowhere for it to be sent. Your settings are stored in your own browser. It asks for exactly three things: temporary access to the current tab when you click the button, permission to inject its script, and local storage for your settings. It requests no standing access to any site. WHERE IT WON'T WORK Desktop Chromium browsers, on left-to-right pages. It cannot run where extensions are not allowed to: the browser's own pages, the extension store, the built-in PDF viewer, text drawn into a canvas, embedded frames and closed shadow roots.