Frequently Asked Questions

Encludo is an AI-powered accessibility platform that helps websites meet WCAG 2.2 AA with a single line of code. It includes 15+ user-controllable accessibility settings, AI chat, voice commands, 20-language translation, real-time contrast correction, and a dashboard audit that detects 14 WCAG criteria for your team to address.

Register for free, add a single script tag to your website, and the widget appears as an accessibility button your users can open. Contrast failures are corrected automatically at runtime. The dashboard audit scans your pages and flags 14 further WCAG issues for your team. Everything else (font size, fonts including Lexend by default for dyslexia, focus outlines, link underlines, colour modes, translation) is exposed as user-controllable settings — because someone with low vision and someone with migraines need opposite things. The AI chat adapts its response style to the visitor's selected disability profile and asks clarifying questions when uncertain rather than guessing.

Yes. After registration, the Free tier includes one domain, 3,000 pageviews/month per domain, and unlimited AI accessibility chat. No credit card required.

Encludo works with any website — WordPress, Shopify, React, Angular, Vue, static HTML, or any other framework. If it runs in a browser, Encludo can make it accessible.

No. The widget is under 50KB gzipped and loads asynchronously. It has zero impact on your page load time and scores 95+ on Lighthouse performance.

No. The widget uses Shadow DOM, which creates a completely isolated scope. Your styles don't affect the widget, and the widget doesn't affect your styles.

Add the class "encludo-language-selector" to any element on your page — a button, link, header item, anything. The same script tag that loads the accessibility widget binds the trigger automatically. Add data-encludo-language-label to a child element if you want it to show the active language's native name (e.g. "हिन्दी"). Multiple triggers stay in sync; clicking is a no-op when translation is disabled in the dashboard. Full example in /docs/.

All widget controls (text, color, navigation aids, profiles) work completely offline. AI features (chat, translation, simplification) require an internet connection.

Our CDN. You add a single <script> tag pointing at our hosted file — no build step, no package to install, no assets to deploy. Updates ship through the CDN so your users always get the latest accessibility fixes automatically.

Alt+A toggles the widget open and closed — on a Mac that is Option+A, since Option is the key marked Alt. Alt+Shift+A (Option+Shift+A on a Mac) opens the widget and jumps directly into the AI chat input, which is useful for switch users and voice-control users who otherwise need multiple steps. Esc closes the widget. All chat controls are reachable via Tab.

No automated tool can, and we're honest about it. Encludo auto-corrects contrast at runtime (WCAG 1.4.3), hands 15+ visual adjustments to your users, and scans for 14 common WCAG violations (alt text, form labels, empty links, heading order, ARIA names, missing lang, duplicate IDs and more) which it reports to your dashboard as Accessibility Insights — diagnostic, not certifying. For the parts that need real human judgement, nothing replaces testing by a person using the site with their own assistive technology.

Encludo materially improves your accessibility posture — real contrast correction, user controls, documented audit trail, and the option to add a manual audit report by disabled testers. No tool can guarantee legal immunity, and we explicitly do not issue WCAG conformance certificates because they're what the disability community has criticized overlay vendors for. What matters in ADA cases is demonstrating proactive, ongoing accessibility effort and consulting real users with disabilities — both of which Encludo documents.

Yes. EAA requires WCAG 2.1 AA conformance for digital products in the EU. Encludo auto-corrects contrast, hands user-controllable visual adjustments to your visitors, reports 14 WCAG detections to your dashboard, and offers pay-as-you-go manual audits by disabled testers — the combination your DPA or procurement team will want to see.

For AI features, you can either wait until next month, upgrade Free to Pro, or — on either tier — bring your own OpenAI key from Dashboard → AI Settings to lift all AI rate limits. The widget itself never breaks for your end users; only AI features pause.

Yes. No long-term contracts. Downgrade or cancel any paid domain at any time from the dashboard. You can always fall back to the Free tier.

Nothing while we are in beta. There is no price list yet and no card to enter — we onboard beta sites by hand. When pricing does arrive, beta sites hear first and nobody is moved onto a paid plan without agreeing to it.

accessiBe charges roughly $490/mo per website, UserWay starts at $49/mo, AudioEye from $49/mo up past $1,500/mo for managed plans. Encludo is free during the beta. We would rather earn the right to charge than publish a price for a product that is still changing.

Three ways. First, we never modify your page's structure — no injected ARIA, no invented alt text, no auto-fixes, so nothing we do can break what your markup already gets right. Second, we do not claim to make you compliant, because a script cannot; we hand control to your visitor and report what needs fixing. Third, you see exactly what runs on your site through the dashboard. No black box.

Yes. The dashboard shows per-domain: which users activated which feature, audit health over time, translation usage, device breakdowns, and accessibility preference aggregates. All consent-gated and privacy-safe.

People who use assistive technology every day — screen readers, magnification, switch access and voice control — across visual, auditory, motor and cognitive needs. If a feature does not work for them, it does not ship.

By default: zero. Opt-in "functional" mode adds only anonymous pageview counts. Opt-in "analytics" mode adds aggregate feature usage and country-level geography — no PII, no fingerprinting, no cookies, no IP addresses ever stored. AI chat messages are processed for one inference and immediately discarded.

No. We treat disability profile selection as GDPR Article 9 health data and DPDP-sensitive personal data, so it lives only on your device (browser localStorage) and is never transmitted to our servers as a stored record, never written to a database, and never tied to any session, fingerprint, or visitor ID. The dashboard's aggregate "profile distribution" chart is built from anonymous per-day Redis counters with no path back to any individual.

Yes. The chat shows your last six turns in the panel for context; the "Clear chat" button at the top of the chat tab drops them. The "Reset & forget me" button at the bottom of widget settings goes further — it wipes every Encludo storage key on your device (preferences, onboarding flag, chat history, translation cache, analytics session ID).

Yes. The widget uses localStorage (not cookies) for user preferences, inherits consent from your CMP (Cookiebot, OneTrust, TrustArc, CookieYes, Osano), and respects DNT and Global Privacy Control. PII (emails, phones, long IDs, Indian PAN) is regex-scrubbed from any text we forward to an LLM, and the abuse-tracking identifier sent to LLM providers is a daily-rotating anonymous hash, not a user ID. Built to align with DPDP Act 2023 (India), GDPR (EU), and CCPA/CPRA (California).

Never. User interactions are never used to train any AI model, even with consent. Chat messages are sent to the LLM provider for one inference under a zero-data-retention contract, then discarded.