The Reviseberg visitor toolbar is one <script> tag you add to your pages. It puts a button on the page, and a visitor who opens it can change how your pages are presented to them: larger text, more spacing, a plainer font, other colours, a reading guide, stopped animations, the page read aloud. The change happens in that visitor's browser, for that visitor, and for nobody else.
It is on every plan, the free account included. On the free account the toolbar carries a small "Powered by Reviseberg"; on a paid plan it does not.
Try it on this page
This website runs the toolbar itself. Its button is at the bottom right of every page, and Alt+Shift+A opens it from the keyboard. Here it runs in demo mode: everything works except the AI assistant, so typed and spoken requests are answered by the phrase matcher in your browser alone. What you change stays in this browser and changes nothing for anybody else.
What it is, and what it is not
The toolbar changes presentation, and only for the visitor who asks. It is not a repair, and it does not claim to be one:
- It fixes nothing in your site. Your code and your content stay exactly as they are, and our scans see the page you built.
- It does not change whether your site meets WCAG, the BFSG or the European Accessibility Act. Nothing the toolbar does is evidence that it does, and nothing we publish — on this website, in the dashboard or in a plugin — says otherwise. In 2025 the US Federal Trade Commission ordered the maker of an overlay product to pay one million dollars, among other things for advertising that its product could make any website meet WCAG [1].
- It never replaces your words. A summary, a simpler version or a translation the assistant writes is shown in the toolbar's own panel or reading mode, labelled as such, and never in place of your text.
- Our scans never see it. More on that below.
The order of the work does not change: remove barriers in the source, where they are made, and then — if you want to — offer a toolbar as a comfort on top. Our guide to accessibility overlays explains why that order matters.
What a visitor can change
35 settings, grouped the way the panel shows them. In the dashboard you can hide any of them, and keep parts of a page — a logo that must keep its colours, a chart whose colours carry meaning — out of a group of settings.
Besides the settings, the toolbar does things once, on request: read the page or a selection aloud, open the main content on its own in a reading mode, list the page's headings, regions and links, jump to the main content, and put a number on every link, button and field in view so that a visitor can say the number to use it.
Profiles
9 profiles turn on several settings in one step. Each is named for the people who tend to want it and described by what it changes. Any setting can be changed on its own afterwards, and turning a profile off puts back what it set.
| Profile | What it turns on |
|---|---|
| Epilepsy and migraine | Stops animations and autoplaying video, and mutes strong colours. |
| Low vision | Larger text, stronger contrast, a plain font, a strong focus outline and a large cursor. |
| ADHD | A reading mask, no animations and a strong focus outline. |
| Reading and understanding | A plain font, more space between lines and words, and highlighted links and headings. |
| Dyslexia | A font designed for readers with dyslexia, more spacing, left-aligned text and a reading guide. |
| Colour vision | Corrects colours for red-green colour-vision deficiency; the type can be changed under Colour. |
| Keyboard and motor | Single-key shortcuts, a strong focus outline and a large cursor. |
| Read aloud and keyboard | Reads out what the visitor clicks or focuses, with keyboard shortcuts and a strong focus outline. |
| Older adults | Somewhat larger text, more line height, a large cursor, highlighted links and no animations. |
A profile is a starting point, not a promise. "Epilepsy and migraine" stops what the toolbar can stop; a video it cannot reach can still flash.
Temporary fixes
When a scan finds an image with no text alternative or a button with no name, Reviseberg can suggest the missing text, and a person on your team accepts or rejects it under Suggestions. The fix belongs in your code or your CMS. Until it is there, an Admin can let the toolbar show accepted fixes to visitors:
- Off by default. An Admin switches it on, per site.
- Accepted only. Only suggestions a person accepted are shown.
- One attribute, on one element.
alt,aria-label,titleorlang, on the exact element the suggestion was for — never text, markup or script, and never over a value the page already has. - Labelled. Every patched element carries
data-reviseberg-fix; the toolbar's About section lists them, and a visitor can turn them off. - The issue stays open. Every scan counts it until your source has the fix. The dashboard shows each suggestion as "Shown", "Not shown" with the reason, or "Fixed in your source".
A temporary fix is added in the visitor's browser, so a screen reader in that browser reads it. It disappears whenever the script does not load — which is why it is a stopgap and not the fix.
Typed and spoken requests
A visitor can type or say what they need: "bigger text", "stop the animations", "read this to me". Every request goes first to a phrase matcher that runs on the visitor's device — complete in English and German, with the common requests in 10 more languages. It is on every plan and sends nothing anywhere.
What the matcher cannot place can go to an AI model, but only when all four of these hold:
- the plan includes it: 2,000 requests a month across your sites on Starter, 10,000 on Growth, and by agreement on Enterprise; the free account has the phrase matcher only;
- an Admin has switched it on for the site;
- the page is not excluded — checkout, account and login pages are excluded from the start;
- the visitor has read a notice naming the provider and what is sent.
What is sent: the request, the toolbar's language, the settings already on, and an outline of the page — its headings, landmarks, link and button names, and its path without the query string. The page's main text only when the visitor asks about the page. Never sent: form values, the query string, and anything you mark with data-reviseberg-private or exclude. The reply is checked twice before anything is applied, and every change it makes can be undone. We store counts, not the text of requests.
Voice uses the browser's own speech recognition, which in some browsers sends the audio to the browser maker's servers. The notice says so.
Privacy
- Nothing is stored before a visitor changes something. A visitor who only looks leaves no trace.
- Settings stay in that browser, in the local storage of your site, under the toolbar's own name. No cookie, no identifier, nothing another site can read. "Hide for this visit" uses session storage, which the browser forgets.
- Counts, not people. The toolbar counts how often it was opened and which settings were turned on by hand, and sends those numbers once, when the page is hidden — without an identifier, a cookie or the page's address. Your dashboard shows daily totals per site, and those totals are all that exists.
20 languages
The toolbar's interface follows your page's language unless you set one, and a visitor can switch. English and German are written by us. The other 18 were drafted by machine translation and are waiting for review by native speakers — we say so here rather than list twenty languages as if they were equal.
Our scans never see it
The toolbar's loader stops before its first request when the browser introduces itself as our crawler, RevisebergBot, or when our engine has marked the page as a crawl. So a Reviseberg scan measures your site and never the toolbar: switching it on cannot raise a score, and a temporary fix leaves its issue open until your source has the fix.
Install
One tag, before the closing </body> of every page, with the key from your dashboard (Settings › Visitor toolbar). There is a guide for each of 43 platforms, and for many of them a plugin, module or package that adds the tag for you. None is listed in a platform's store yet: you download the package from its guide.