One line to integrate
One <script> tag, deferred.
BFSG · EN 301 549 · WCAG 2.2 AA
Digital accessibility — in one line of code
A lazy-loading accessibility widget: ~6 KB loader, ~28 KB core, 28 languages, no cookies, no tracking, and no DOM/ARIA override of your page.
Or use the keyboard shortcut Ctrl + Alt + A — or the button in the bottom-right corner.
<script
src="https://widgets.professional-hosting.com/accessibility-widget/v1/accessibility-widget-loader.min.js"
defer
></script>Why this widget
An honest preference layer — not a magic compliance button.
No DOM/ARIA override
The widget never rewrites your markup.
Zero tracking, zero cookies
No analytics, no third-party calls.
28 languages, RTL-ready
Auto-detects the browser language.
Curated profiles
Six one-click presets.
Lightweight by design
A ~6 KB loader.
Explore the widget: Configuration · API · Events · Playground.
Install
One script tag covers 95 % of cases. For build tools and 13 integrations, see the options below.
Recommended
CDN — one line
The v1 alias always serves the latest release in that major.
<script
src="https://widgets.professional-hosting.com/accessibility-widget/v1/accessibility-widget-loader.min.js"
defer
></script>Production: pin a version + SRI
Pin an immutable …/<version>/… path and secure it with
Subresource Integrity.
<script
src="https://widgets.professional-hosting.com/accessibility-widget/1.0.5/accessibility-widget-loader.min.js"
integrity="sha384-…"
crossorigin="anonymous"
defer
></script>Bundlers
npm
Install @bauer-group/accessibility-widget for typed config.
npm i @bauer-group/accessibility-widget13 integrations
Frameworks, CMS & shops
React · Vue · Angular · Svelte · Next.js · Nuxt · Astro · WordPress · TYPO3 · Drupal · Shopify · Shopware · Magento.
Compliance
The widget is aligned with three overlapping frameworks:
🇩🇪 BFSG
Accessibility Strengthening Act — the national implementation of the EAA.
Legal text →🇪🇺 EN 301 549
The European standard for digital accessibility. References WCAG.
ETSI document →🌍 WCAG 2.2 AA
Web Content Accessibility Guidelines by the W3C.
W3C Recommendation →FAQ
Does the widget make my site automatically compliant?
No — and any vendor that promises automatic compliance is misleading you. No widget can repair broken markup or supply missing semantics. What it does add is a genuine, user-facing preference layer — contrast, text size, spacing, focus, reading aids and text-to-speech — on top of the accessible code you still own. Treat it as a complement to conformance work, never a replacement for it.
Does it change my HTML or ARIA?
No. The widget never rewrites your DOM or your ARIA attributes. Every preference is applied through its own isolated layer — data attributes on the root element and a scoped stylesheet — so it cannot break an already-accessible page or interfere with assistive technology.
How big is it really?
The loader is ≤ 6 KB gzip — smaller than most analytics snippets — and that is all that ships on first paint. The ≤ 30 KB core is fetched on demand, only once a visitor actually opens the panel. Both budgets are enforced automatically at build time, so they cannot regress unnoticed.
Is there any tracking or cookies?
None whatsoever. No analytics, no third-party requests, no cookies, no fingerprinting. Every preference is stored locally in the visitor’s browser via localStorage and never leaves their device.
Is it GDPR-compliant? Do I need a consent banner?
Yes, and no banner is required. Because the widget processes no personal data and sets no cookies, it raises no GDPR/DSGVO consent obligations. Preferences stay on the visitor’s device and are never transmitted to us or any third party.
What does it cost and how is it licensed?
It is free to use: anyone may embed the widget on any website at no cost. It is dual-licensed. As long as you just embed it — or publish any changes you make to the code — the AGPL-3.0-only applies (copyleft: modifications must be released under the same license). Only if you want to build the widget or modified code into your own closed-source or proprietary product without disclosing the source do you need a commercial license. Contact BAUER GROUP for commercial terms and support.