🍕 Fix tab access in browser

[samccone]

sorta Fixes #104

[marcysutton]

This only goes part of the way there, and it could cause problems as-is. If possible, using tabindex="0" will keep the existing tab order in the page–that makes the collection of tabbable elements much easier to manage. Secondly, tabindex, on what's essentially a fancy div, isn't very useful by itself if there aren't a few key things:

• A button role or native button element, assuming the behavior is button-like.
• Text for a screen reader to know what the button is for. This can be a visually-hidden span or an aria-label, remembering localization requirements (the hardest part IMO).
• A keydown or keypress event, since click won't fire from the keyboard on a custom element.

I like the way you're thinking though, keep it up! 🍕

[samccone]

👍 thx for the protips :) will update

[marcysutton]

Here's a handy keyboard event reference, you can use it to determine which event to use for custom/non-semantic elements: http://unobfuscated.blogspot.com/2013/05/event-handlers-and-screen-readers.html