Accessibility

Combric

Combric starts from native elements and adds behavior only where the platform does not supply the required composite pattern.

Framework contracts

• Native inputs, buttons, links, tables, progress, fieldsets, labels, and select controls retain platform semantics.
• Focus-visible styling uses the canonical focus token.
• Controlled values remain authoritative; uncontrolled variants own only their initial local state.
• Field descriptions and mounted messages compose aria-describedby without dangling IDs.
• Modal overlays isolate background content, cycle focus, close on Escape, and restore trigger focus.
• Menus, tabs, toggle groups, and disclosure controls document their keyboard behavior on their component pages.
• Live-region behavior is explicit rather than automatically attached to all feedback.
• Spinner and Skeleton animation stops when reduced motion is requested.

Consumer responsibilities

Consumers remain responsible for meaningful names, labels, heading order, validation logic, announcement timing, link destinations, table content, color combinations, and application-level focus after navigation.

Automated DOM assertions, Playwright behavior, and axe scans catch only part of the accessibility surface. They do not establish WCAG certification or conformance.

Automated regression matrix

The documentation browser suite exercises the real catalogue examples for Accordion, Checkbox, RadioGroup, Switch, Slider, Select, Tabs, Dialog, Drawer/Sheet, DropdownMenu, Popover, Tooltip, Toast, Toggle, and ToggleGroup. It combines axe scans with component-specific keyboard, focus, state, naming, and dismissal assertions where applicable. Modal focus trapping and restoration also have focused component tests. This is regression coverage, not a complete audit of a consumer application or a WCAG conformance claim. The release gate also checks the landing page, versioned documentation, catalogue, accessibility guide, search, and current Playground in desktop and mobile Chromium under light, dark, and system color preferences. Mobile checks include navigation, search, overlay dismissal, responsive overflow, and the Playground; they do not certify the accessibility of a consuming application.

Combric Guard checks static package, CSS, and token integration. It does not evaluate runtime accessibility behavior.