If you've looked into website accessibility, you've been pitched an overlay: paste one line of code, a little button appears in the corner, and your site is "accessible."
We've published an honest essay about what those widgets actually do — and why the answer is "not much."
The short version
An overlay is a script that runs after your page loads and tries to patch problems on the fly. But the underlying code — the part a screen reader reads, the part a keyboard navigates — is untouched. The widget guesses at alt text for photos it's never seen, injects controls that can fight the assistive tools guests already use, and calls the result "fixed."
What works instead
Accessibility isn't something you add to a site. It's something you build into it — semantic HTML, real alt text, contrast in the design itself, keyboard support from the first line of code. That's the standard every Remi site is built to: WCAG 2.2 AA, at the source.
The essay also answers the fair follow-up: if overlays don't work, why does Remi have a toolbar? Because ours is a comfort layer on a site that's already accessible — personalization, not a patch.