Interactions / Component reference

Accordion

Single or multi-expand disclosures with managed aria-expanded state.

V1 BETA / DOCUMENTEDLive variants · API · Accessibility · Responsive guidance

LIVE COMPONENT REFERENCE

Native disclosure and grouped accordion

Native details/summary is recommended for simpler disclosure. The advanced accordion script is optional.

Actual Xshna CSSResize to test wrapping

What is Xshna.css?

A browser-native, namespaced interface framework.

Does hosting need Node.js?

No. Deploy the compiled CSS and optional JavaScript.

Can I use this with PHP?

Yes. Include the assets in any HTML response.

HTML · COPY AND USE

<div class="xsh-accordion"><details open><summary>What is Xshna.css?</summary><p>A browser-native, namespaced interface framework.</p></details><details><summary>Does hosting need Node.js?</summary><p>No. Deploy the compiled CSS and optional JavaScript.</p></details><details><summary>Can I use this with PHP?</summary><p>Yes. Include the assets in any HTML response.</p></details></div>

Overview

Use xsh-accordion, xsh-accordion-trigger and xsh-accordion-panel; data-xsh-single enforces one panel at a time.

Live example

Interactive · Real framework

No. Upload prebuilt CSS and optional vanilla JavaScript.

Example markup

<div class="xsh-accordion" data-xsh-single>
 <section class="xsh-accordion-item"><h3><button class="xsh-accordion-trigger" aria-expanded="true" aria-controls="xsh-acc-one">Does it require Node.js?</button></h3><div class="xsh-accordion-panel" id="xsh-acc-one">No. Upload prebuilt CSS and optional vanilla JavaScript.</div></section>
 <section class="xsh-accordion-item"><h3><button class="xsh-accordion-trigger" aria-expanded="false" aria-controls="xsh-acc-two">Does it work on shared hosting?</button></h3><div class="xsh-accordion-panel" id="xsh-acc-two" hidden>Yes. No server-side runtime is required.</div></section>
</div>

Production guidance

Accordion triggers must be native buttons within headings. Each button must control its own panel.

Customize this component through --xsh-* CSS tokens, data-xsh-* configuration attributes and documented xsh-* utilities. Use the optional JavaScript distribution only when an interactive behavior is needed.

Build with confidenceOpen interactive design playground →

EXACT NAMES FROM THE SHIPPED STYLESHEETS

Complete selector inventory

These selectors exist in the current distribution. An entry in this table does not imply that arbitrary modifier combinations are meaningful; use the examples above for the intended composition.

Class	Purpose	Delivery
`.xsh-accordion`	Core component	CSS + optional behavior
`.xsh-accordion-item`	Composable modifier / structure class	CSS + optional behavior
`.xsh-accordion-panel`	Composable modifier / structure class	CSS + optional behavior
`.xsh-accordion-trigger`	Composable modifier / structure class	CSS + optional behavior

ENGINEERING AND INTEGRATION

Implementation details

Semantic structure

Use the documented Xshna classes with semantic HTML rather than replacing native elements unnecessarily.

Compose existing xsh- classes on the appropriate HTML element. Keep content order meaningful when CSS is disabled.

Interactive behavior

Verify focus order, disabled behavior and descriptive labels for interactive patterns.

Load xshna.min.js only if the documented interaction needs it. Your application remains responsible for data, persistence and business rules.

Responsive and localization

Test narrow containers, long translations and user-defined text sizes.

Test 320px-wide viewports, container-constrained instances, keyboard zoom, longer translations and right-to-left text where relevant.

Theme and customization

Use --xsh-* CSS variables for theme values and data-xsh-design / data-xsh-density on the xsh-app root.

Prefer design tokens over hard-coded overrides so components remain coherent across personalities.

ACCEPTANCE CHECKLIST

What to verify before shipping

Confirm every documented class used by the feature exists in the release CSS.
Navigate controls using Tab, Shift+Tab, Enter, Space and Escape where appropriate.
Test with reduced motion, high contrast, 200% text zoom and a narrow mobile viewport.
Verify disabled, loading, empty, error and long-content states where relevant.
Check actual application behavior independently of the preview: these examples use illustrative data.