* Make sure the language doesn't assume controls are buttons.
(i.e. change Tab moves focus to the first enabled toolbar button. & Left Arrow and Right Arrow keys navigate to the enabled buttons in the toolbar)

* Add some language about elements which consume left/right arrow in the toolbar. Something about "avoid them" but if really have to add them then add ways to mitigate their usage.

* Change text about shortcut keystroke to talk about "application level toolbar" or toolbar "relevant to current context". We should not encourage unique keystrokes to every toolbar in the page.

Disabled element discussion:
"In general disabled elements are not included in the focus sequence but there may be some circumstances where discoverability of a function is crucial and an author may choose to include them in the navigation sequence."

(delete the rest of the conversation about disabled buttons)

WAI-ARIA Roles, States, and Properties:
Delete - 
* The children of the toolbar are frequently elements with role button.
* Other tools that are common within toolbars are comboboxes and pull-down menus.

Modify 
* It is recommended that a toolbar is labelled using aria-label.

To
* It is recommended that a toolbar is labelled especially if there is more than 1 toolbar

Keyboard Interaction Section.

Change first bullet to

* The listbox element is focusable. See Keyboard Navigation between Widgets.

(In reply to James Nurthen from comment #6)
> Keyboard Interaction Section.
> 
> Change first bullet to
> 
> * The listbox element is focusable. See Keyboard Navigation between Widgets.

Please ignore this comment. Wrong bug.

Add orientation and kb information for orientation

All changes complete and merged into master.