What we fix. What you control. What still needs a human.
Most accessibility overlays claim to “fix” dozens of WCAG criteria in one pass. Most of that is marketing. Here is what the Encludo widget actually does on your pages, in honest categories.
Applied automatically
Nothing. And that is the feature.
Encludo changes nothing on your page until a visitor asks it to. No scan on load, no silent rewrite of your colours, no “fixes” applied to a design you paid for. Add the script tag and your site renders exactly as you built it.
We shipped this the hard way. An earlier build repaired contrast on page load, holding every text pair to AAA — stricter than the law asks — and it quietly recoloured type that already met the standard. We took it out. A tool that overrules your designers without being asked is the thing we exist to be an alternative to.
What a visitor gets instead
If a page has faint text, the widget notices and offers: “Some text on this page is faint — want me to darken it?” One tap and it repairs only the pairs that genuinely fail WCAG AA, never touching text that already passes. One tap the other way and it leaves your page alone. Every change is named on screen and reversible.
Handed to your users
Thirteen adjustments your users can switch on themselves.
These are not forced on the page — the user opens the widget panel and picks what they need. That's deliberate: a person with low vision and a person with migraines need opposite things, and only they know which.
Contrast repair — measures each text/background pair and lifts only what fails
1.4.3 Contrast (Minimum)
Ask in your own words, or by voice — "the text is too small", in any of 21 languages
No formal SC — cognitive & motor support
Navigate by voice — "take me to the contact section" and the page goes there
2.1.1 Keyboard / motor support
Read aloud, with real Indian-language voices rather than a robotic English one
No formal SC — cognitive & vision support
Font size up to 200%
1.4.4 Resize Text
Line height, letter spacing, word spacing
1.4.12 Text Spacing
Dyslexia-friendly fonts (Lexend default, plus Atkinson Hyperlegible and OpenDyslexic)
1.4.8 Visual Presentation
High-contrast, dark, grayscale and inverted colour modes
1.4.3 / 1.4.6
Visible focus outline (3px, AA contrast)
2.4.7 Focus Visible
Force-underline all links
1.4.1 Use of Color
Reading guide that follows the cursor
No formal SC — cognitive support
Text simplification (AI)
3.1.5 Reading Level
20-language on-page translation
3.1.2 Language of Parts
Reported to your dashboard
Fourteen detections the audit flags for your team.
The dashboard audit scans every page the widget loads on and surfaces the violations below. These are flagged, prioritised, and trended over time — they are not silently patched. Fixing them is a code change on your end, because doing it automatically would break your pages. On-demand Accessibility Insights audits are available on every plan.
- 1.1.1 Non-text Content — images without alt attributes
- 1.2.2 Captions (Prerecorded) — videos without captions/track elements
- 1.3.1 Info and Relationships — form inputs without associated labels
- 1.3.1 Info and Relationships — data tables without header cells
- 1.4.2 Audio Control — media that autoplays unmuted
- 1.4.4 Resize Text — viewport meta tags that block user zoom
- 2.2.1 Timing Adjustable — meta-refresh redirects
- 2.2.2 Pause, Stop, Hide — marquee / blink elements
- 2.4.2 Page Titled — missing or empty document titles
- 2.4.4 Link Purpose — links with no accessible text
- 3.1.1 Language of Page — missing html lang attribute
- 4.1.1 Parsing — duplicate element IDs
- 4.1.2 Name, Role, Value — buttons with no accessible name
- 4.1.2 Name, Role, Value — iframes with no title
What no automated tool can fix
A lot of accessibility work is judgment, not mechanics. These require a human — either your team or a disabled tester — and we won't pretend otherwise.
- Video captions, transcripts, and audio descriptions (1.2.x)
- Complete keyboard operability of custom widgets (2.1.1)
- Complex multi-step form validation logic (3.3.x)
- Meaningful page titles for single-page-app routes (2.4.2)
- Alt text that describes intent rather than contents (1.1.1)
- Third-party embedded content (maps, payments, chat widgets)
For the criteria that need real human judgement, nothing replaces a person testing your site with their own assistive technology. That is the part of WCAG conformance you cannot automate your way out of — and we would rather say so than sell you a certificate.
See what the audit finds on your site
Free tier after registration. One domain. No credit card.