@a11y-context/mcp-server 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and do
+          not modify the License. You may add Your own attribution notices
+          within Derivative Works that You distribute, alongside or as an
+          addendum to the NOTICE text from the Work, provided that such
+          additional attribution notices cannot be construed as modifying
+          the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 A11y Context
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,62 @@
+# @a11y-context/mcp-server
+
+A [Model Context Protocol](https://modelcontextprotocol.io) server that serves the [A11y Context](https://a11y-context-project.vercel.app) accessibility-pattern corpus — WCAG 2.2 AA component patterns and cross-cutting Foundations rules — to AI coding agents.
+
+The server is the **retrieval mechanism**. Pair it with the A11y Context **MCP skill** (the brain that selects which patterns a task needs); the skill calls these tools. See the [setup guide](https://a11y-context-project.vercel.app/getting-started/ai-coding-agents/install/mcp-server).
+
+## Install
+
+**Claude Code:**
+
+```bash
+claude mcp add a11y-context -- npx -y @a11y-context/mcp-server
+```
+
+Or add it to your MCP client config (`.mcp.json`, `.cursor/mcp.json`, etc.):
+
+```json
+{
+  "mcpServers": {
+    "a11y-context": {
+      "command": "npx",
+      "args": ["-y", "@a11y-context/mcp-server"]
+    }
+  }
+}
+```
+
+Then run `/mcp` (in Claude Code) to confirm it's connected.
+
+## Tools
+
+| Tool | Purpose |
+|---|---|
+| `list_patterns` | List the available component patterns for a stack. Call first to select which patterns a task needs (via each entry's `selection_excerpt`). |
+| `get_pattern` | Get the full spec for one pattern by `id`: `must_haves`, `donts`, `golden_pattern`, `customizable`, `acceptance_checks`. |
+| `get_foundations` | Get the cross-cutting Foundations rules (focus, landmarks, headings, contrast, page structure). Retrieve on every UI task; each rule's `scope` decides where it applies. |
+
+All tools take a `stack` argument (defaults to `web/react`, the only fully populated stack today).
+
+## Corpus
+
+The server ships a bundled snapshot of the corpus at `corpus/<stack>/`, refreshed per release. Retrieval is deterministic ID-based selection — no vector database, no embeddings.
+
+## Transports
+
+- **stdio** (default, via `npx`) — runs locally in your MCP client.
+- **HTTP** — `npm run start` serves the same tools over HTTP for clients that connect by URL.
+
+## Development
+
+```bash
+npm install
+npm run build
+npm run dev          # stdio, ts-node
+npm run inspector    # MCP Inspector
+```
+
+Override the corpus location with `PATTERN_REPO_PATH` (absolute, or relative to the package root) to develop against a live corpus checkout.
+
+## License
+
+[Apache-2.0](./LICENSE). The bundled corpus content is also Apache-2.0.

package/corpus/web/react/components/accordion.basic.md

@@ -0,0 +1,157 @@
+---
+id: accordion.basic
+title: Accordion
+stack: web/react
+status: beta
+latest_version: 0.1.1
+tags: [accordion, disclosure, show-hide]
+aliases: [accordion, disclosure group, expand collapse, collapsible panels]
+summary: A set of show/hide sections with heading-wrapped buttons controlling associated panels via aria-expanded (and optionally aria-controls / region).
+---
+
+# Accordion
+
+Pattern ID: `accordion.basic`
+
+A set of show/hide sections with heading-wrapped buttons controlling associated panels via `aria-expanded` (and optionally `aria-controls` / region).
+
+## Use When
+- Use when content can be organized into collapsible sections to reduce scanning and scrolling.
+
+## Do Not Use When
+- Do not use when content must be visible for comparison or comprehension (use static, non-collapsing sections instead).
+
+## Must Haves
+- Accordion is composed of a series of header + panel pairs.
+- Each accordion header control is a native `<button>` (or `role="button"` only when a native button cannot be used).
+  - If role="button" is used instead of a native `<button>`, add `tabindex="0"` and keyboard support for Enter and Space, ensuring Space prevents page scrolling while activating the control.
+- Each header button is contained within a heading element (`<h2>`–`<h6>`) or an element with `role="heading"` and the appropriate `aria-level`.
+- The header button uses `aria-expanded="true"` when its panel is visible and `"false"` when hidden.
+- The panel is shown/hidden in the DOM (e.g., via the `hidden` attribute), so that hidden content **cannot** be accessed by screen readers.
+- Users move focus between accordion headers using Tab / Shift+Tab.
+- Since the header control is a button, it is activated with Enter or Space.
+- If the accordion does not permit a panel to be collapsed while expanded, the expanded header button uses `aria-disabled="true"` (rare case).
+- Ensure a visible focus state (e.g., a 2px solid outline offset by 1-2px) around the header controls.
+
+## Customizable
+- `aria-controls` on the header button pointing to the panel ID (recommended, but optional).
+- Panel container uses `role="region"` with `aria-labelledby` referencing the header button ID (optional).
+  - Avoid `role="region"` when it would create landmark proliferation (e.g., many panels can be expanded at once, especially > ~6).
+  - Prefer `role="region"` when panels contain headings.
+- Whether multiple panels can be expanded at the same time.
+  - If only one panel may be expanded, expanding a new panel collapses the previously open panel.
+- The heading level will usually be `h2`, but this is customizable and depends on the heading hierarchy of the surrounding page.
+
+## Don'ts
+- Do not use non-focusable headers (e.g., `<div>` without proper button semantics) as the interactive control.
+- Do not make the panel visible while leaving `aria-expanded="false"` (and vice versa).
+- Do not remove panel content from the DOM in a way that breaks expected focus behavior (e.g., collapsing a panel while focus remains inside it without moving focus).
+- Do not use `role="heading"` without an `aria-level`.
+- Do not nest accordions within accordion panels.
+
+## Golden Pattern
+
+Structural reference for AI coding assistants — semantics, focus, and keyboard behavior. Styling, copy, and demo data are illustrative.
+
+```jsx
+"use client";
+
+export function AccordionDemo() {
+  // Single-expand: exactly one panel open at a time.
+  const [openId, setOpenId] = useState("overview");
+
+  function toggle(id) {
+    setOpenId(id);
+  }
+
+  const overviewOpen = openId === "overview";
+  const detailsOpen = openId === "details";
+  const shippingOpen = openId === "shipping";
+
+  return (
+    <div>
+      {/* h3 assumes an h2 section heading exists above the accordion.
+          Match the heading level to the surrounding page hierarchy
+          (see Customizable). */}
+      <h3>
+        <button
+          id="acc-btn-overview"
+          type="button"
+          aria-expanded={overviewOpen ? "true" : "false"}
+          aria-controls="acc-panel-overview"
+          onClick={() => toggle("overview")}
+        >
+          Overview
+        </button>
+      </h3>
+      <div
+        id="acc-panel-overview"
+        hidden={!overviewOpen}
+        role="region"
+        aria-labelledby="acc-btn-overview"
+      >
+        <p>
+          This section contains summary information. Learn more in the{" "}
+          <a href="#details">details section</a>.
+        </p>
+      </div>
+
+      <h3>
+        <button
+          id="acc-btn-details"
+          type="button"
+          aria-expanded={detailsOpen ? "true" : "false"}
+          aria-controls="acc-panel-details"
+          onClick={() => toggle("details")}
+        >
+          Details
+        </button>
+      </h3>
+      <div
+        id="acc-panel-details"
+        hidden={!detailsOpen}
+        role="region"
+        aria-labelledby="acc-btn-details"
+      >
+        <p>
+          This panel includes supporting text and a link to{" "}
+          <a href="#policies">policies</a>.
+        </p>
+      </div>
+
+      <h3>
+        <button
+          id="acc-btn-shipping"
+          type="button"
+          aria-expanded={shippingOpen ? "true" : "false"}
+          aria-controls="acc-panel-shipping"
+          onClick={() => toggle("shipping")}
+        >
+          Shipping
+        </button>
+      </h3>
+      <div
+        id="acc-panel-shipping"
+        hidden={!shippingOpen}
+        role="region"
+        aria-labelledby="acc-btn-shipping"
+      >
+        <p>Shipping information goes here. This panel contains only text.</p>
+      </div>
+    </div>
+  );
+}
+```
+
+## Acceptance Checks
+
+- Keyboard
+  - Tab/Shift+Tab moves focus through accordion header buttons in order.
+  - Enter and Space toggle the associated panel visibility.
+  - Focus remains on the header button after toggling.
+  - If a panel is collapsed while focus is inside it (implementation choice), focus is moved to a sensible place (typically the controlling header).
+- Screen Reader
+  - Each header is announced as a button within a heading. 
+  - The expanded/collapsed state is announced via `aria-expanded`.
+  - If `role="region"` is used, the panel is announced with a name that matches the controlling header.
+  - Links inside expanded panels are reachable and operate normally.

package/corpus/web/react/components/button.basic.md

@@ -0,0 +1,91 @@
+---
+id: button.basic
+title: Basic Button
+stack: web/react
+status: beta
+latest_version: 0.2.1
+tags: [button, control, action, icon-button]
+aliases: [btn, primary button, icon button, call to action, cta]
+summary: Native button that triggers an action. Supports text-only, icon+text, and icon-only labeling patterns.
+---
+
+# Basic Button
+
+Pattern ID: `button.basic`
+
+Native button that triggers an action. Supports text-only, icon+text, and icon-only labeling patterns.
+
+## Use When
+- Use when the user triggers an immediate action (e.g., "Save", "Continue", "Dismiss").
+
+## Do Not Use When
+- Do not use when the control navigates to a new URL (use `link`).
+- Do not use when the control represents an on/off pressed state (use `button.toggle`).
+- Do not use when the control opens a menu (use `menu.basic`).
+
+## Must Haves
+- Use a native `<button>` for built-in semantics and keyboard behavior.
+  - A custom implementation with `role="button"` is appropriate only when a native button cannot be used.
+  - If role="button" is used instead of a native <button>, add tabindex="0" and keyboard support for Enter and Space, ensuring Space prevents page scrolling while activating the control.
+- The button has an accessible name that describes its purpose or action.
+- When the button has visible text, the visible text serves as the accessible name.
+- When additional context is needed beyond the visible text, add it via `aria-label`, `aria-labelledby`, or offscreen text. The visible text appears at the start of the accessible name.
+- For icon-only buttons, provide an accessible name using `aria-label` or `aria-labelledby`.
+- Icons within buttons must be decorative (`aria-hidden="true"`).
+- If the action is unavailable, disable the button using the native `disabled` attribute. (It becomes unfocusable and non-interactive.)
+- Ensure a visible focus state (e.g., a 2px solid outline offset by 1-2px) around the button.
+
+## Customizable
+- No accessibility-relevant variations beyond the Must Haves above.
+
+## Don'ts
+- Do not build a button out of a `<div>` or `<span>` with `role="button"` unless you absolutely must; native `<button>` is the baseline.
+- Do not create icon-only buttons without an accessible name (no unlabeled icons). 
+- Do not use `aria-label` that conflicts with (or is wildly different from) the visible label text. Accessible names should at least begin with the visible label.
+- Do not hide focus outlines without providing a strong custom focus style.
+
+## Golden Pattern
+
+Structural reference for AI coding assistants — semantics, focus, and keyboard behavior. Styling, copy, and demo data are illustrative.
+
+```jsx
+export function ButtonBasicDemo() {
+  return (
+    <div>
+      {/* Text-only */}
+      <button type="button" onClick={() => alert("Saved")}>
+        Save
+      </button>
+
+      {/* Icon + text */}
+      <button type="button" onClick={() => alert("Downloaded")}>
+        <span aria-hidden="true">[icon]</span> Download
+      </button>
+
+      {/* Icon-only (must have accessible name) */}
+      <button
+        type="button"
+        aria-label="Open settings"
+        onClick={() => alert("Settings")}
+      >
+        <span aria-hidden="true">[icon]</span>
+      </button>
+
+      {/* Disabled */}
+      <button type="button" disabled onClick={() => alert("Won't fire")}>
+        Disabled
+      </button>
+    </div>
+  );
+}
+```
+
+## Acceptance Checks
+- Tab to the button: a visible focus indicator is present.
+- Press Space or Enter: the button activates.
+- Text-only button: screen reader announces the visible label.
+- Icon+text button: screen reader announces the text label (icon is not redundantly announced).
+- Icon-only button: screen reader announces the `aria-label` (e.g., "Open settings").
+- Disabled button:
+  - Cannot be activated by click/keyboard.
+  - Is not focusable when `disabled` is set.

package/corpus/web/react/components/button.toggle.md

@@ -0,0 +1,109 @@
+---
+id: button.toggle
+title: Toggle Button
+stack: web/react
+status: beta
+latest_version: 0.2.1
+tags: [button, toggle, pressed, aria-pressed, mute-button]
+aliases: [toggle button, pressed button]
+summary: Two- or three-state button that toggles between pressed and not pressed using aria-pressed.
+---
+
+# Toggle Button
+
+Pattern ID: `button.toggle`
+
+Two- or three-state button that toggles between pressed and not pressed using `aria-pressed`.
+
+## Use When
+- Use when a control toggles a feature or action within the current context (e.g., "Mute", "Bold", "Pin", "Enable Closed Captioning").
+
+## Do Not Use When
+- Do not use when the control navigates to a new URL (use `link`).
+- Do not use when the control represents a persistent on/off system or application setting, such as "Enable notifications", "Dark mode" (use `switch.basic`).
+- Do not use when the control records a value to submit with a form rather than toggling something in the current context (use `checkbox.basic`).
+- Do not use when the control opens a menu (use `menu.basic`).
+
+## Must Haves
+- Use a native `<button>` element for built-in semantics and keyboard behavior.
+- The button has an accessible name that describes its purpose or action.
+- Default strategy: represent state by changing the accessible name to the next action (e.g., "Mute" ↔ "Unmute", "Pin" ↔ "Remove pin").
+- When the button has visible text, the visible text serves as the accessible name.
+- When additional context is needed beyond the visible text, add it via `aria-label`, `aria-labelledby`, or offscreen text. The visible text appears at the start of the accessible name.
+- For icon-only buttons, provide an accessible name using `aria-label` or `aria-labelledby`.
+- Icons within buttons must be decorative (`aria-hidden="true"`).
+- If the action is unavailable, disable the button using the native `disabled` attribute. (It becomes unfocusable and non-interactive.)
+- Ensure a visible focus state (e.g., a 2px solid outline offset by 1-2px) around the button.
+
+### Formatting toolbar exception
+- If the control is a formatting toggle in a toolbar (e.g., Bold/Italic/Underline), use aria-pressed="true|false" to reflect whether formatting is currently applied.
+- In this toolbar case, keep the accessible name stable (e.g., "Bold") and do not rename it to "Remove bold" or "Unbold".
+
+## Customizable
+- For most toggles (non-toolbar), you may express "next action" via:
+  - Visible text (preferred when space allows), and/or
+  - `aria-label` / `aria-labelledby` (required for icon-only).
+- You may add context to the accessible name when multiple similar toggles exist (e.g., "Mute Trailer", "Unmute Trailer") using `aria-label`, `aria-labelledby`, or offscreen text.
+
+## Don'ts
+-   Do not use `aria-pressed` for non-toolbar toggles **if** you are already changing the accessible name to the next action (avoid conflicting models like "Unmute, pressed").
+- Do not leave `aria-pressed` incorrect, stale, or always `"true"` / always `"false"` when you choose the toolbar approach.
+- Do not ship icon-only toggles without an accessible name (`aria-label` or `aria-labelledby`).
+- Do not put state only in the icon (screen reader users must get state via the accessible name change or `aria-pressed`, depending on strategy).
+
+## Golden Pattern
+
+Structural reference for AI coding assistants — semantics, focus, and keyboard behavior. Styling, copy, and demo data are illustrative.
+
+```jsx
+export function ToggleButtonDemo() {
+  const [muted, setMuted] = useState(false);
+  const [iconOnlyMuted, setIconOnlyMuted] = useState(false);
+  const [pinned, setPinned] = useState(false);
+  const [bold, setBold] = useState(false);
+
+  return (
+    <div>
+      <p>Toggle state indicated by accessible name change</p>
+
+      <button type="button" onClick={() => setMuted((v) => !v)}>
+        <span aria-hidden="true">[icon]</span>{" "}
+        {muted ? "Unmute" : "Mute"}
+      </button>
+
+      <button type="button" onClick={() => setPinned((v) => !v)}>
+        <span aria-hidden="true">[icon]</span>{" "}
+        {pinned ? "Unpin" : "Pin"}
+      </button>
+
+      <button
+        type="button"
+        onClick={() => setIconOnlyMuted((v) => !v)}
+        aria-label={iconOnlyMuted ? "Unmute" : "Mute"}
+      >
+        <span aria-hidden="true">[icon]</span>
+      </button>
+
+      <hr />
+
+      <p>Toggle state indicated by aria-pressed (toolbar formatting)</p>
+
+      <button
+        type="button"
+        aria-pressed={bold ? "true" : "false"}
+        onClick={() => setBold((v) => !v)}
+      >
+        <span aria-hidden="true">[icon]</span>{" "}
+        Bold
+      </button>
+    </div>
+  );
+}
+```
+
+## Acceptance Checks
+- Keyboard activation
+  - Tab to each control: a visible focus indicator is present.
+  - Press Space or Enter: the control activates/toggles.
+- Either the button's accessible name adjusts to reflect its state (preferred), or it remains constant and the value of `aria-pressed` reflects its state
+- Icons are not announced (decorative via `aria-hidden="true"`).