Accessibility widget · not an overlay, real scanning

Is your site accessible to everyone? Do not guess, measure.

30 settings and 11 ready-made profiles for visitors with a single line of code. Behind it, a real WCAG 2.2 scanner: 0-100 Accessibility Health, a severity-ranked violation report and an EAA statement generator. See the technical findings and improve them.

Start free See the sample report 0-100 Accessibility Health · violation report · EAA statement

Standards and frameworks covered

The badges above are supported standards; installing the widget alone does not mean automatic/full legal compliance.

Honest positioning

There is no such thing as a "one-click accessible site".

Overlay tools inject a single script and claim "instant compliance"; this neither resolves most WCAG violations nor avoids legal risk. We chose a different path: measure, report, document.

The overlay approach

One line of script, a big promise.

  • "Instant / 100% compliance / protects from lawsuits", legal risk
  • Does not fix the source code; hides the problem rather than solving it
  • Produces no auditable report or statement
  • It can interfere with the DOM and break the screen reader

"We wired up a button, the site became accessible", that is not how it actually works.

cerez.io approach

Helper widget + real scanner + documentation.

  • Genuinely measures against WCAG 2.2 A/AA/AAA rules
  • 0-100 Accessibility Health + prioritized violation report
  • Document your obligation with the EAA statement generator
  • Shadow DOM, native screen reader behavior is preserved

We say it plainly: full compliance requires source code fixes and manual review. We shorten the path and produce the evidence.

Real scan · real output

Not guesswork, measurable compliance.

The WCAG 2.2 scanner analyzes your site page by page, ranks violations by severity and produces a 0-100 Accessibility Health score. The report below is an example output.

0/ 100 Accessibility Health

WCAG 2.2 AA · 24 pages scanned

Last scan: today 09:14

+14 points versus last month
Priority violations17 findings · example
Critical Image has no alt text3 images have no description, the screen reader cannot read them · WCAG 1.1.1 (A) AI suggestion
Critical Low color contrastButton text is 2.9:1, AA requires ≥4.5:1 · .btn-secondary · WCAG 1.4.3 (AA) Fix in source
Serious Focus indicator not visibleThe :focus style has been removed, keyboard users get lost · WCAG 2.4.7 (AA) Fix in source
Serious Missing form labelThe search input has no accessible name · input#search · WCAG 3.3.2 (A) Guide
Moderate Heading hierarchy skippedJump from h2 to h4, h3 is skipped · blog post · WCAG 1.3.1 (A) Guide

Automatic scanning catches a significant portion of violations; full WCAG compliance requires source code fixes and manual review. "Auto-fix" provides a temporary, SDK-level solution only for specific violations. For AI alt-text suggestions, human review is recommended.

0
Accessibility features · active with one click
0
Ready-made profiles (dyslexia, elderly, seizure safe…)
0-100
Measurable Accessibility Health
0 line
Installation code
11 ready-made profiles

The visitor selects the profile that suits them with one click.

Each profile activates the relevant group of features at once and remembers the user's preference.

Elderly Mode

Large font, high contrast, animation stop, large cursor.

Seizure Safe

Animations stop, flashing effects are blocked. For epilepsy.

Low Vision

Large text, letter and line spacing, link highlighting, large cursor.

Dyslexia

OpenDyslexic font, line spacing, reading guide, letter spacing.

ADHD Mode

Reading mask, simple view, reduces distractions.

Color Blindness

Color blindness filter, protanopia, deuteranopia, tritanopia.

Motor Impaired

Large click targets, keyboard navigation, animation stop.

Attention Disorder

Reading mask, highlighted text, simple design.

Parkinson Mode

Large cursor, large click targets, animation removal.

Smart Night Mode

Low brightness, warm colors, reduced animation.

Cognitive Impairment

Readable font, line spacing, animations stopped.

30 settings · 6 categories

Under the profile, 30 settings.

A total of 30 individual settings for text, reading, color, highlighting and motion, plus 11 ready-made profiles. Some settings are off by default and only appear if the site owner turns them on.

Content Settings

10 settings
  • Text size (3 levels)
  • Line, letter and word spacing
  • Readable and dyslexia fonts
  • Large cursor, cursor colour, pause animations

Navigation

12 settings
  • Focus highlighting, larger click area
  • Reading guide and reading mask
  • Keyboard focus, link highlighting
  • Mute sound, stop autoplay

Color Filters

8 settings
  • Monochrome and saturation
  • High contrast and contrast boost
  • Low brightness, sepia, hue
  • Underlined links

The widget runs inside Shadow DOM and does not interfere with the host site's CSS or native screen reader behavior.

AI-powered · Pro plan

Automatic suggestions for missing alt text .

Using the Claude vision model it finds images without alt text and suggests descriptive text. Results are cached, the same image is never processed twice. It speeds up closing WCAG 1.1.1 (Non-text Content) findings.

  • Links to the "missing alt text" violations in the scan report
  • Plan-based quota, scales with usage
  • It is a suggestion; human review is recommended before publishing.
Try it with Pro
Installation

One line of code, two products.

Add a single line to your site's <head>; the widget loads async inside Shadow DOM and leaves your host CSS untouched. It uses the same API key as Cookie Consent; both products ship together with a single embed.

  • No developer queueWordPress, Shopify, Next.js and GTM guides are ready.
  • Does not block first paintLoads async; minimal impact on Lighthouse score.
  • CSP-compatible, isolatedNo JS namespace conflicts; native screen reader is preserved.
Get my API key

A single line. 30 settings + 11 profiles + Shadow DOM active automatically; scanning is started from the panel.

EAA · 2019/882

The European Accessibility Act is in force.

As of 28 June 2025, the EAA introduces accessibility obligations in sectors such as e-commerce, banking, transport and telecom. Turkish sites selling into the EU market may also fall within scope. cerez.io helps with this process through measurement and documentation.

  • Scanning targeting WCAG 2.2 AA + 0-100 Accessibility Health
  • EAA statement generator, documents your obligation
  • A local team that knows KAİK and KVKK

This page is not legal advice; seek advice specific to your sector regarding scope and obligations.

Honest statement

Saying "fully compliant" can lead to a fine.

In April 2025, the US Federal Trade Commission fined accessiBe 1 million dollars for claiming "one line of code makes your site WCAG compliant." cerez.io does the exact opposite: it bases your statement on a real WCAG scan and never says "fully compliant" without evidence.

Evidence-based The statement is generated automatically from your latest scan's Accessibility Health and severity-ranked violations, not from a blank template.
No overclaiming When open violations exist, it automatically drops to "partially compliant" and adds the note "automated testing does not prove full compliance."
Legally sound EN 301 549 / EU model statement skeleton, named complaint bodies and a self-declaration disclaimer.
Why an honest statement? The accessiBe case and getting your statement right
FAQ

The questions on your mind

Does your widget deliver "instant compliance"?
No, and we say so plainly. Overlays promise "one-click compliance"; that is both false and a legal risk. We actually scan your site, give you a 0-100 Accessibility Health score and a prioritized violation report, offer visitors an assistive widget, and generate your EAA statement. Full compliance requires source-code fixes and manual review; we shorten the path and document the evidence.
How do you differ from overlay tools?
Overlays hide the problem; we measure and report it. We genuinely test WCAG 2.2 A/AA/AAA rules, list violations by severity, temporarily resolve some at the SDK level with "auto-fix," and generate your EAA statement. The widget runs inside Shadow DOM and does not interfere with the host site's DOM or native screen reader behavior.
Does the EAA apply to us?
If you offer products or services in the EU market, most likely yes. From 28 June 2025, WCAG 2.2 AA is targeted in the e-commerce, banking, transport and telecom sectors. Turkish e-commerce sites with European customers may also fall within scope. For precise scope, get advice specific to your sector.
Does the widget conflict with screen readers?
The widget does not replace the visitor's screen reader. It runs in isolation inside a Shadow DOM; features that could conflict with a screen reader (e.g. reading selected text aloud, the magnifier) are off by default and only appear if the site owner turns them on.
How is AI alt text generated?
Included with the Pro plan. Using the Claude vision model it finds images without alt text and automatically suggests a description. Caching ensures the same image is never processed twice. These are suggestions; they are never published without your approval.
Does "auto-fix" deliver full compliance?
No. Auto-fix only adds temporary fixes at the SDK level for specific gaps (for example an empty page title, an unlabeled form field or a nameless link); it does not fix issues such as contrast or focus visibility and does not change the score. Structural issues require source code fixes; our report lists these in priority order with a remediation guide.
Does the widget affect my site's speed?
Because it loads async, it does not block first paint; because it uses Shadow DOM, it does not affect your global CSS. The impact on your Lighthouse score is minimal.

Start measuring your accessibility compliance today.

Not an overlay, we genuinely scan your site: 0-100 Accessibility Health, violation report, EAA statement. 30 settings + 11 profiles, Shadow DOM safety and Turkish support in a single panel.

Start free See plans Request a demo