Tag
composite-widgets
- Aug 17, 2026 Roving tabindex and aria-activedescendant as Competing Models Two ways to keep one tab stop inside a composite widget: moving real DOM focus between items, or holding focus on a container and pointing at an item. Their costs differ in event routing, virtualisation, and IME handling. accessibility
- Jul 30, 2026 Keeping Focus Stable in Virtualized and Reordered Lists Why windowing libraries lose focus when they recycle nodes, how sorting a list breaks a tab stop, and what content-visibility does to the focusability of skipped subtrees. accessibility
- Jul 4, 2026 Custom Widgets Over Virtualized Content When only the visible window of a list exists in the DOM, the accessibility tree holds a fragment of the data. Position, size, and the active item have to be reported through attributes rather than structure. accessibility
- Jul 3, 2026 The Combobox Popup Contract: Ownership, Focus, and Announcement What a text input and its suggestion list must agree on to be one widget: the popup relationship, where DOM focus lives during typing, and who announces the active option. accessibility
- Mar 8, 2026 Roving tabindex and Active Descendant Compared Two ways to give a composite widget one tab stop: moving tabindex among items, or keeping focus on a container and pointing at an item with aria-activedescendant. accessibility
- Jan 26, 2026 Container Roles and Nested Structure How group, region, and composite containers nest, what nesting does to landmark and heading navigation, and when a wrapper should carry a role at all. accessibility