npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@bauer-group/accessibility-widget-react

v2.1.0

Published

React Wrapper für das BAUER GROUP Accessibility Widget.

Readme

@bauer-group/accessibility-widget-react

React wrapper for the BAUER GROUP Accessibility Widget (BFSG / EN 301 549 / WCAG 2.2 AA).

🇬🇧 English · 🇩🇪 Deutsch

Installation

npm install @bauer-group/accessibility-widget-react

No assets to host: by default the widget loads from the BAUER GROUP CDN (the floating v1 tag) and stays current automatically — the integration may age, the widget never does.

Usage

Zero-config — drop the component in once (e.g. in your root layout):

import {
  AccessibilityWidget,
  openAccessibilityWidget,
} from '@bauer-group/accessibility-widget-react';

export function App() {
  return (
    <>
      <AccessibilityWidget />
      <button onClick={() => openAccessibilityWidget()}>Accessibility</button>
    </>
  );
}

Configuration

The config prop is fully typed (WidgetConfig) and accepts every option of window.AccessibilityWidgetConfig — appearance (position, offset, zIndex, primaryColor, locale, buttonLabel), behaviour (draggableFab, keyboardShortcut, respectReducedMotion, …), content (statementUrl, disclaimer) and the 15 accessibility features via initialFeatures / disabledFeatures. Unknown keys pass straight through, so newer widget options work without a wrapper update.

<AccessibilityWidget
  config={{
    position: 'bottom-left',
    primaryColor: '#0058a3',
    locale: 'de',
    offset: { x: 24, y: 24 },
    initialFeatures: { contrast: true },
    disabledFeatures: ['tts'],
    statementUrl: '/accessibility',
  }}
/>

Full option list (types, defaults, EN/DE descriptions): configuration reference. The exported types WidgetConfig, WidgetPosition, WidgetLocale and FeatureId give you autocomplete for every value.

Self-hosting (optional escape hatch)

Only if you must avoid the third-party CDN (strict CSP, air-gapped, …): host the three assets yourself and point the wrapper at them. No SRI is used on the floating v1 path.

<AccessibilityWidget
  loaderSrc="/accessibility-widget/accessibility-widget-loader.min.js"
  coreSrc="/accessibility-widget/accessibility-widget-core.min.js"
  cssHref="/accessibility-widget/accessibility-widget.min.css"
/>

Development

cd packages/js/react
pnpm install
pnpm build
pnpm test

Smoke tests (Vitest + happy-dom) in test/AccessibilityWidget.test.tsx are the reference pattern for the other wrappers (Vue, Svelte, Angular, …) — the dedupe mechanism (data-aw-loader, data-aw-css) is identical.

License

MIT · © 2026 BAUER GROUP — the widget loaded at runtime is separately licensed (AGPL-3.0-only or commercial).


🇩🇪 Deutsch

React-Wrapper für das BAUER GROUP Accessibility Widget (BFSG / EN 301 549 / WCAG 2.2 AA).

🇬🇧 English · 🇩🇪 Deutsch

Installation

npm install @bauer-group/accessibility-widget-react

Keine Assets zu hosten: Standardmäßig lädt das Widget vom BAUER GROUP CDN (floating v1-Tag) und bleibt automatisch aktuell — die Integration darf veralten, das Widget nie.

Nutzung

Zero-Config — die Komponente einmal einbinden (z. B. im Root-Layout):

import {
  AccessibilityWidget,
  openAccessibilityWidget,
} from '@bauer-group/accessibility-widget-react';

export function App() {
  return (
    <>
      <AccessibilityWidget />
      <button onClick={() => openAccessibilityWidget()}>Barrierefreiheit</button>
    </>
  );
}

Konfiguration

Die config-Prop ist vollständig typisiert (WidgetConfig) und akzeptiert jede Option von window.AccessibilityWidgetConfig — Darstellung (position, offset, zIndex, primaryColor, locale, buttonLabel), Verhalten (draggableFab, keyboardShortcut, respectReducedMotion, …), Inhalt (statementUrl, disclaimer) und die 15 Barrierefreiheits-Funktionen über initialFeatures / disabledFeatures. Unbekannte Schlüssel werden durchgereicht — neue Widget-Optionen funktionieren also ohne Wrapper-Update.

<AccessibilityWidget
  config={{
    position: 'bottom-left',
    primaryColor: '#0058a3',
    locale: 'de',
    offset: { x: 24, y: 24 },
    initialFeatures: { contrast: true },
    disabledFeatures: ['tts'],
    statementUrl: '/barrierefreiheit',
  }}
/>

Komplette Optionsliste (Typen, Defaults, EN/DE-Beschreibungen): Konfigurations-Referenz. Die exportierten Typen WidgetConfig, WidgetPosition, WidgetLocale und FeatureId liefern Autovervollständigung für jeden Wert.

Self-Hosting (optionaler Notausgang)

Nur falls das Drittanbieter-CDN vermieden werden muss (strikte CSP, Air-Gap usw.): die drei Assets selbst hosten und den Wrapper darauf zeigen lassen. Auf dem floating v1-Pfad wird kein SRI verwendet.

<AccessibilityWidget
  loaderSrc="/accessibility-widget/accessibility-widget-loader.min.js"
  coreSrc="/accessibility-widget/accessibility-widget-core.min.js"
  cssHref="/accessibility-widget/accessibility-widget.min.css"
/>

Entwicklung

cd packages/js/react
pnpm install
pnpm build
pnpm test

Smoke-Tests (Vitest + happy-dom) in test/AccessibilityWidget.test.tsx sind das Referenz-Pattern für die anderen Wrapper (Vue, Svelte, Angular, …) — das Dedupe-Muster (data-aw-loader, data-aw-css) ist identisch.

Lizenz

MIT · © 2026 BAUER GROUP — das zur Laufzeit geladene Widget ist separat lizenziert (AGPL-3.0-only oder kommerziell).