For website owners
You own the website. You don't have to own the codebase.
Improve accessibility for real visitors today — and get an honest, prioritised list of what still needs a developer. Free scan, no login. Free account, no card.
- No login for your score
- Setup in under 2 minutes
- No trial timer
62Automated score
Low-contrast text in the main navigationWCAG 1.4.3 · 14×
Product images with no alternative textWCAG 1.1.1 · 31×
DeveloperNewsletter field has no associated labelWCAG 3.3.2 · 2×
DeveloperBody text below the minimum readable sizeWCAG 1.4.4 · 8×
Every finding is labelled Widget can help or Needs developer remediation. Nothing is hidden to make the widget look better.
Illustrative example — not a real scan result.
01 — The state of things
No scare statistics. Here are the sources.
Numbers without a citation are marketing. Every figure on this page links to the study it came from.
of the top one million home pages had automatically detectable WCAG failures in February 2026 — up from 94.8% a year earlier, reversing six years of slow improvement.
WebAIM Million 2026 (opens in a new tab) · published 30 March 2026, data collected February 2026
detected errors on the average home page. Six categories account for 96% of them — low-contrast text (83.9% of pages), missing alt text (53.1%) and missing form labels (51%) lead the list, as they have for seven years.
WebAIM Million 2026 (opens in a new tab) · published 30 March 2026, data collected February 2026
average detected errors on Shopify home pages — about 34% above the overall average. WordPress home pages averaged 52.8, slightly below it. Your platform changes your starting point.
WebAIM Million 2026 (opens in a new tab) · published 30 March 2026, data collected February 2026
federal website accessibility lawsuits filed in the United States in 2025, 27% more than in 2024. Counting state courts, the total passed 5,000; roughly 70% targeted e-commerce.
Seyfarth Shaw ADA Title III report, published January 2026 (covering 2025 filings) · UsableNet 2025 year-end report
All figures on this page are taken from published research and were last verified on 28 July 2026. None of them are projections or internal estimates. We re-check each one when the underlying report is republished.
And here is the statistic about our own product category
Throughout 2025, lawsuits continued to be filed every month against companies that already had an accessibility widget installed — typically alleging that the underlying code was never fixed. A widget improves the experience for real visitors and demonstrates good-faith effort. It does not substitute for fixing the code. We build the scanner, the reports and the audits precisely because it doesn't. (Source: UsableNet, 2025.)
02 — Where you stand
Before you buy anything, find out where you stand.
A 0–100 score and a prioritised issue list. No account, no card, no sales call.
Ranked by impact, not dumped in a list
Each issue maps to the affected element, the WCAG 2.2 success criterion behind it, and remediation guidance you can hand to a developer.
Two labels that change everything
"Your site has 47 issues" becomes "9 of these are handled today, 12 are a two-hour job for a developer, and 3 are the ones a lawyer would care about."
A limit worth knowing up front
Automated testing reliably detects 30–50% of WCAG 2.2 AA success criteria. Whether your alt text is meaningful, or whether a screen reader user can finish checkout, needs human judgement.
// Findings by severity
Critical3
Serious12
Moderate21
Minor11
Illustrative layout of a report summary. Severity is always given as a written label and a count — never by colour alone.
03 — The widget
Give visitors control today.
One line of code, or one click on WordPress. Visitors adapt your site to how they need to read it.
Vision
Text resizing, contrast modes, colour filters and link highlighting, applied by the visitor to suit their own sight.
Reading support
Dyslexia-friendly fonts, wider line spacing and reading guides for visitors who process text differently.
Keyboard navigation
Full TAB navigation with clear focus indicators, for visitors who cannot use a mouse or trackpad.
Seizure protection
Pauses animation and GIFs and dampens flashing content, which can be genuinely dangerous for some visitors.
Screen reader support
Semantic markup and ARIA labelling for NVDA, JAWS and VoiceOver — within the limits of what the widget can see in your code.
Focus mode
Reduces visual noise, mutes autoplay media and simplifies layouts for visitors who are easily overwhelmed.
- One-tap profiles
- Blind
- Low Vision
- Color Blind
- Dyslexia
- Motor Assist
- ADHD / Focus
- Seizure Safe
- Cognitive
About page speed — the number we won't give you
The script is under 30 kb, loads asynchronously so your content renders first, and is served from a CDN edge. We deliberately don't publish a single page-speed figure, because your real number depends on your theme, your plugins, your hosting and your visitor's device. Measure it yourself before and after install — it takes two minutes, and it's your site, not our benchmark.
04 — The honest split
What a widget fixes, and what it can't.
This is the section most overlay vendors leave out. It appears in every FlexAccesses report too.
| The issue | Widget can help | Needs developer |
|---|---|---|
| Low colour contrast | YesContrast modes let the visitor override it | Also yesThe CSS is the real fix |
| Text too small to read | YesText scaling | Not required |
| Keyboard navigation gaps | PartlyFocus indicators, TAB order support | YesStructural fixes in the markup |
| Missing form labels in the code | No | Yes |
| Missing alt text on images | NoA widget cannot invent a meaningful description | Yes |
| A <div onclick> used as a button | No | YesNot focusable, no role, no keyboard operation |
| Video without captions | No | YesCaptions have to be written |
The rule we hold ourselves to: if a fix requires changing your source code, we say so plainly. We never imply the widget resolved it. That's not modesty — it's the difference between a site that passes a demo and a site that works for the person using it.
And for the right-hand column, we hand your developer the work half-done
Saying "this needs a developer" and stopping there would leave you exactly where you started. Every manual-fix finding arrives as a ready-to-work ticket.
- Framework-specific code
Snippets for plain HTML, React, Vue and Angular — pre-tested against NVDA, JAWS and VoiceOver.
- A before-and-after simulator
Toggle between the broken and fixed markup and hear exactly what a screen reader announces in each case.
- Tickets in your tracker
Export findings straight to Jira, GitHub, Trello or Asana, each tagged with priority and legal risk.
No accessibility tool — including ours — replaces accessible design. Every site deserves real remediation work.
05 — Setup
Two minutes, no developer.
Installation is the easy part. We're honest about which findings come after it.
Scan
Enter your URL. Get a score and a prioritised issue list without creating an account.
Install
One script tag, or one click with the WordPress plugin. Brand colours, position and labels are yours to set.
Hand off the rest
Export the developer-only findings as a scoped list. Your developer fixes code instead of hunting for it.
WordPress
Native plugin, one-click. Works with Elementor, Divi, Gutenberg and WooCommerce, including checkout, and alongside WP Rocket and LiteSpeed caching.
Shopify
Install the app, or paste one line into theme.liquid.
Wix
Paste into Settings → Custom Code. No developer needed.
Squarespace
Paste into Settings → Advanced → Code Injection.
Webflow
Script embed in project settings.
Custom or headless
One script tag in the head. Framework-agnostic — React, Next.js, Vue, PHP.
<script
src="https://cdn.flexaccesses.com/fa.js"
data-account="YOUR_ID"
async></script>06 — Keeping it true
Sites don't stay fixed.
You publish a post with an unlabelled image. A theme update changes your button colours. A plugin adds a modal nobody can escape with a keyboard. Accessibility isn't a project you finish — it's a property you maintain.
- DOC 01
Accessibility statement
Generated for you, ready to publish in your footer. It describes your current state and your ongoing effort — which is what a statement is supposed to do.
- DOC 02
Compliance report
A PDF audit showing what was found, what was fixed, and when. Monitoring reports state honestly what the widget helps with and what needs a developer.
- DOC 03
Certificate
Every certificate links to a live transparency profile showing which areas are accessible and where work is ongoing. A snapshot, not a shield.
Accessibility status — your-site.com
- Standard tested against
- WCAG 2.2 AA
- Pages scanned
- 84
- Automated coverage
- 30–50%
- Areas verified accessible
- 11
- Areas with work ongoing
- 4
This certificate documents work completed on the date shown. It is not a conformance claim and confers no legal protection. The live profile at the link below shows the current state, including what is still open.
Illustrative example — not a real certificate.
Read this part carefully
A certificate is a snapshot, not a shield. It documents work done at a point in time. It is not a permanent seal, it is not legal protection, and no document — ours or anyone's — makes a site lawsuit-proof. What documentation gives you is a record of documented, continuing effort. That is worth having. It is not the same as immunity, and we won't describe it as if it were.
07 — FAQ
Questions, answered honestly.
Will this make my website fully compliant?
No. Nothing sold as a widget makes a site fully WCAG-conformant, and we won't be the vendor that claims otherwise. Real conformance means accessible design, semantic markup, alt text, captions and keyboard-operable interfaces built into the site itself. What we give you is immediate improvement for visitors, an accurate picture of what remains, and the documentation to show your work.
Will it protect me from a lawsuit?
No widget provides legal immunity — not ours, not anyone's. Courts under the ADA look at whether the site is actually usable. What helps is a documented, continuing effort: scanning, fixing what you can, recording what you've done. We help you build that record. We won't sell it to you as insurance.
Do I need a developer?
For installation, no. For some of the findings, yes — and the report tells you exactly which ones, so you can hand a developer a scoped list instead of paying them to go looking.
Will the widget slow my site down?
The script is under 30 kb and loads asynchronously, so your content renders before the widget does. We deliberately don't publish a single page-speed number, because yours depends on your theme, plugins, hosting and your visitor's device. Measure it yourself before and after install — that's the only number that means anything for your site.
Does it collect data about my visitors?
No tracking cookies. Accessibility preferences stay in the visitor's own browser via local storage, so their settings persist between visits, but nothing is sent to advertisers. GDPR and CCPA ready.
What does the free tier actually cover?
Scanning is free with no login at all for the score and issue summary. A free account — no payment card, no trial timer — covers one website, 100 scanned pages per month, unlimited widget impressions, and basic WCAG 2.2 reporting.
What if the scan finds something serious?
We tell you it's serious. We don't inflate findings to sell you an audit, and we don't soften them to keep the mood pleasant. If you want human testing — screen reader, keyboard-only, and testing by people who use assistive technology daily — that's what the manual audit is for. If you don't need it, we'll say so.
Start with the scan. Decide after that.
Free score with no login. Free account with no card. No trial timer counting down while you think about it.
Built for people who want accessibility done properly, not quickly.