Astryx v0.1.3: better tables, keyboard navigation, and accessibility

bash
npm i @astryxdesign/core@0.1.3

All packages ship together at the same version, so bump every @astryxdesign/* package to 0.1.3 to match.

Tables now support plugin-contributed context menus. Right-click a column header or a row to get real actions — like sort ascending, sort descending, and clear sort — instead of the browser's default menu. Plugins add their own actions through the existing cell transforms, and the table concatenates them across every enabled plugin, so you can extend the menu with no core changes.

TabList, TreeList, Toolbar, SegmentedControl, and menus now follow the WAI-ARIA APG patterns: a single tab stop, arrow-key navigation, Home/End, typeahead, and roving focus. New building blocks — useListFocus, useGridFocus, useTypeahead, useKeyboardHint, and useAnnounce — let you build accessible composite widgets of your own, and a new VisuallyHidden primitive makes it easy to add screen-reader-only context.

Selector, MultiSelector, DateInput, TimeInput, and Typeahead can now sit inside InputGroup with shared labels, descriptions, and connected borders.

Add disabledMessage to choice, picker, and text-entry inputs to show a tooltip telling users why a control is disabled — while keeping it focusable so the explanation is reachable by keyboard.

Stack, Grid, and Center gain padding, sizing, and scroll props, so common frame layouts no longer need inline style={{}}.

New hasLightDismiss and hasEscapeDismiss props let you build explicit-dismiss surfaces like onboarding coachmarks. Layer animations now respect prefers-reduced-motion.

A new Kanban Board template, plus a blog RSS feed and plaintext (.txt) posts.

hasAutoFocus was removed from DropdownMenu, ContextMenu, and MoreMenu. Menus now always focus their first item on open — the correct APG behavior. No migration needed; just delete the prop if you were passing it.

Huge thanks to everyone who contributed this release: @AKnassa, @arham766, @athz, @cixzhang, @durvesh1992, @ejhammond, @ernestt, @harshavardhan194, @humbertovirtudes, @IFAKA, @imdreamrunner, @josephfarina, @kentonquatman, @mohitWeb-lab, @pollychen-lab, and @thedjpetersen.

Also thank you to @aarongarciah for feedback on accessibility, and to @aurorascharff, who drove the work to optimize the docsite on the latest Next.js features.