The application's own Toolbar: base for every use, presets chosen at a
use with preset, and the call over both. mixins concatenate in that
order; a style given at the call replaces the preset's.
The mixins:key-conflict that drawing the toolbar with routes would
throw, or none: the application's routes against the arrows along the
orientation (default 'horizontal'), Home and End, and against each other.
A disabled toolbar still builds its routes, so it throws as well.
The toolbar's own contract: a named, keyboard-navigable root. Its controls
are the caller's, so their roles and activation are theirs; the group and
separator carry only a role.
A toolbar publishes its root, the groups that gather related controls
under a name, and the separator between sets. The controls are the
caller's own elements (a Button, a toggle, a menu's trigger), which the
toolbar hands the attributes of its one tab stop; it adds no markup around
them, so a control keeps the class of its own recipe.
A toolbar in one call, the APG's: role="toolbar" named by label, one tab
stop over its controls, and the arrows along the orientation, Home and End
moving focus between them. The view holds no state; the application keeps
the tab stop (roving, a placed RovingTabindex) so that leaving and
coming back with Tab lands on the control focused last.
A disabled control is skipped by the arrows and takes no focus, as in
Segmented: the APG leaves the choice open, and a focusable disabled
control would stop a keyboard user on something that does nothing. A text
field, a select or a range keeps the keys it uses itself (see usedBy), so
the arrows leave a text field only from the edge they point at, and Home and
End never leave it: place a field last, as the APG advises, or leave it with
Tab. A press that starts in something the toolbar did not draw (a menu's
items) is left to it.