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

#nav-above conflicts with skip-to-content link in the primary menu #148

Closed
mfields opened this issue Feb 2, 2013 · 4 comments
Closed

#nav-above conflicts with skip-to-content link in the primary menu #148

mfields opened this issue Feb 2, 2013 · 4 comments

Comments

@mfields
Copy link
Contributor

mfields commented Feb 2, 2013

#136 suggests the use a bit of javascript for an a11y enhancement. While testing the code, I Noticed that the "skip to content" link does not technically skip to the content. The goal of this link is to allow users to bypass the top navigation menu. When this link is clicked, visual focus is given to #content. But the first thing we find inside #content is another nav element.

The easiest solution is removal, but I know that a lot of themes currently use post-level navigation above the loop.

Another solution would be to reword the markup moving the posts-nav outside of #content.

What do you think?

@obenland
Copy link
Member

I'm in favor of removing nav above - hardly any newer theme uses it (might be subjective). It would also simplify _s_content_nav().

@lancewillett
Copy link

I'm also in favor of removing top navigation.

@iamtakashi
Copy link
Contributor

Agreed with @obenland and @lancewillett I don't use nav above because It's an awkward element to make a theme look nice with :)

@mfields
Copy link
Contributor Author

mfields commented Feb 27, 2013

Thanks! I'll get started on nav removal.

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

4 participants