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.
Foundations / Component reference
Accessibility
Keyboard focus, native HTML semantics, high contrast and reduced-motion defaults.
Overview
Use native buttons, inputs and dialogs, meaningful labels, field errors and structural headings. Xshna supplies styling and interaction patterns, not a guarantee of WCAG certification.
Live example
Interactive · Real frameworkVisible labels remain even when placeholder text disappears.
Example markup
<div class="xsh-stack">
<label class="xsh-label" for="xsh-access-email">Email address</label>
<input class="xsh-input" id="xsh-access-email" type="email" placeholder="[email protected]" aria-describedby="xsh-access-help">
<p class="xsh-help" id="xsh-access-help">Visible labels remain even when placeholder text disappears.</p>
</div>Production guidance
Validate with keyboard, screen reader and contrast tooling on real screens. Use semantic tags, not role additions without the expected behavior.
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 →
Files, tokens and configuration
| Surface | Source of truth | What to check |
|---|---|---|
dist/xshna.min.css | Compiled framework | Styling and responsive behavior |
dist/xshna.min.js | Optional interactions | Lifecycle, event handling and teardown |
src/css/ | Readable source | Public class names and token definitions |
src/contracts/ | Published component contracts where available | State, configuration and behavioral support |
Implementation details
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.
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.