Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Search Box accessibility issues #1483

Closed
claycompton opened this issue Aug 17, 2013 · 2 comments
Closed

Multiple Search Box accessibility issues #1483

claycompton opened this issue Aug 17, 2013 · 2 comments
Assignees

Comments

@claycompton
Copy link

Keyboard and mouse experience on receiving focus are inconsistent in new search box

To repro, follow these steps.
1. Type text in the textbox.
2. Click outside the box to make it lose focus.
3. Click inside the box to restore focus.

RESULT: The box won't immediately expand. It will do so only if you type additional content.
EXPECTED: if you use the keyboard to tab or shift-tab back to the box, it will expand immediately on receiving focus. We should be consistent between these two modalities.

Accessibility (WCAG level A): Change of tab order when tabbing into and out of new search box.

To reproduce this, follow these steps:

  1. Navigate to http://qa.nugettest.org/.
  2. Using only the keyboard, tab to the search box. Notice that each of the links in the navigation bar are tab stops.
  3. While focus is on the search box, press the space bar (to force the search box to expand)
  4. Press Shift-Tab to leave the search box.

RESULT: Focus will move to one of the account buttons (either Register or Log Off), not the buttons in the navigation bar.
EXPECTED: We shouldn't have unexpected changes in focus order, which will confuse blind users. In this case, Shift-Tab ought to move focus to the Blog link in the navigation bar.

@analogrelay
Copy link
Contributor

I think we have some other keyboard focus issues, so I'd say we can ship with out this, but as with the others, I'll take a look when I get back. I do want to get it fixed, but I figure it's easier for me to just pop on and do it when I get back then to pull devs off other things :).

@analogrelay
Copy link
Contributor

NOTE: The fix for this will also fix #1486

analogrelay added a commit that referenced this issue Sep 9, 2013
Fix #1483 by tweaking hide/unhide techinque for menu.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants