# Kbd

> Keyboard keys with a little depth, alone, in a combo or in a list of shortcuts. Type one for real and its keys sink as you press them; the whole combo down lights its line.

Data display · kbd, keyboard, shortcut, keys · HTML, CSS, vanilla JS · no dependencies · updated 2026-10-16
Demo: https://kodza.dev/components/kbd/

## Files

The code below, served as files: byte for byte what the Kodza site copies (the CSS includes its theme guard).

- [`kodza-kbd.css`](https://kodza.dev/registry/kbd/kodza-kbd.css) · 5.2 KB
- [`kodza-kbd.js`](https://kodza.dev/registry/kbd/kodza-kbd.js) · 4.4 KB
- [`kodza-kbd.html`](https://kodza.dev/registry/kbd/kodza-kbd.html) · 1.0 KB · the markup, to adapt and paste into your page

**Can you run shell commands? Download the CSS and the JS, don't retype them.** Retyping costs thousands of tokens and can drop or change lines of the CSS. Put the files where your stack expects them (Use it says where: change the `-o` paths):

```bash
curl -fsSL --create-dirs -o kodza/kodza-kbd.css https://kodza.dev/registry/kbd/kodza-kbd.css
curl -fsSL --create-dirs -o kodza/kodza-kbd.js https://kodza.dev/registry/kbd/kodza-kbd.js
```

Then load the files from your page as Use it shows, instead of pasting the content. The HTML is the part you adapt (text, links, modifiers): paste it from the Code section. Copy the CSS and the JS from the Code section only if you can't run commands, exactly as they are. (Windows PowerShell: `curl.exe`.)

## API

- Root: `.kodza-kbd`
- Variables (set them on the root element itself: it declares its own defaults):
  - `--kz-kbd-bg: #ffffff`
  - `--kz-kbd-fg: #0a0a0a`
  - `--kz-kbd-muted: rgba(10, 10, 10, 0.62)`
  - `--kz-kbd-line: rgba(10, 10, 10, 0.16)`
  - `--kz-kbd-depth: rgba(10, 10, 10, 0.18)`
  - `--kz-kbd-soft: rgba(10, 10, 10, 0.05)`
  - `--kz-kbd-ease: cubic-bezier(0.22, 1, 0.36, 1)`
  - `--kz-kbd-s: var(--kz-kbd-size, 26px)`
- Attributes:
  - `data-key` (e.g. `Mod`, `k`, `c`, `Enter`, `z`, `Escape`)
- Lifecycle: `kodza:init` / `kodza:destroy` on `document`, with `{ detail: { root } }` to target a container.

## Dark mode

The values Kodza uses on a dark background (`#0a0a0a`). For a page that follows the system theme, add them after the component's CSS:

```css
@media (prefers-color-scheme: dark) {
  .kodza-kbd,
  .kodza-kbd-combo,
  .kodza-kbd-list {
    --kz-kbd-bg: #1c1c1c;
    --kz-kbd-fg: #f2f2f0;
    --kz-kbd-muted: rgba(242, 242, 240, 0.62);
    --kz-kbd-line: rgba(255, 255, 255, 0.16);
    --kz-kbd-depth: rgba(255, 255, 255, 0.14);
    --kz-kbd-soft: rgba(255, 255, 255, 0.07);
  }
}
```

A site with its own theme switch puts the same rules under its dark selector instead (`[data-theme="dark"] .kodza-kbd { … }`); a single dark section, under that section's class.

## Use it

### Plain HTML page

- CSS: `kodza/kodza-kbd.css` next to the page (the Files commands as they are), linked in `<head>`: `<link rel="stylesheet" href="kodza/kodza-kbd.css">`. Without a shell, paste it in a `<style>` in `<head>` instead. It only touches `kodza-` classes.
- HTML: where the component goes. Paste it as many times as you need: instances never interfere.
- JS: `kodza/kodza-kbd.js`, loaded with `<script src="kodza/kodza-kbd.js" defer></script>` in `<head>`. Without a shell, paste it in a `<script>` before `</body>` (or in `<head>`: it waits for the page). One copy per page, whatever the number of instances.
- Restyle with the `--kz-…` variables, set on the component's root element itself (the root declares its own defaults, so a value on an ancestor is ignored), and with the modifiers / attributes listed under API.
- Font: it takes the page's own. The Kodza look is Geist: `<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@400;500&display=swap">`.
- Content added later (AJAX navigation, a SPA route, a builder preview): start it with `document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: container } }))`; before removing it, the same call with `'kodza:destroy'` stops it and puts the original markup back.

### Claude artifact (claude.ai)

- Paste the CSS in a `<style>` and the JS in a `<script>` at the end, in the artifact itself: it loads stylesheets only from Google Fonts and scripts only from a few CDNs, so no `<link>` or `<script src>` to Kodza.
- Writing the artifact file with a shell? Insert the downloaded files (Files) with a command instead of retyping them: a line `KODZA-CSS` alone inside the `<style>`, `KODZA-JS` inside the `<script>`, then `sed -e '/^KODZA-CSS$/{r kodza/kodza-kbd.css' -e 'd' -e '}' -e '/^KODZA-JS$/{r kodza/kodza-kbd.js' -e 'd' -e '}' page.html > artifact.html`.
- Font: load Geist from Google Fonts (allowed): `<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@400;500&display=swap">`.
- Dark mode: the viewer sets `data-theme="dark"` or `"light"` on `<html>`, or nothing when it follows the system. Write the Dark mode rules twice: inside `@media (prefers-color-scheme: dark)` with `:root:not([data-theme="light"])` in front of each selector, and with `:root[data-theme="dark"]` in front of each selector.

### WordPress

- HTML: a **Custom HTML** block (or a pattern / template part). WordPress keeps this markup as it is only for users allowed to post unfiltered HTML (Administrators; Super Admins on multisite): for anyone else it strips tags such as `<svg>`, `<input>` or `<dialog>`, so add it from the theme (a pattern or template part) instead.
- This one is inline (it flows like a word): pasted alone, many themes leave it at the edge of the page (block themes, and classic ones like Twenty Twenty-One or Blocksy), so put the Custom HTML block inside a **Group** block to line it up with the text.
- CSS and JS: the downloaded files go in the theme, under `wp-content/themes/<your-theme>/kodza/` (the child theme if there is one), enqueued from its functions.php (or a code-snippets plugin):
  ```php
  add_action('wp_enqueue_scripts', function () {
    $dir = get_stylesheet_directory() . '/kodza/';
    $uri = get_stylesheet_directory_uri() . '/kodza/';
    wp_enqueue_style('kodza-kbd', $uri . 'kodza-kbd.css', [], filemtime($dir . 'kodza-kbd.css'));
    wp_enqueue_script('kodza-kbd', $uri . 'kodza-kbd.js', [], filemtime($dir . 'kodza-kbd.js'), true);
  });
  ```
  Scoped to `kodza-` classes, the CSS never touches the theme. One copy of the JS, whatever the number of blocks.
- No access to the theme files? The CSS can also go, as it is, in **Appearance → Customize → Additional CSS** (classic theme) or **Styles → Additional CSS** in the Site Editor (block theme).
- Theme with AJAX page transitions: fire `kodza:init` on the new content after each swap (and `kodza:destroy` on the old one).
- Performance plugin (WP Rocket, LiteSpeed Cache, Perfmatters…) with **Delay JavaScript execution** turned on: add `kodza` to the scripts it must not delay. Otherwise the component waits for the visitor's first scroll, tap or mouse move, and that first click can be lost.
- Colours: by default, match the theme's palette. After the component's CSS, point these variables at the theme's colours, on the component root, Kodza's value as the fallback:
  `.kodza-kbd { --kz-kbd-fg: var(TEXT, #0a0a0a); --kz-kbd-bg: var(BACKGROUND, #ffffff); }`
  TEXT, BACKGROUND and ACCENT (the colour the theme fills its own buttons with) are the theme's own colour variables — block themes (theme.json, like Twenty Twenty-Five): `--wp--preset--color--contrast`, `--wp--preset--color--base`, `--wp--preset--color--contrast` (they fill their buttons with it; their accent-1… colours are decorative); Astra: `--ast-global-color-2`, `--ast-global-color-4`, `--ast-global-color-0`; Kadence: `--global-palette3`, `--global-palette9`, `--global-palette1`; GeneratePress: `--contrast`, `--base-3`, `--accent`; Blocksy: `--theme-palette-color-4`, `--theme-palette-color-8`, `--theme-palette-color-1`. Use only these names, and only if the site really has them (the theme's CSS, or Styles → Colors): the `--wp--preset--color--black`, `--white`, `--vivid-…` that WordPress adds everywhere are not the theme's palette. Another theme, or one without these variables (Hello Elementor, OceanWP): leave the variables alone, it keeps Kodza's monochrome; same when the developer asks for monochrome or the Kodza look. Leave the translucent greys (`rgba(10, 10, 10, …)`) as they are: they suit any light background. On a dark palette, set the other variables from Dark mode too.
- WordPress turns straight quotes and `--` into typographic ones in the text of a Custom HTML block (not inside `<code>` or `<pre>`).

#### With Elementor

- HTML: an **HTML** widget (Elementor shows it to administrators only). It keeps the code exactly as pasted, straight quotes included.
- CSS and JS: as above. Elementor's Site Settings → Theme Style styles every button, field, link and image of the page, components included; the theme guard at the end of the CSS keeps the component's buttons, fields and link colours as they are.
- The Elementor editor redraws each widget after the page has loaded: without the script below, the component stays still in the editor preview (the published page works). Add it once per site, in the footer like the component's script (`kodza/elementor-editor.js`, or a code-snippets plugin):

```js
// Kodza in the Elementor editor: the editor redraws each HTML widget after the page has loaded.
// Start Kodza in what it draws, stop it in what it replaces or removes. Once per site.
window.addEventListener('elementor/frontend/init', () => {
  if (!elementorFrontend.isEditMode()) return;
  class KodzaWidget extends elementorModules.frontend.handlers.Base {
    onInit() {
      super.onInit();
      this.kodza = [...this.$element[0].children];
      document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: this.$element[0] } }));
    }
    onDestroy() {
      super.onDestroy();
      this.kodza.forEach((root) => document.dispatchEvent(new CustomEvent('kodza:destroy', { detail: { root } })));
    }
  }
  elementorFrontend.elementsHandler.attachHandler('html', KodzaWidget);
});
```

- No child theme: everything can go in the HTML widget instead, `<style>` with the CSS, the HTML, then `<script>` with the JS. It works on the page and in the editor without the script above.

### Shopify

- Files: `assets/kodza-kbd.css` and `assets/kodza-kbd.js` (the Files commands with `-o assets/…`).
- In the section: `{{ 'kodza-kbd.css' | asset_url | stylesheet_tag }}` and `<script src="{{ 'kodza-kbd.js' | asset_url }}" defer></script>`, then the HTML.
- The theme editor re-renders sections: restart them with
  `document.addEventListener('shopify:section:load', (e) => document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: e.target } })));`
  and the same with `shopify:section:unload` → `kodza:destroy`.

### React / Next.js

- Files, side by side (e.g. in `components/kodza/`): `Kbd.tsx` (below), the CSS block under Code saved as `kbd.css` and the JS block as `kbd.js`, both as they are. The HTML block is already inside the component: skip it.
- Use it: `import { Kbd } from '@/components/kodza/Kbd';` then `<Kbd>⌘</Kbd>`. Props: `dataKey` (`data-key`: "Mod", "k", "c", "Enter", "z", "Escape"), `vars` (the `--kz-…` variables listed under API, e.g. `vars={{ '--kz-kbd-bg': … }}`), `children` (the text, plain), `className`, `style` and the other props of its `<kbd>` (`onClick`, `aria-…`).
- Next.js App Router: it is a Client Component already (`'use client'`). Pages Router: Next.js takes global CSS only in `pages/_app`, so move the `import './kbd.css'` line there.
- Safe under StrictMode, client-side navigation and prop changes: when a prop changes, the `key` gives React a fresh element, `kodza:destroy` stops the script on the old one and `kodza:init` starts it on the new one.

```tsx
'use client';
// Kodza — Kbd, for React. From https://kodza.dev/components/kbd/
// Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license
// Next to this file: kbd.css and kbd.js, the component's CSS and JS from Kodza, as they are.
// Yours to edit: the markup is plain JSX below.
// In Kodza's markup it sits in a <span class="kodza-kbd-combo">, which the CSS and the script use too:
// put yours in one for the same result.
// The script changes this markup once React has rendered it (it adds layers, splits text, moves
// nodes), so React must not patch it afterwards. When a prop changes, the key gives React a fresh
// element: kodza:destroy stops the script on the old one, kodza:init starts it on the new one.
import { useRef, useEffect, type ComponentPropsWithoutRef, type ComponentRef, type CSSProperties } from 'react';
import './kbd.css';

export type KbdProps = Omit<ComponentPropsWithoutRef<'kbd'>, "children" | "vars" | "dataKey"> & {
  /** data-key on the root (default: Mod) */
  dataKey?: "Mod" | "k" | "c" | "Enter" | "z" | "Escape";
  /** Settings, as CSS variables on the root */
  vars?: {
    /** default: #ffffff */
    "--kz-kbd-bg"?: string | number;
    /** default: #0a0a0a */
    "--kz-kbd-fg"?: string | number;
    /** default: rgba(10, 10, 10, 0.62) */
    "--kz-kbd-muted"?: string | number;
    /** default: rgba(10, 10, 10, 0.16) */
    "--kz-kbd-line"?: string | number;
    /** default: rgba(10, 10, 10, 0.18) */
    "--kz-kbd-depth"?: string | number;
    /** default: rgba(10, 10, 10, 0.05) */
    "--kz-kbd-soft"?: string | number;
    /** default: cubic-bezier(0.22, 1, 0.36, 1) */
    "--kz-kbd-ease"?: string | number;
    /** default: var(--kz-kbd-size, 26px) */
    "--kz-kbd-s"?: string | number;
  };
  /** The text, plain: the script reads it and rebuilds the markup around it */
  children?: string;
  className?: string;
};

export function Kbd({ dataKey = "Mod", vars, children = "⌘", className, style, ...rest }: KbdProps) {
  const ref = useRef<ComponentRef<'kbd'>>(null);
  const classes = ["kodza-kbd", className].filter(Boolean).join(' ');
  // Everything the markup is made of: when it changes, React gets a fresh element (see the top)
  const key = JSON.stringify([classes, dataKey, vars, children, style, rest]);

  // Starts the script on this element once React has rendered it, stops it when it goes
  useEffect(() => {
    const root = ref.current;
    let live = true;
    // @ts-ignore: a plain script, no types to find
    import('./kbd.js').then(() => {
      if (live) document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root } }));
    });
    return () => {
      live = false;
      document.dispatchEvent(new CustomEvent('kodza:destroy', { detail: { root } }));
    };
  }, [key]);

  return (
    <kbd key={key} {...rest} className={classes} data-key={dataKey} style={{ ...vars, ...style } as CSSProperties} ref={ref}>{children}</kbd>
  );
}
```

## Code

```html
<span class="kodza-kbd-combo kodza-kbd-combo--lg"><kbd class="kodza-kbd" data-key="Mod">⌘</kbd><kbd class="kodza-kbd" data-key="k">K</kbd></span>

<ul class="kodza-kbd-list">
  <li><span>Open the command palette</span><span class="kodza-kbd-combo"><kbd class="kodza-kbd" data-key="Mod">⌘</kbd><kbd class="kodza-kbd" data-key="k">K</kbd></span></li>
  <li><span>Copy the code</span><span class="kodza-kbd-combo"><kbd class="kodza-kbd" data-key="Mod">⌘</kbd><kbd class="kodza-kbd" data-key="c">C</kbd></span></li>
  <li><span>Ship it</span><span class="kodza-kbd-combo"><kbd class="kodza-kbd" data-key="Mod">⌘</kbd><kbd class="kodza-kbd" data-key="Enter">↵</kbd></span></li>
  <li><span>Undo your last mistake</span><span class="kodza-kbd-combo"><kbd class="kodza-kbd" data-key="Mod">⌘</kbd><kbd class="kodza-kbd" data-key="z">Z</kbd></span></li>
  <li><span>Pretend nothing happened</span><span class="kodza-kbd-combo"><kbd class="kodza-kbd" data-key="Escape">Esc</kbd></span></li>
</ul>
```

```css
/* Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license */
/* Kodza — Kbd
   Keyboard keys with a little depth, alone or in a combo, and a list of shortcuts. Type one
   for real and its keys sink as you press them; when the whole combo is down, its line
   lights up. data-key="Mod" shows ⌘ on a Mac and Ctrl elsewhere.
   Everything is tuned with the --kz-kbd-* variables. */
.kodza-kbd,
.kodza-kbd-combo,
.kodza-kbd-list {
  --kz-kbd-bg: #ffffff;
  --kz-kbd-fg: #0a0a0a;
  --kz-kbd-muted: rgba(10, 10, 10, 0.62);
  --kz-kbd-line: rgba(10, 10, 10, 0.16);
  --kz-kbd-depth: rgba(10, 10, 10, 0.18);
  --kz-kbd-soft: rgba(10, 10, 10, 0.05);
  --kz-kbd-ease: cubic-bezier(0.22, 1, 0.36, 1);
}

/* The size comes from the combo (--lg) or stays at 26px */
.kodza-kbd {
  --kz-kbd-s: var(--kz-kbd-size, 26px);
}

.kodza-kbd {
  display: inline-grid;
  place-items: center;
  min-width: var(--kz-kbd-s);
  height: var(--kz-kbd-s);
  padding: 0 calc(var(--kz-kbd-s) * 0.26);
  box-sizing: border-box;
  border-radius: calc(var(--kz-kbd-s) * 0.27);
  background: var(--kz-kbd-bg);
  box-shadow: inset 0 0 0 1px var(--kz-kbd-line), 0 2px 0 var(--kz-kbd-depth);
  color: var(--kz-kbd-fg);
  font-family: inherit;
  font-size: calc(var(--kz-kbd-s) * 0.48);
  font-weight: 500;
  line-height: 1;
  transition: transform 0.12s ease, box-shadow 0.12s ease;
}

/* Pressed: the key sinks into its depth */
.kodza-kbd.is-pressed {
  box-shadow: inset 0 0 0 1px var(--kz-kbd-line), 0 0 0 var(--kz-kbd-depth);
  transform: translateY(2px);
}

.kodza-kbd-combo {
  display: inline-flex;
  align-items: center;
  gap: 4px;
}

.kodza-kbd-combo--lg {
  --kz-kbd-size: 64px;

  gap: 10px;
}

.kodza-kbd-combo--lg .kodza-kbd {
  box-shadow: inset 0 0 0 1px var(--kz-kbd-line), 0 5px 0 var(--kz-kbd-depth);
  font-weight: 400;
}

.kodza-kbd-combo--lg .kodza-kbd.is-pressed {
  box-shadow: inset 0 0 0 1px var(--kz-kbd-line), 0 0 0 var(--kz-kbd-depth);
  transform: translateY(5px);
}

/* A list of shortcuts */
.kodza-kbd-list {
  margin: 0;
  padding: 0;
  color: var(--kz-kbd-fg);
  font-size: 15px;
  list-style: none;
}

.kodza-kbd-list > li {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 24px;
  /* The line hangs 14px past the text on each side, never more than the page leaves there (a 10px
     phone gutter): it never widens the page */
  margin: 0 calc(-1 * min(14px, (100vw - 100%) / 2));
  padding: 12px min(14px, (100vw - 100%) / 2);
  border-radius: 12px;
  transition: background-color 0.5s ease;
}

.kodza-kbd-list > li + li {
  box-shadow: inset 0 1px 0 var(--kz-kbd-soft);
}

/* The whole combo is down: its line lights up */
.kodza-kbd-list > li.is-hit {
  background: var(--kz-kbd-soft);
  transition-duration: 0.1s;
}

@media (prefers-reduced-motion: reduce) {
  .kodza-kbd,
  .kodza-kbd-list > li {
    transition-duration: 0.01ms !important;
  }
}

/* Theming example — on a dark background:
.dark-section .kodza-kbd,
.dark-section .kodza-kbd-combo,
.dark-section .kodza-kbd-list {
  --kz-kbd-bg: #1c1c1c;
  --kz-kbd-fg: #f2f2f0;
  --kz-kbd-muted: rgba(242, 242, 240, 0.62);
  --kz-kbd-line: rgba(255, 255, 255, 0.16);
  --kz-kbd-depth: rgba(255, 255, 255, 0.14);
  --kz-kbd-soft: rgba(255, 255, 255, 0.07);
}
*/

/* kodza-guard 9f185a3fefc7 — generated by Kodza, do not edit.
   Theme guard: keeps a site's own CSS (WordPress themes, Bootstrap, CSS resets…) off this
   component. :not(#_) is always true and weighs as much as an id, so these lines win over
   theme rules made of classes and tags. Customise the component through its --kz-* variables. */

/* What the browser gives, on everything the component leaves to it */

.kodza-kbd:not(#_) {
  border: revert;
  outline: revert;
  text-decoration: revert;
  list-style: revert;
  position: revert;
  outline-offset: revert;
  appearance: revert;
  max-height: revert;
  font-style: revert;
  letter-spacing: revert;
  text-transform: revert;
  text-underline-offset: revert;
  text-align: revert;
  text-indent: revert;
  text-shadow: revert;
  vertical-align: revert;
}

/* The component's own rules, one step stronger: real buttons and fields, what it sets on tags themes style (links, lists, headings, images…), and the root width (a theme may narrow it, never widen it) */

.kodza-kbd:not(#_) {
  display: inline-grid;
  padding: 0 calc(var(--kz-kbd-s) * 0.26);
  box-sizing: border-box;
  border-radius: calc(var(--kz-kbd-s) * 0.27);
  background: var(--kz-kbd-bg);
  box-shadow: inset 0 0 0 1px var(--kz-kbd-line), 0 2px 0 var(--kz-kbd-depth);
  color: var(--kz-kbd-fg);
  font-family: inherit;
  font-size: calc(var(--kz-kbd-s) * 0.48);
  font-weight: 500;
  line-height: 1;
  transition: transform 0.12s ease, box-shadow 0.12s ease;
}

.kodza-kbd.is-pressed:not(#_) {
  box-shadow: inset 0 0 0 1px var(--kz-kbd-line), 0 0 0 var(--kz-kbd-depth);
}

.kodza-kbd-combo--lg .kodza-kbd:not(#_) {
  box-shadow: inset 0 0 0 1px var(--kz-kbd-line), 0 5px 0 var(--kz-kbd-depth);
  font-weight: 400;
}

.kodza-kbd-combo--lg .kodza-kbd.is-pressed:not(#_) {
  box-shadow: inset 0 0 0 1px var(--kz-kbd-line), 0 0 0 var(--kz-kbd-depth);
}

@media (prefers-reduced-motion: reduce) {
  .kodza-kbd:not(#_) {
    transition-duration: 0.01ms !important;
  }
}
```

```js
// Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license
// Kodza — Kbd
// Shows Mod as ⌘ on a Mac and Ctrl elsewhere, sinks the keys the user is really pressing, and
// lights up a shortcut line when its whole combo is down. It only watches: nothing is
// prevented, the page keeps its own shortcuts.
(() => {
  const SELECTOR = '.kodza-kbd';
  const mac = /Mac|iPhone|iPad/.test(navigator.platform || navigator.userAgent);

  // What a key event means for data-key ("Mod" is Command on a Mac, Control elsewhere)
  const name = (event) => {
    if (event.key === (mac ? 'Meta' : 'Control')) return 'mod';
    return (event.key || '').toLowerCase();
  };
  // The keys running on the page share one watch on the keyboard, on while there is at least one
  const keys = new Set();
  const down = new Set();
  let watch = null;
  const paint = () => {
    const all = [...keys].filter((key) => key.dataset.key);
    all.forEach((key) => key.classList.toggle('is-pressed', down.has(key.dataset.key.toLowerCase())));
    new Set(all.map((key) => key.closest('.kodza-kbd-combo'))).forEach((combo) => {
      if (!combo) return;
      const parts = [...combo.querySelectorAll('.kodza-kbd[data-key]')];
      const hit = parts.length && parts.every((key) => down.has(key.dataset.key.toLowerCase()));
      const line = combo.closest('.kodza-kbd-list > li');
      if (hit && line) {
        line.classList.add('is-hit');
        clearTimeout(line.kodzaHit);
        line.kodzaHit = setTimeout(() => line.classList.remove('is-hit'), 650);
      }
    });
  };
  const start = () => {
    watch = new AbortController();
    const { signal } = watch;
    document.addEventListener('keydown', (event) => {
      down.add(name(event));
      if (event.metaKey && mac) down.add('mod');
      if (event.ctrlKey && !mac) down.add('mod');
      paint();
    }, { signal });
    document.addEventListener('keyup', (event) => {
      // On a Mac, letters held with ⌘ never send their keyup: letting ⌘ go lets them all go
      if (name(event) === 'mod') down.clear();
      else down.delete(name(event));
      paint();
    }, { signal });
    window.addEventListener('blur', () => {
      down.clear();
      paint();
    }, { signal });
  };

  // One instance. Everything it starts is tied to `signal`, so kodza:destroy stops it all
  function mount(key, signal) {
    if (key.dataset.key === 'Mod') {
      key.textContent = mac ? '⌘' : 'Ctrl';
      key.setAttribute('aria-label', mac ? 'Command' : 'Control');
    }
    keys.add(key);
    if (!watch) start();
    // The last key gone, the watch stops
    signal.addEventListener('abort', () => {
      keys.delete(key);
      if (keys.size) return;
      watch.abort();
      watch = null;
      down.clear();
    });
  }

  // Kodza lifecycle, the same in every component: `kodza:init` starts the instances inside
  // event.detail.root (the whole page by default), `kodza:destroy` stops them and puts their
  // markup back. For themes and apps that swap content without a page load.
  const instances = new WeakMap();
  const find = (scope = document) => [scope, ...scope.querySelectorAll(SELECTOR)].filter((el) => el.matches?.(SELECTOR));
  const init = (scope) => find(scope).forEach((root) => {
    if (root.classList.contains('is-ready')) return; // already running, maybe from another copy of this script
    const controller = new AbortController();
    instances.set(root, { controller, html: root.innerHTML, attrs: [...root.attributes].map((a) => [a.name, a.value]) });
    mount(root, controller.signal);
    root.classList.add('is-ready');
  });
  const destroy = (scope) => find(scope).forEach((root) => {
    const instance = instances.get(root);
    if (!instance) return;
    instances.delete(root);
    instance.controller.abort();
    [...root.attributes].forEach((a) => root.removeAttribute(a.name));
    instance.attrs.forEach(([name, value]) => root.setAttribute(name, value));
    root.innerHTML = instance.html;
  });
  document.addEventListener('kodza:init', (event) => init(event.detail?.root));
  document.addEventListener('kodza:destroy', (event) => destroy(event.detail?.root));
  init();
  // Loaded in <head>, the script runs before the markup exists: once more when it is parsed
  if (document.readyState === 'loading') document.addEventListener('DOMContentLoaded', () => init(), { once: true });
})();
```

Free to use, from Kodza (https://kodza.dev).