Accessibility: pf wizard buttons are inaccessible via keyboard navigation

[benjaminapetersen]

via issue 406 in web console.

You cannot tab through the wizard content & then access the cancel, next buttons.

• button is not actually a button, it is just a node styled like a button w/o a tabindex.
• you can also tab through content below the modal (on the page) while the modal is open.

[jeff-phillips-18]

Thanks @benjaminapetersen , would you like to contribute the solution?

[benjaminapetersen]

If I take a stab at it, it looks like each of the components in src/wizard/wizard-buttons.js need a template with a real button element. That is prob not too hard.

To fix the tab issue with content under the modal, I would tend toward keeping track of the 1st and last "tabbable" item in the modal, add a keyup or keydown handler to the last & set focus on the first if e.which === 9 && !e.shiftKey. What could get a little ugly there is querying child view for the steps & updating the first element reference. Using require may be cleaner...

Thoughts? Reasonable direction?