makeup-active-descendant
Implements ARIA active descendant keyboard navigation.
Experimental
This module is still in an experimental state, until it reaches v1 you must consider all minor releases as breaking changes.
Example 1: Programmatic Relationship
In this example the focusable element is not an ancestor of the "descendant" elements. The module will add aria-owns
to create a programmatic relationship between the two elements. This is typical of a combobox or date-picker type pattern.
Starting markup:
<div class="widget">
<input type="text">
<ul>
<li>Item 1</li>
<li>Item 2</li>
<li>Item 3</li>
</ul>
</div>
import * as ActiveDescendant from 'makeup-active-descendant';
const widgetEl = document.querySelector('.widget');
const focusEl = widgetEl.querySelector('input');
const containerEl = widgetEl.querySelector('ul');
const activeDescendant = ActiveDescendant.createLinear(widgetEl, focusEl, containerEl, 'li');
widgetEl.addEventListener('activeDescendantChange', function(e) {
console.log(e.detail);
});
Markup after instantiation:
<div class="widget" id="widget-0">
<input type="text" aria-owns="widget-0-list-0">
<ul id="widget-0-list-0">
<li id="widget-0-item-0" data-makeup-index="0">Item 1</li>
<li id="widget-0-item-1" data-makeup-index="1">Item 2</li>
<li id="widget-0-item-2" data-makeup-index="2">Item 3</li>
</ul>
</div>
Markup after pressing down arrow key on focusable element:
<div class="widget" id="widget-0">
<input type="text" aria-activedescendant="widget-0-item-0" aria-owns="widget-0-list-0">
<ul id="widget-0-list-0">
<li class="active-descendant" id="widget-0-item-0" data-makeup-index="0">Item 1</li>
<li id="widget-0-item-1" data-makeup-index="1">Item 2</li>
<li id="widget-0-item-2" data-makeup-index="2">Item 3</li>
</ul>
</div>
Use CSS to style the active descendant however you wish:
.widget .active-descendant {
font-weight: bold;
}
Example 2: Hierarchy Relationship
In this example the focusable element is an ancestor of the list items and therefore the "descendant" relationship can be automatically determined from the DOM hierarchy. This is typical of a standalone listbox or grid widget.
NOTE: this module does not add any ARIA roles; only states and properties.
Starting markup:
<div class="widget">
<ul tabindex="0">
<li>Item 1</li>
<li>Item 2</li>
<li>Item 3</li>
</ul>
</div>
import * as ActiveDescendant from 'makeup-active-descendant';
const widgetEl = document.querySelector('.widget');
const focusEl = widgetEl.querySelector('ul');
const containerEl = focusEL;
const activeDescendant = ActiveDescendant.createLinear(widgetEl, focusEl, containerEl, 'li');
widgetEl.addEventListener('activeDescendantChange', function(e) {
console.log(e.detail);
});
Markup after instantiation:
<div class="widget" id="widget-0">
<ul id="widget-0-list-0" tabindex="0">
<li id="widget-0-item-0" data-makeup-index="0">Item 1</li>
<li id="widget-0-item-1" data-makeup-index="1">Item 2</li>
<li id="widget-0-item-2" data-makeup-index="2">Item 3</li>
</ul>
</div>
Markup after pressing down arrow key on focusable element:
<div class="widget" id="widget-0">
<ul id="widget-0-list-0" aria-activedescendant="widget-0-item-0" tabindex="0">
<li class="active-descendant" id="widget-0-item-0" data-makeup-index="0">Item 1</li>
<li id="widget-0-item-1" data-makeup-index="1">Item 2</li>
<li id="widget-0-item-2" data-makeup-index="2">Item 3</li>
</ul>
</div>
Use CSS to style the active descendant however you wish:
.widget .active-descendant {
font-weight: bold;
}
Options
activeDescendantClassName
: the HTML class name that will be applied to the ARIA active descendant element (default: 'active-descendant')autoInit
: specify an integer or -1 for initial index (default: 0) (see makeup-navigation-emitter
)autoReset
: specify an integer or -1 for index position when focus exits widget (default: null) (see makeup-navigation-emitter
)autoScroll
: Specify true to scroll the container as activeDescendant changes (default: false)axis
: specify 'x' for left/right arrow keys, 'y' for up/down arrow keys, or 'both' (default: 'both')ignoreButtons
: if set to true, nested button elements will not trigger navigationModelChange events. This is useful in a combobox + button scenario, where only the textbox should trigger navigationModelChange events (default: false)
Custom Events
Properties
filteredItems
: returns filtered items (e.g. non-hidden items)index
: the index position of the current active descendantitems
: returns all items that match item selector
Methods
destroy
: destroys all event listenersreset
: will force a reset to the value specified by autoReset
Dependencies