Improve accessibility for keyboard users

[Rustuma]

Original from Rustum:
Title: "Keyboard navigation. No clear focus states "
Description: "Set focus on buttons or search bars."

---

Update from @techieshark: Changing issue title from "Keyboard navigation. No clear focus states" to "Improve accessibility for keyboard users" (because the issue involves considering now just how the site is navigated visually but how it is navigated by all non-mouse users). From WebAIM:

Keyboard accessibility is one of the most important aspects of web accessibility. Many users with motor disabilities rely on a keyboard. Blind users also typically use a keyboard for navigation. Some people have tremors which don't allow for fine muscle control. Others have little or no use of their hands. Some people simply do not have hands, whether due to a birth defect, an accident, or amputation. In addition to traditional keyboards, some users may use modified keyboards or other hardware that mimics the functionality of a keyboard.

[techieshark]

Using TAB key to navigate, it does seem there are clear focus states. Do you not see this?

(A bigger issue might be that when the JS then moves you to the next "screen", the focus doesn't move to the next input.)

[Rustuma]

Correct- that's what I meant:

[techieshark]

roger that

[Rustuma]

Also - on multi-school list, TAB key doesn't move through the list but rather to the next control:

[reekypete]

Added focus states (blurred outlines) to buttons and anchors

[techieshark]

Note:

• Safari does tabbing differently for links and buttons http://stackoverflow.com/questions/2292016/is-there-a-workaround-to-safaris-operas-bug-that-you-cant-tab-through-hyperli

[Rustuma]

It looks like that was an issue from 2010. Is it still one? How does it work on your Mac, @techieshark ?

[techieshark]

@Rustuma Safari still has that behavior it seems. Hitting Tab when on a button will skip over the next link. However, Option+Tab when on the button will jump to the next selectable item even if that is a link. We can probably assume that the behavior is something Mac users reliant on their keyboard will be used to, so no need to change anything just because of this yet.

[Rustuma]

I would think so.