Visitor control that persists
Text scaling, line and letter spacing, two legible typefaces, contrast modes, colour-blind correction, a reading mask, a magnifier and a large cursor. Every choice is remembered between visits.
One script tag adds a floating button that lets a visitor scale text, switch to a dyslexia-friendly font, raise contrast, correct for colour blindness, mask everything but the line they are reading, and have the page read aloud. Twenty-seven settings, eight one-tap profiles, English and Arabic.
Alt + Shift + A
This widget is an aid layered on top of a site. It helps a visitor adapt a page to how they read, and it repairs a defined set of common defects. It does not make a site WCAG, ADA or EN 301 549 conformant, and we do not sell it as though it does. Underlying markup defects remain defects: the widget can add a missing label, but it cannot know what an unlabelled icon means, cannot fix a wrong heading order, and cannot make a keyboard trap disappear.
We say this plainly because overlay vendors have been challenged, and in the United States penalised, for claiming that a JavaScript widget delivers compliance. What we will claim is what the product verifiably does — and that claim is defensible.
Text scaling, line and letter spacing, two legible typefaces, contrast modes, colour-blind correction, a reading mask, a magnifier and a large cursor. Every choice is remembered between visits.
Fills missing alternative text, labels unlabelled controls, titles frames, ensures a main landmark. Every write is journalled, so switching it off restores the page exactly — including attributes that were absent rather than empty.
The panel sets its own text direction on its shadow root, independently of your page, so an Arabic panel works correctly on a left-to-right site. Panel styling uses logical properties throughout, so right-to-left is a data change rather than a second stylesheet.
Vanilla JavaScript in a single file. It degrades rather than breaks: no shadow DOM falls back to prefixed classes, no popover support costs you nothing but a cosmetic detail, and a private-mode browser that refuses storage keeps every setting for the session.
Per-site configuration, an embed snippet you paste once, usage analytics that tell you which settings visitors actually reach for, a page scanner that says plainly which defects the widget can mitigate and which need a change in your code, licence and team management.
Paste one tag before the closing body tag. Nothing else is required — no build step, no package manager, no framework.
<script src="https://a11y.elixtechs.com/a11y/v1/loader.js?k=YOUR_SITE_KEY" async></script>