Better handling of keyboard navigation to be "accessible"?

[patrickhlauke]

As the term "accessible" is being used here, it's worth noting that ideally the modal should handle keyboard navigation a bit better - if it acts as a true modal, users that navigate via keyboard should, after opening the modal, only be able to tab/shift+tab through the links/elements of the modal itself until it's closed. this will require some additional JS to set initial focus into the modal, make sure that focus stays/cycles within the modal itself, and is returned back to the main page after the modal is closed.

[drublic]

Thanks for the comment and thoughts, Patrick.

The modal is focused when opening it. Please see this line and the setFocus function in modal.js. And it works for me. Do you have problems using it?
This implementation doesn't include cycling through the modal though. Do you have any hint on how to enforce cycling through an element?

I tried to focus back on the main page when the modal is closed here. I might have to look into restoring the original focus state on the actual element instead of the body element which happens in Chrome.

An update for the cycling should definitely be implemented.

[drublic]

Ping @patrickhlauke. Would be awesome if you could throw some links at me :) I'd love to include it in the next version.