Skip to content
Start free Sign in

Accessibility widget for your website

More ways to read your site.

Kukie.io adds a panel to your pages where visitors can enlarge text, raise contrast, change the font or hear text read aloud. It comes inside the script your consent banner already uses.

The widget is included on the Agency and Unlimited plans.

Watch the walkthrough

See the widget in use.

Follow a visitor from the cookie banner into the panel, then switch the widget on in the dashboard or the WordPress plugin.

1 minute 29 seconds, narrated, with captions in the player. The sites and rules in it are examples.

Read the transcript
  1. 0:00 Some visitors need bigger text. Some need stronger contrast. And some would rather listen.
  2. 0:06 Introducing the accessibility widget, from Kukie.io. It comes inside the script your cookie banner already uses.
  3. 0:13 Your visitors see your cookie banner first. Once they choose, a small round button stays in the corner.
  4. 0:19 One click, or Control plus U, opens the panel.
  5. 0:23 Seventeen adjustments apply at once. Bigger text. Higher contrast. A reading guide that follows the pointer.
  6. 0:30 Or tap a profile to set a whole combination. Dyslexia turns on a friendlier font, wider spacing, taller lines and a reading guide.
  7. 0:39 Read aloud uses the browser's own voice. Click a paragraph to hear it.
  8. 0:43 The panel speaks more than 70 languages, and mirrors right to left for Arabic and Hebrew.
  9. 0:49 Choices are saved in the visitor's own browser, so every page stays adjusted. No extra requests. No tracking.
  10. 0:57 And if their device already asks for reduced motion or more contrast, it's on before the first click.
  11. 1:03 You switch it on for each site in your dashboard. Choose the corner, the size and the colour, hide any tool you don't need, and check it all in a live preview.
  12. 1:12 On WordPress, the Kukie.io plugin has its own accessibility widget page. Switch it on there, with no new code on your site.
  13. 1:21 The Kukie.io accessibility widget. More ways to read your site.

In the panel

Adjustments for the way each visitor reads.

The panel has 17 adjustments and a page structure navigator. Each adjustment applies at once, stays on as the visitor moves between pages and resets with one tap.

  • Bigger text

    Larger type in 3 sizes that keep their proportions.

  • Text spacing

    Wider letter and word spacing for easier tracking.

  • Line height

    More room between lines, in 3 steps.

  • Text align

    Left, centre or right alignment across the page.

  • Dyslexia-friendly font

    Swaps the page type for a dyslexia-friendly face.

  • Bold text

    A heavier weight across the whole page.

  • Highlight links

    Underlines and outlines every link on the page.

  • Highlight titles

    Marks every heading, so the structure stands out.

  • Contrast

    High contrast, dark mode or inverted colours.

  • Saturation

    More colour, less colour or monochrome.

  • Content scaling

    Grows or shrinks the whole page in steps.

  • Hide images

    Removes images for reading without distraction.

  • Pause animations

    Stops CSS animations, transitions and marquees.

  • Mute sounds

    Silences audio and video on the page.

  • Big cursor

    A large, high-visibility pointer.

  • Reading guide

    A guide line, or a reading mask that follows the pointer.

  • Read aloud

    Select a paragraph or any text to hear it, spoken by the browser's own speech engine.

  • Page structure navigator

    Lists the page's headings, landmarks and links, so visitors can jump to what they need.

You choose which of these appear on your site. A module you hide is fully inactive, not only out of sight.

Profiles

One tap sets a whole profile.

Most visitors do not want to tune 17 settings. A profile applies a sensible combination at once, and each part can still be adjusted afterwards.

  • Limited dexterity

    A big cursor, bigger text and highlighted links, for easier targets with a mouse, switch or head pointer.

  • Low vision

    Bigger text, stronger contrast, taller line height and a big cursor, working together.

  • Dyslexia

    The dyslexia-friendly font plus wider spacing, taller line height and a reading guide.

  • Cognitive

    Highlighted links, a reading guide and paused animations, cutting the page down to what matters.

  • ADHD

    A reading mask, paused animations and larger content, for fewer competing distractions.

  • Reduce motion

    Pauses animations and lowers colour saturation.

Some visitors never need to open the panel. On a first visit, the widget reads the accessibility preferences set on the visitor's device. If the device asks for reduced motion or more contrast, Pause animations or Contrast is already on before the visitor touches anything.

Languages

The panel speaks your visitor's language.

An accessibility tool that only speaks English is a barrier. The panel comes in 70+ languages, the same set as your banner, and opens in the language your banner detected.

  • A picker in the panel lets visitors switch language on the spot
  • You choose which languages to offer, or the panel follows your banner's languages
  • You can change any panel text in each language to match your site
  • Arabic, Hebrew, Persian and Urdu mirror the panel right to left

One script

No second script on your site.

Kukie.io puts the widget inside the script that already runs your consent banner, so your pages keep loading one script.

Every accessibility widget on the market, including the ones sold by other consent platforms, is a separate product: another embed code, another plugin to keep updated and another vendor's script on every page, often reporting back to its own servers.

When you turn the widget on for a site, it joins the script that serves your banner. Nothing else is requested, because everything the widget needs (the panel, the translations and the flags) travels inside it. The widget script adds about 15 KB compressed1, and only for sites that turn it on.

  • No second embed code and no extra plugin to install or update
  • No network requests of its own: no vendor API, no external fonts, no beacons
  • Sites with the widget off get the same script as before, byte for byte

Privacy

Built by a privacy company.

Popular accessibility overlays load from the vendor's servers and report back to them, so the tool you added for inclusion becomes another third party in your privacy policy.

  • Served with your banner

    It comes from your Kukie.io script on our CDN, never from a separate accessibility vendor.

  • No third-party requests of its own

    No vendor API calls, no external fonts, no analytics beacons. Read aloud uses the browser's own voices, which some browsers fetch online.

  • No tracking

    Nothing about a visitor's choices is collected, profiled or sent anywhere.

  • Preferences stay local

    Choices are kept only in the visitor's own browser, which is how pages stay adjusted from one to the next.

It is the same widget we run on this website, in the corner of this page. Read our own accessibility statement.

The law

What changed for accessibility in 2025.

The European Accessibility Act has applied to new products and services since 28 June 20252. It reaches much of the consumer web, e-commerce in particular.

The Act points to EN 301 549, which for websites largely means WCAG 2.1 level AA. Elsewhere, ADA lawsuits over inaccessible websites have been common in the US for years. Around one in four EU adults reports a disability, so accessibility concerns a real audience, not an edge case.

  • What a widget honestly does

    It gives visitors real, immediate help, such as larger text, contrast, read aloud and a navigator, on top of whatever your site already does well. It shows visible effort, complements your accessibility statement and improves the experience today, while deeper fixes land in your code.

  • What no widget can do

    No overlay makes a website WCAG, EAA or ADA compliant, whatever the sales page says. Conformance lives in your markup: semantics, keyboard operation, labels and focus order. Vendors that promised compliance by widget have ended up cited in the lawsuits their customers hoped to avoid.

The widget supports your accessibility work and improves the experience for many visitors. Whether your website meets a given legal standard depends on how the site itself is built, and may need an audit and remediation work specific to your organisation.

Accessibility statement

An accessibility statement comes with it.

An accessibility statement is the public page where you say which standard you aim for, what does not work yet and how visitors can reach you about barriers. The EAA expects one.

The Kukie.io legal document generator builds it with a guided wizard, covering the conformance target, known limitations, a feedback contact and how you assessed the site, and publishes it at its own address. The widget panel then links to it, so the tool and the statement point at each other.

Setup

Switch it on from your dashboard.

If your Kukie.io banner is already installed, there is nothing to install. The widget is a switch in the dashboard, and your site picks it up by itself.

  1. Step 1: Be on a plan that includes it

    The widget is included on the Agency and Unlimited plans. Check the pricing page for the details, or upgrade from Billing & Invoices in your dashboard.

  2. Step 2: Switch it on for each site

    Open the site's Accessibility widget page, turn it on and set the corner, size, colour, languages, modules and texts, with a live preview of the real widget.

  3. Step 3: No code changes

    Your site's Kukie.io script is rebuilt with the widget inside. The embed code on your site stays as it is, on WordPress, WooCommerce, Shopify or anything else.

Running WordPress or WooCommerce? The widget comes through the same embed the plugin already manages, so there is nothing extra to install there either.

In short

Why this widget, in one list.

No invented comparison table, only the facts that separate this widget from a typical accessibility overlay, each true of the product as it ships today.

  • Inside your existing consent script: one embed, no second vendor tag
  • Served with your banner, with no third-party requests of its own and no tracking
  • A panel in 70+ languages, with a language picker and right-to-left layouts
  • Read aloud, a page structure navigator, 17 adjustments and 6 one-tap profiles
  • Reduced-motion and contrast preferences from the visitor's device, applied on a first visit
  • Your control for each site: hide modules, change any text per language, pick the corner, colour and size
  • An accessibility statement generator, linked from the panel footer
  • A toggle button never smaller than 44px, the WCAG 2.5.5 target size

Read the accessibility widget guide

Questions about the accessibility widget

Does an accessibility widget make my website WCAG or EAA compliant?
No, and be wary of any vendor that says otherwise. A widget gives visitors tools to adapt your pages, such as larger text, higher contrast, a reading guide and read aloud, which helps people and shows visible effort. But conformance with WCAG or the European Accessibility Act depends on how your site is built: semantic markup, keyboard operation, labelled forms and a sensible focus order. A widget supports your accessibility work. It does not replace an audit or fixes in your own code.
What is the European Accessibility Act, and does it apply to my website?
The European Accessibility Act (EAA) is an EU directive that has applied to new products and services since 28 June 2025. It covers many consumer-facing online services, e-commerce among them, and points to the EN 301 549 standard, which for websites largely means WCAG 2.1 level AA. Microenterprises providing services are exempt, and existing service contracts have transition periods. If you sell to EU consumers, it is worth reading up on. This page is product information, not legal advice.
Do I need to add another script or plugin to my website?
No. The widget comes inside the same Kukie.io script that already serves your cookie banner. When you turn it on for a site, that script is rebuilt with the widget included. When it is off, the script is byte for byte the one you had without the feature. There is no second embed, no separate plugin and nothing new to install or update on your site.
Will the accessibility widget slow my website down?
Only a little. The widget script is about 15 KB compressed, plus the panel text for the languages you offer, and it is added only for sites that turn it on. Sites without it get exactly the same script as before. It makes no network requests of its own: no vendor API, no fonts from a CDN, no analytics beacon. Everything it needs travels in the one script your pages already load.
Does the widget track visitors or send their data anywhere?
No. The widget comes from your Kukie.io script and makes no third-party requests of its own. A visitor's chosen adjustments are stored only in their own browser so they persist between pages, and nothing about their choices is sent to Kukie.io or anyone else. Read aloud uses the voices the visitor's browser provides. Some browsers fetch those voices from an online service, which is a request the browser makes, not the widget.
Can I choose which accessibility tools appear in the panel?
Yes. You can switch off any module for a site, and visitors never see the tools you hide. You can also change any panel text per language, limit or extend the language list, pick the corner and button size, set the colour or use your banner colour, and hide the widget on phones. A live preview in the dashboard shows the real widget with your settings before you save.

Give visitors more ways to read your site.

Turn the widget on for a site in your dashboard. Your pages keep the same script, with no code changes.

Related features

The widget is one part of an accessible consent experience. These are its neighbours.

See all features

More on web accessibility

Guides to the European Accessibility Act, WCAG and consent that everyone can use.

See all articles

Footnotes

Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.

  1. 1. Measured on 30 September 2026 on the widget script itself: 50,593 bytes uncompressed and 15,333 bytes with gzip at level 6. KB on this page is 1,024 bytes. The panel text and flag for each language your site offers are added on top, and the compression your visitors receive from the CDN can differ slightly.Back to footnote 1 in the text
  2. 2. The European Accessibility Act is Directive (EU) 2019/882 on the accessibility requirements for products and services. Article 31(2) sets 28 June 2025 as the date from which its measures apply.Back to footnote 2 in the text

Listed on