Accordion
Overview
Accordion is a design-system component intended for reusable, product-agnostic UI composition.
Import
import { Accordion, AccordionItem, AccordionTrigger, AccordionContent } from "@tesseract-nexus/tesserix-ui"Exports
export { Accordion, AccordionItem, AccordionTrigger, AccordionContent } from './accordion'
export type { AccordionProps, AccordionItemProps, AccordionTriggerProps, AccordionContentProps } from './accordion'Props
export interface AccordionProps extends React.HTMLAttributes<HTMLDivElement> {
type?: "single" | "multiple"
defaultValue?: string | string[]
collapsible?: boolean
}
export interface AccordionItemProps extends React.HTMLAttributes<HTMLDivElement> {
value: string
}
export interface AccordionTriggerProps extends React.ButtonHTMLAttributes<HTMLButtonElement> {
value: string
}
export interface AccordionContentProps extends React.HTMLAttributes<HTMLDivElement> {
value: string
}Variations
No explicit cva variant map found. Variations are primarily structural/compositional for this component.Usage Patterns
Basic
import { Accordion, AccordionItem, AccordionTrigger, AccordionContent } from "@tesseract-nexus/tesserix-ui"
export function Example() {
return <Accordion />
}Do / Don’t
Do
// Compose with domain wrappers in product code
<Accordion className="w-full" />Don’t
// Avoid one-off hardcoded values that bypass tokens
<Accordion className="bg-[#123456] text-[#fafafa] px-[13px]" />Token / Theming Mapping
- Color tokens: —primary, —secondary, —muted, —destructive, —foreground, —background
- Shape tokens: —radius
- Border/input tokens: —border, —input, —ring
- Spacing and typography: Tailwind scale via design-system preset
Interaction Test Checklist
- Interaction: click/keyboard activation for primary paths.
- Focus: visible focus styles and logical tab order.
- Variants: core variants and sizes render correctly.
- Disabled/error states: behavior and ARIA attributes are correct.
- Regression: Storybook visual check for primary states.
Accessibility
- Verify keyboard behavior for all interactive states.
- Ensure labels and semantic roles are present in consuming screens.
- Validate focus treatment and screen-reader output during QA.