Compare
Remedify vs. EqualWeb: overlay widget compared to code fixes
EqualWeb offers an overlay widget that adjusts the storefront experience at runtime through an injected script.
Remedify replaces the widget approach with real edits to your theme and store data, each reviewed as a diff and recorded with a date so you can show your work.
| Dimension | Overlay widget | Real, code-level fix |
|---|---|---|
| Where the fix lives | EqualWeb injects a JavaScript layer that sits on top of your storefront at runtime; the underlying theme markup is unchanged. | Remedify edits the actual theme and store data — alt text, labels, focus order, contrast — so the correction is in the code itself. |
| What screen readers and keyboards see | Assistive tech reads whatever the script manages to re-write on the fly, which can drift, conflict, or break as a shopper navigates. | Assistive tech reads the corrected, semantic markup directly, because that is what the theme now ships. |
| Auditability | The behaviour is a third-party black box you cannot inspect line by line. | Every change is shown as a before/after diff you approve before it ships, and is kept in a dated remediation record. |
| Storefront performance | Adds a runtime script every shopper downloads and executes on every page. | Adds no runtime widget for shoppers; the fixes are static markup with effectively no load cost. |
| Ownership after you leave | Remove EqualWeb and the storefront reverts — the script was doing the work, so nothing underneath improved. | Uninstall Remedify and the corrected markup stays in your theme; you keep the improvements. |
| What we claim | Marketed by some vendors with sweeping accessibility promises that regulators have challenged. | We promise real fixes and a dated, good-faith record of the work — never an outcome or a legal shield. |
Real fixes plus a dated, good-faith record is a stronger position than a runtime overlay. That is the loop Remedify is built around.