One script tag, any platform.
Custom build, a framework, a platform we have never heard of: if you can add one script tag to the head, AbleGuard can scan every page and apply the fixes you approve. The same honest mechanism as everywhere else, and the same limits stated out loud.
- Works anywhere you can add a script
- WCAG 2.2 AA, graded by axe-core
- Free 5-page check, no card
Why it matters
One tag, whatever you built it with.
Platform-agnostic
A custom build, a framework, or a platform nobody has heard of. If the rendered page can carry a script tag, it can be scanned.
Read after it renders
The scanner reads the page as assistive technology does, once it has rendered, so React or Vue is not a problem in itself.
Nothing runs on your stack
Scanning happens on our servers. Your build, your pipeline and your hosting stay exactly as they are.
Fixes are browser-side here
Without a server-side integration the rules are applied in the browser. Source-level fixing needs the WordPress plugin.
The record is the same
Verification, the statement on your own domain, monitoring and the dated evidence pack do not depend on how fixes are delivered.
It cannot reach a login
Pages behind authentication are outside the scan today, which matters if that is where most of your site lives.
How it works
Three steps, no vocabulary to learn.
Add the script tag
One tag in the head. Scanning itself happens on our servers, so your stack is untouched and your build stays as it is.
Fix what can be fixed safely
Attributes and CSS only, from rules you approve one at a time. On a platform without a server-side integration, they are applied in the browser — the source-level mode needs the WordPress plugin.
Get the record either way
Verification, the accessibility statement on your own domain, monitoring on your plan’s cadence, and a dated evidence pack. Those do not depend on how the fixes are delivered.
One tag, then find out.
Five pages free, monthly, no card, on any platform that takes a script.
The same product, delivered differently.
What changes on a generic site is how a fix reaches the page. What does not change is the approval, the verification and the record.
One script tag is the whole integration.
Add it to the head and the first scan can run. There is no build step, no package to install and nothing for your team to maintain.
- Works with any rendered page
- Scanning runs on our servers
- No build changes
In the browser, because there is no other way in.
Fixes are applied at the source where the platform allows it, and in the browser where it does not. On a generic site that means the browser, and the rules are still yours to approve.
- Source-level fixes need the WordPress plugin
- Attributes and CSS only
- Re-measured on the live page
The evidence pack does not care about your stack.
Scans, fixes, verifications and manual checks accumulate into the same dated, printable history regardless of what your site is built on.
- Dated and printable
- Statement on your own domain
- Nothing back-dated or edited
Frequently asked questions
About any website. The product-wide questions are on the features page.
Does it work with React, Vue or a static site?
Yes, as long as the rendered page can carry the script tag. The scanner reads the page as assistive technology does, after it renders, so a framework is not a problem in itself.
Can it scan pages behind a login?
Not today. The scan reaches pages it can load, so a members-only area is outside it, which is worth knowing before you buy if that is where most of your site lives.
Do I get the statement and evidence pack too?
Yes. The statement on your own domain, monitoring, verification and the dated evidence pack are part of the paid plans regardless of platform. Only the fix delivery differs by platform.
Start fixing your site today. Free.
Five pages, every problem ranked by risk, in plain English — before a lawsuit-hunting scan finds them first.
- Free 5-page check
- No credit card
- 14-day money-back guarantee