Skip to Content
ComponentsCheckbox

Checkbox

Overview

Checkbox is a design-system component intended for reusable, product-agnostic UI composition.

Import

import { Checkbox } from "@tesseract-nexus/tesserix-ui"

Exports

export { Checkbox } from './checkbox' export type { CheckboxProps } from './checkbox'

Props

export interface CheckboxProps extends Omit<React.InputHTMLAttributes<HTMLInputElement>, 'type'> {} const Checkbox = React.forwardRef<HTMLInputElement, CheckboxProps>( ({ className, ...props }, ref) => { return ( <input type="checkbox" className={cn( "peer h-5 w-5 shrink-0 rounded border-2 border-input bg-background shadow-sm transition-all duration-200", "focus-visible:outline-none focus-visible:ring-4 focus-visible:ring-ring/20", "checked:bg-primary checked:border-primary checked:text-primary-foreground", "disabled:cursor-not-allowed disabled:opacity-50", "cursor-pointer", className )} ref={ref} {...props} /> ) } ) Checkbox.displayName = "Checkbox" export { Checkbox }

Variations

No explicit cva variant map found. Variations are primarily structural/compositional for this component.

Usage Patterns

Basic

import { Checkbox } from "@tesseract-nexus/tesserix-ui" export function Example() { return <Checkbox /> }

Do / Don’t

Do

// Compose with domain wrappers in product code <Checkbox className="w-full" />

Don’t

// Avoid one-off hardcoded values that bypass tokens <Checkbox 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

  1. Interaction: click/keyboard activation for primary paths.
  2. Focus: visible focus styles and logical tab order.
  3. Variants: core variants and sizes render correctly.
  4. Disabled/error states: behavior and ARIA attributes are correct.
  5. 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.