FAQ sections
Group common questions into a readable native disclosure layout.
Live preview
Frequently asked questions
Does it require npm?
No. Include the distributed local assets directly.
Can I customize colors?
Yes. Override the scoped design tokens.
HTML
<section class="xsh-faq" aria-label="Common questions">
<h3>Frequently asked questions</h3>
<details>
<summary>Does it require npm?</summary>
<p>No. Include the distributed local assets directly.</p>
</details>
<details>
<summary>Can I customize colors?</summary>
<p>Yes. Override the scoped design tokens.</p>
</details>
</section>Installation & markup
Include the local stylesheet and script once on the page, then place the component inside a data-xsh-ui root. The example above works without a build system.
<link rel="stylesheet" href="/dist/xshna-ui.css">
<div data-xsh-ui>
<!-- Add the HTML example above -->
</div>
<script defer src="/dist/xshna-ui.js"></script>Component API
Public classes, attributes and hooks used by this example. Keep the xsh- prefix intact.
| Identifier | Contract |
|---|---|
xsh-faq | Used by the example markup and component styles or behavior. |
details | Used by the example markup and component styles or behavior. |
summary | Used by the example markup and component styles or behavior. |
Accessibility & keyboard
Each question expands with native Enter/Space and exposes its expanded state.
Implementation note. Use short answers and link to longer guides where appropriate.
Interaction contract
Behavioral components use the shared delegated runtime; visual-only primitives rely on semantic HTML and CSS. Runtime controls emit bubbling xsh:* CustomEvents; bind application handlers to those events when server persistence, API data or navigation is required.