Text size
Up to 160%, applied to the text itself, so pages built with fixed pixel sizes still grow.
A settings panel visitors open from any page: bigger text, high contrast, a readable font, reading aids, paused motion, read aloud and a map of the page. When something still gets in their way, they can tell you, and the report lands next to what your scan found on that page.
The widget is running here. Each button below switches a setting on for this page, exactly as a visitor would from the panel. Everything is remembered on their device and nowhere else.
Up to 160%, applied to the text itself, so pages built with fixed pixel sizes still grow.
White text on black with yellow links. Also: light high contrast, inverted colours and grayscale.
Takes the colour out of the whole page, for visitors overwhelmed by saturated colour.
Line, letter, word and paragraph spacing at the values WCAG 1.4.12 says content must survive.
Swaps decorative and condensed typefaces for a plain one, leaving icon fonts alone.
No justified or centred paragraphs, so word gaps stop shifting from line to line.
Underlines and outlines every link, so none of them depend on colour alone.
A thick amber ring with a dark halo on whatever the keyboard is on. Press Tab to see it.
A pointer about twice the usual size, easier to find and to keep track of.
A band that follows the pointer, to hold your place in long text.
Dims everything except the few lines around the pointer.
Stops CSS animation and transitions and pauses playing video.
Removes pictures and background images, so the text stands alone.
Reads the text a visitor selects, or the main content, in the browser's own voice. Nothing is sent anywhere.
Lists the page's headings and regions. Choosing one moves focus straight there.
Profiles are shortcuts, not modes: each switches on a set of settings, and visitors adjust from there. Pick one to see what it does to a typical city page.
The same permits page with larger text, underlined and outlined links, a strong focus ring on the Apply online button and a large pointer.
Some barriers no preference can get around: a form that can't be finished by keyboard, a chart with no description, a scanned PDF. The panel has a short form for those, and the report goes to the people who can fix the page.
They pick a category, describe the problem and leave an email if they want a reply. The page address and the settings they had on are attached automatically.
In SentraCheck the report sits next to the open findings the scanner recorded on that same page, one click from the inspector.
In the CMS, the template or the document, where the fix reaches every visitor and not only the one who wrote in.
Rescan, check the finding is gone, mark the report resolved, and reply if they left an address.
Reports never change your score or your accessibility statement. They are unverified until a person reads them, so they inform the work rather than the numbers.
What the visitor sees
What your team sees
Publish your accessibility statement from SentraCheck and the panel links to it. It is rebuilt from your latest scan every time someone opens it.
Some widgets are sold as instant compliance. This one isn't, and we won't sell it that way.
ADA Title II asks for the site itself to meet WCAG 2.1 AA. A panel of preferences can't add a missing description, label a form field or remove a keyboard trap. Those get fixed in the site.
No injected ARIA, no AI-guessed alt text, no automatic "repairs" running on top of your developers' code. The only changes are the ones a visitor switches on, for that visitor.
In 2025 the FTC ordered accessiBe to pay $1 million over claims that its overlay made websites compliant, and sites running overlays continue to be named in ADA lawsuits. A tool that promises compliance it can't deliver leaves you exposed.
What does fix your site: website scanning with a fix-first plan, and document remediation for the PDFs.
Every control is a native button, radio or checkbox. Tab stays inside the open panel, Escape closes it, and focus returns to where it was.
A labelled dialog, grouped controls, and spoken confirmations when a setting changes.
No violations in the open panel against the WCAG 2.1 A and AA rule sets plus best practices.
It renders in a Shadow DOM, so your stylesheets don't reach the panel and its styles don't leak onto your pages.
Choose your brand colour. If it's too pale to carry white text, the panel falls back to navy instead of failing contrast.
Visitors who've asked their system for less motion get no animation from the widget at all.
Settings stay in the visitor's browser. Nothing is collected unless they choose to send a report.
About 50 KB with no dependencies, loaded with defer so it never holds up your page.
Turn the widget on for a verified site in SentraCheck, copy its tag, and add it to your site's shared footer. It works in WordPress, Drupal, CivicPlus, Granicus or hand-built HTML.
<script src="https://sentracheck.com/widget.js"
data-site="YOUR_SITE_KEY" defer></script>
<script src="https://sentracheck.com/widget.js"
data-site="YOUR_SITE_KEY"
data-trigger="your-icon-id"
data-launcher="none" defer></script>
<button type="button" onclick="SentraCheckWidget.open()"> Accessibility settings </button>
The tag works on the verified site and its subdomains and nowhere else, so copying it to another site shows nothing.
Pick the colour and bottom-left or bottom-right in SentraCheck. Changes reach visitors within five minutes, with no new tag.
Point data-trigger at its id and
hide the floating button with data-launcher="none". An icon that isn't a real
button still gets Enter and Space support and the right roles.
Remove the old vendor's script in the same change, so two panels aren't fighting over the same icon.
No. It helps visitors with preferences no site can predict, like a bigger font or a darker page, and gives them a way to report what's still broken. Meeting WCAG 2.1 AA is done in the site itself, which is what SentraCheck's scanning and remediation are for.
None, until a visitor chooses to send a report. A report holds the page address, the category and description they wrote, an email address only if they gave one, and which settings they had on. Their IP address is kept only as a salted hash, for rate limiting. Settings never leave the visitor's browser, and there are no cookies.
It is one file of about 50 KB with no dependencies, loaded with defer, so it runs
after your page has rendered. Its settings come from one small request that browsers cache for
five minutes.
Reports are limited per visitor and per site each day, a hidden field catches simple bots, and the form only accepts pages on your own domain. Every report waits for a person to review it.
Yes. Remove their script, add this one, and if your header icon used to open theirs, point
data-trigger at it. Visitors keep a familiar entry point; you lose the automatic
rewriting of your pages, which is the part that never made the site compliant.
In a live demo we'll scan your site, walk through the fix-first plan, and switch the widget on for your domain so your team can try it where your visitors will.