Accessibility
Built to WCAG 2.1 AA guidelines
Consent experience
Accessibility widget for your website
A website accessibility widget is a panel your visitors open on any page to adapt it to how they read: bigger text, higher contrast, a dyslexia-friendly font, read aloud and more. Kukie's widget ships inside the same script as your cookie banner - one embed, fully self-hosted, translated into 70+ languages, with zero third-party requests and zero tracking.
What can visitors adjust? All 17 tools
Every adjustment applies instantly, persists as the visitor moves between pages, and can be reset with one tap. You choose which of these appear on your site - any module you hide is fully inactive, not just invisible.
Bigger text
Three sizes of larger, still-proportionate type.
Text spacing
Wider letter and word spacing for easier tracking.
Line height
More room between lines, in three steps.
Text align
Force left, centre or right alignment.
Dyslexia-friendly font
Swaps the page type for a dyslexia-friendly face.
Bold text
Heavier weight across the whole page.
Highlight links
Underlines and outlines every link on the page.
Highlight titles
Marks out every heading so structure stands out.
Contrast
High contrast, dark mode or inverted colours.
Saturation
Boost colour, mute it, or go monochrome.
Content scaling
Grows or shrinks the whole page in steps.
Hide images
Removes imagery for distraction-free reading.
Pause animations
Stops CSS animations, transitions and marquees.
Mute sounds
Silences audio and video elements 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
Click or select any text to hear it spoken, using the browser's own speech engine.
Page structure navigator
Lists the page's headings, landmarks and links so visitors can jump straight to what they need.
Six one-tap profiles, so nobody configures anything
Most visitors do not want to tune seventeen settings. A profile applies a sensible combination in one tap, and each one can still be adjusted afterwards.
Motor impaired
Big cursor and highlighted links, for easier targets with a mouse, switch or head pointer.
Low vision
Bigger text, stronger contrast and highlighted titles working together.
Dyslexia
The dyslexia-friendly font plus wider spacing and a reading guide.
Cognitive
Highlighted links and titles with a reading mask, cutting the page down to what matters.
ADHD
A reading mask with paused animations, for fewer competing distractions.
Seizure-safe
Pauses animations and mutes motion-heavy media, and lowers colour saturation.
Some visitors never need to open the panel at all
The widget reads the accessibility preferences a visitor has already set at operating-system level. Someone whose device asks for reduced motion or more contrast gets those respected on your site automatically, before they have touched anything.
The whole panel, in your visitor's language
An accessibility tool that only speaks English is itself a barrier. The panel ships translated into 70+ languages - the same set as your cookie banner, right-to-left scripts included - and opens in the language your banner detected for the visitor.
- A flag picker in the panel lets visitors switch language on the spot
- You choose which languages to offer, or let it mirror your banner's language set
- Every panel string can be overridden per language to match your site's voice
One script on your site, not two
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, another vendor's script loading on every page and often phoning home to its own servers.
Kukie takes the other road. When you enable the widget for a site, it is compiled into the same per-site bundle that already serves your cookie banner. Your pages keep loading exactly one script. Nothing else is requested, because everything the widget needs - the panel, the translations, the flags - travels inside it.
- No second embed code and no extra plugin to install or update
- About 15 KB compressed on top of your existing script, only for sites that enable it
- Zero additional network requests: no vendor API, no external fonts, no beacons
- Sites with the widget off ship a bundle byte-identical to one without the feature
Built by a privacy company, so it behaves like one
Popular accessibility overlays load from the vendor's servers and report back to them - which means the tool you added for inclusion quietly became another third party on your privacy policy. This one is different by construction.
Fully self-hosted
Served from your Kukie bundle on our CDN, never from a separate accessibility vendor.
Zero third-party requests
No vendor API calls, no external fonts, no analytics beacons. The network tab stays clean.
No tracking
Nothing about a visitor's choices is collected, profiled or sent anywhere.
Preferences stay local
Choices persist in the visitor's own browser so pages stay adjusted - and nowhere else.
It is the same widget we run on this website - see it in the corner of this page, and read our own accessibility statement.
Why accessibility stopped being optional in 2025
The European Accessibility Act has applied to new products and services since 28 June 2025. It reaches much of the consumer web - e-commerce prominently - and points at EN 301 549, which for websites largely means WCAG 2.1 level AA. Elsewhere, ADA lawsuits over inaccessible websites have been a fixture in the US for years. Around one in four EU adults reports a disability; accessibility is a real audience, not an edge case.
What a widget honestly does
It gives visitors real, immediate help - larger text, contrast, read aloud, a navigator - on top of whatever your site already does well. It shows visible effort, complements your accessibility statement, and makes the experience better today, while deeper fixes land in your codebase.
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 operability, labels, focus order. Vendors that promise compliance-by-widget have ended up cited in the very lawsuits their customers hoped to avoid.
This section is context, not legal advice. The widget supports your accessibility efforts 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 require an audit and remediation work specific to your organisation.
The accessibility statement is included too
An accessibility statement is the public page where you say which standard you target, what you know does not work yet, and how visitors can reach you about barriers. The EAA expects one; honest sites publish one regardless.
Kukie's legal document generator builds it with a guided wizard - conformance target, known limitations, feedback contact, assessment approach - and publishes it at its own URL. The widget's panel then links to it automatically, so the tool and the statement point at each other.
How do I add the accessibility widget to my website?
If your Kukie banner is already installed, there is nothing to install. Enabling the widget is a dashboard toggle, and your site picks it up on its own.
1
Be on a plan that includes it
The widget is a plan feature - check the pricing page for where it is included, or upgrade from your billing page.
2
Switch it on per site
Open the site's Accessibility Widget page, enable it, and tune the corner, size, colour, languages, modules and texts with a live preview of the real widget.
3
That's it - no code changes
Your per-site bundle rebuilds itself with the widget inside. The script tag on your site stays exactly as it is, on WordPress, WooCommerce, Shopify or anything else.
Running WordPress or WooCommerce? The widget rides the same embed the plugin already manages - nothing extra to install there either.
Why this widget, in one honest list
No invented comparison tables - just the facts that separate this widget from a typical accessibility overlay, each one true of the product as it ships today.
Delivered inside your existing consent script - one embed, no second vendor tag
Fully self-hosted with zero third-party requests and zero tracking
Panel translated into 70+ languages with a flag picker and RTL support
17 adjustments, 6 one-tap profiles, read aloud and a page structure navigator
Respects OS-level reduced-motion and contrast preferences automatically
Per-site control: hide modules, override any text per language, pick corner, colour and size
Accessibility statement generator built in, linked from the panel footer
The toggle button never drops below 44px - the WCAG 2.5.5 minimum target size
Want the full walkthrough of every setting? Read the accessibility widget guide in the Help Centre.
Related features
The widget is one piece of an accessible consent experience. These are its neighbours.
More on web accessibility
Guides to the European Accessibility Act, WCAG, and building consent experiences everyone can use.
Cookies
July 23, 2026 · 8 min read
Cookie Consent for the EU Accessibility Act 2025
The European Accessibility Act has applied since 28 June 2025, and cookie banners on in-scope servic...
Read more
Guides
April 4, 2026 · 8 min read
Making Cookie Banners Accessible: A Developer's Guide to WCAG 2.1 AA Compliance
Cookie banners are the first interactive element most visitors encounter, yet many fail basic access...
Read more
Guides
March 19, 2026 · 8 min read
Cookie Consent and Accessibility: Meeting WCAG 2.2 Standards in Your Banner
The European Accessibility Act took effect in June 2025, making WCAG 2.2 Level AA the baseline for c...
Read more
Guides
March 19, 2026 · 8 min read
Cookie Banner Design Best Practices: How to Stay Compliant Without Annoying Visitors
A well-designed cookie banner balances regulatory compliance with a smooth visitor experience. This...
Read moreAccessibility widget questions
What site owners ask before switching it on - including the one every vendor should answer honestly.
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 - larger text, higher contrast, a reading guide, read aloud - which genuinely 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 operability, labelled forms, 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 ships inside the same Kukie script tag that already serves your cookie banner. When you enable it for a site, your per-site bundle is rebuilt with the widget included; when it is off, the bundle is byte-identical to one 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?
The widget adds about 15 KB compressed to your existing Kukie script, and only for sites that have switched it on - sites without it ship exactly the same bundle as before. It makes no additional network requests of its own: no vendor API, no fonts fetched 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 is fully self-hosted and makes zero third-party requests. 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 or anyone else. Read aloud uses the speech engine built into the visitor's browser rather than an external service.
Can I choose which accessibility tools appear in the panel?
Yes. Every module can be switched off per site - hide the tools that do not fit and visitors never see them. You can also override any panel text per language, limit or extend the language list, pick the corner and button size, set the colour or inherit your banner theme, and hide the widget on mobile. A live preview in the dashboard shows the real widget with your settings before you save.
Give every visitor a site they can actually use
Enable the widget in a couple of clicks - same script, no code changes, live on your site within minutes.
