inclusive-elements

Native HTML first, with runtime only where the platform still benefits from help.

Each section answers the same question: if you need this pattern today, what is the recommended implementation path with modern HTML plus `inclusive-elements` where it still adds value?

Disclosure

Recommended implementation: native <details> and <summary>.

Shipping information

Ships in 2–3 business days.

Accordion

Recommended implementation: grouped native <details name> elements.

Returns

30 day returns.

Warranty

Two years included.

Menu

Recommended implementation: a native popover surface plus ui-menu for arrow-key navigation, typeahead, submenu behavior, and horizontal popup menus such as reaction pickers.

Popover

Recommended implementation: native popover with CSS anchor positioning.

This pattern no longer needs a library wrapper. Use the platform directly.

Combobox

Recommended implementation: ui-combobox to progressively enhance native source controls while keeping their form behavior.

Choose one option.

Type to filter, then select several.

Choose a suggestion or enter another city.

Tooltip

Recommended implementation: a native hint popover plus ui-tooltip as an adjacent sibling, with optional for when you need an explicit target.

Save changes Create a shareable link

Dialog

Recommended implementation: native <dialog> for modality and focus management.

Native dialog

Focus handling and dismissal are handled by the browser.

Alerts

Recommended implementation: ui-alerts when the platform still needs runtime help for announcement orchestration and timed dismissal.

Tabs

Recommended implementation: ui-tabs to connect tab selection, keyboard navigation, and panel visibility.

Current plan: Pro. Renewal date: April 24.

Toolbar

Recommended implementation: ui-toolbar when a row of controls should use arrow keys for focus movement.