Standards alignment

This page is generated from the ## N. Standards Alignment tables in the specifications and from scripts/docs/standards.json . The conformance vocabulary and the rules for citing a standard live in specs/standards.md . Regenerate with bun run docs:generate ; the rows are checked by bun run docs:standards .

Conformance at a glance

Standards Jx implements

Tracked gaps

Near

• gap:ui-aria — Accessible Rich Internet Applications (WAI-ARIA) 1.2 (WAI-ARIA, Subset ) in ui.md §5, ui.md §6, ui.md §7 — Built and exercised: menu (roving tabindex , typeahead, submenus as child popovers), toolbar and radiogroup ( jx-action-group 's selects ), tablist ( jx-tabs , roving focus, aria-selected , aria-controls ), dialog ( jx-dialog , a native modal), switch , separator , progressbar ( jx-spinner , an empty value writing no aria-valuenow ), tooltip , and tree ( jx-tree and jx-tree-item : the roving caret, aria-level , aria-expanded , aria-multiselectable , and aria-posinset / aria-setsize describing the FULL set while the tree draws a windowed slice of it). conformance.test.ts runs an accessibility lint over every kit document, so a new element joins the claim rather than sitting outside it. listbox ( jx-listbox and jx-option , with the active descendant and the selection as one row) and the editable combobox with list autocomplete ( jx-combobox ) are built as well. Absent: the select-only combobox kind , which is a native <select> here (§5.1). Three deviations are normative and are the reason this is not Adopted on the menu pattern alone: a menu row that owns a submenu still runs its own command (§5.1), a tree's arrows do not wrap where the menu's and the tablist's do (§5.5), and a jx-listbox has no tab stop of its own even when nothing else on the surface owns its keyboard — the slash menu's caret is in the canvas, and a focusable list would take it (§5.3).

• gap:wcag-conformance — Web Content Accessibility Guidelines (WCAG) 2.2 (WCAG 2.2, Subset ) in studio-ui-guidelines.md §1.1, studio-ui-guidelines.md §8.2, studio-ui-guidelines.md §8.7 — No level is claimed, and conformance is not tested end to end — that needs a browser. Four criteria are met deliberately and checked: SC 4.1.3 (Status Messages) — one live region, called from notify() itself, so a failure that lands in the Problems panel is still announced; SC 2.5.7 (Dragging Movements) — cut/paste is the stated alternative to every drag; SC 1.4.3/1.4.11 (Contrast) — a required-pairs table gated in check-styles.ts , with one entry on the debt list; SC 1.4.1 — a forced-colors block redraws the selection and focus affordances Windows High Contrast deletes with box-shadow .

• gap:ui-wcag — Web Content Accessibility Guidelines (WCAG) 2.2 (WCAG 2.2, Subset ) in ui.md §4, ui.md §5, ui.md §7 — No level is claimed, and conformance is not tested end to end — that needs a browser. Seven criteria are met deliberately, an eighth is met for the control height, and each has a test: SC 2.4.7 (Focus Visible) — every element that renders a focusable control declares a :focus-visible rule on the one --jx-focus-ring token, held by conformance.test.ts ; SC 2.1.1 (Keyboard) — every composite's keyboard contract is exercised ( menu , jx-tree , toolbar , tabs , split , combobox , color-area ); SC 2.5.7 (Dragging Movements) — the splitter's arrows and Enter collapse ( split.test.ts ) and the colour area's arrow keys ( color-area.test.ts ) are the non-drag alternative; SC 2.3.3 (Animation from Interactions) — the theme zeroes every --jx-dur-* under prefers-reduced-motion: reduce ( theme.test.ts ); SC 2.2.1 (Timing Adjustable) — the toast's clock pauses on pointer and on focus and resumes with what was left ( jx-toast.test.ts ); SC 1.4.13 (Content on Hover or Focus) — the tooltip is hoverable, dismissible and persistent ( tooltip.test.ts ); SC 1.4.3/1.4.11 (Contrast) — Studio's required pairs over the kit's tokens are gated per scheme in check-styles.ts , which is the one criterion whose evidence lives outside this package. SC 2.5.8 (Target Size, Minimum) for the control height and for sm — every --jx-control-h -sized control is at least 24px at every density, and every sm button and checkbox accepts the pointer over the same token through a ::before hit area inset past its 20px picture, both held by conformance.test.ts and the arithmetic by target-size.test.ts (compact used to draw 20px rows, which is why this row once claimed nothing for the criterion; §4.3 records the floor, what compact buys instead, and the hit-area technique); jx-textfield 's clear button and jx-combobox 's toggle carry the same hit area at every field size; jx-number-field 's steppers fall under the criterion's Equivalent exception at md and lg , where the input beside them takes the same step at the floor; a small number field is the non-claim below, its input included. What is not claimed: SC 2.5.8 for a small FIELD — an sm jx-textfield , jx-number-field , jx-select or jx-combobox draws its native input 4px under the floor and a replaced element renders no pseudo-element to extend it, so a host owes those the criterion itself; the members of a jx-action-group on its packed axis — 22px each but the last at the default 2px gap, where the later sibling's extension paints over the earlier one's and the overlap rule gives it the strip, and the drawn width in a compact group, where the boxes touch and the sheet zeroes the extension rather than let it cover the neighbour (a jx-toolbar 's 4px gap is where two extended neighbours abut, and there the claim holds); and jx-split 's 5px handle, whose 24px strip would cover the panes it divides (§4.3 records the trade-off); and SC 4.1.2 beyond what the accessibility lint refuses (an interactive node with no name). The busy-indicator exemption §5.2 records is deliberate and is stated there.

• gap:ui-html-overlays — HTML Standard (WHATWG HTML, Subset ) in ui.md §3, ui.md §6 — Built and exercised: popover in auto ( jx-menu , jx-popover ) and hint ( jx-tooltip ) with light dismissal, Escape one level and Tab-hides-root; <dialog> opened with showModal() , so inertness, focus restoration and closedby are the platform's; invoker commands , including the custom --show a host aims at a jx-dialog ; autofocus , forwarded by jx-button to its inner control; and ToggleEvent , which is what a dialog's open is mirrored from rather than written. Absent: popover="manual" , which no element needs yet, and inert written by the kit itself — a modal <dialog> supplies it, and nothing else here claims it. Form association through ElementInternals is not offered and is not a gap: §3.2 records it as a decision, so a host restoring a default writes value .

Untiered

These bind a section carrying no status marker, so no tier can be derived.

• gap:apg-coverage — Accessible Rich Internet Applications (WAI-ARIA) 1.2 (WAI-ARIA, Subset ) in studio-ui-guidelines.md §6, studio-ui-guidelines.md §8, studio-ui-guidelines.md §12 — The tree, menu, toolbar and radiogroup patterns are implemented with their full state and keyboard contracts, and two more now are: the combobox (Quick Access carries aria-controls , aria-activedescendant and an aria-expanded that is false when nothing matched — it was the literal string true ) and the dialog ( role , aria-modal and a name off the wrapper's headline). Every tab strip in the shell carries real tablist / tab / tabpanel semantics ( jx-tabs ), the PANE strip included. Both trees are jx-tree now , which is the same correction one level down: the Outline and the Files tree each wrote out role="tree" , role="treeitem" , aria-level , aria-posinset , aria-setsize , a roving tabindex and their own arrow-key cases, and nothing held the two copies in agreement — ← climbed to a parent in one and only closed a directory in the other, Home and End existed in one and not the other, and neither had typeahead. The element owns all of it and both trees gained the half they were missing; what the panels keep is the half a windowed tree cannot delegate, because the DOM holds a slice: the counts describe the full set, a caret move past the drawn rows comes back as move , and ← climbs to the parent the ROW MODEL recorded rather than to the nearest painted row at a shallower level. It was the last one out, because a Studio tab chip carries a pin toggle, an origin marker and a draft pill and jx-tab accepted no slotted content; the gap was one <slot> in the kit's element rather than a missing keyboard contract, and closing it took three ( ui.md §5.4, slots icon , status and actions ). The chip keeps all three marks and is a tab inside a tablist : one stop in the tab order with a roving caret inside it, arrows with wrap, Home and End, and Delete closing a document — a path the × had never had, and the reason this gap was worth closing in the element rather than around it. The Tabulator data grid is virtualized — hand-authoring role="grid" over rows that do not exist in the DOM would make it worse, not better. One deviation from the menu pattern is deliberate and is recorded in §8.4: the rail foot's Settings menu gives a row that owns a submenu an action of its own , which the APG does not describe. It is the requirement rather than an oversight — the heading opens the surface and the submenu deep-links a section — and it is why these menus were hand-rolled before the kit had one: Spectrum's stock slot="submenu" forbade it outright. Nothing is unreachable: Enter runs the row, ArrowRight reaches every child, aria-haspopup announces the popup, and every child has a second door.

Declined

Adoption backlog

Standards whose owning spec section does not exist yet, so no row can bind them. Each names the spec that will own it; when that section is written the entry becomes a tracked gap.

Standards catalog

Every identifier a specification may cite, with the canonical URL the citation must use.