Right now, the "skip to nav" link points to a hard-coded spot in the page.tpl.php and that causes issues when moving stuff around in page.tpl.php. See also the problems with #255265: Don't "skip to nav" if there's no nav.

So I was thinking we could add an interface like custom breadcrumbs for adding links to the skip to nav div.

One textarea specifying one link text per line. And one textarea specifying one path per line (corresponding to the lines in the "link text" textarea.

Comments

yoroy’s picture

Status: Active » Postponed (maintainer needs more info)

Can't really visualize what this interface looks like (a bit like adding paths to block visibility settings?), but how often do these problems occur and does that warrant a UI to be made for it?

JohnAlbin’s picture

Title: Make "skip to nav" links configurable instead of hard-coded » Add page navigation links by expanding "skip to nav" idea
Status: Postponed (maintainer needs more info) » Active

Hmm… I had jumped straight to describing my solution without explaining the problem. I hate when people do that. :-p

So, basically, "Skip to nav" is useful as a page navigation link, but only when you have your primary navigation in the div#navbar. Since a particular graphic design can change the location of the site navigation, the hard-coded "skip to nav" link is easy to break. And often themer don't notice its broken; which is even worse.

A working "skip to nav" is useful, but what would probably be much more useful is a short list of page navigation links that appear at the top of the page. “Jump to: content, site navigation, section navigation, search, etc.”

So we have 2 options that I can see:

1. We could continue to hard-code the page navigation links. And if the graphic design requires the site navigation to not be in the div#navbar, the themer would still have to know that the page.tpl.php has to be copied/overridden/modified in the sub-theme. That only marginally improves things for the themers.

2. What I was trying to describe in the initial issue posting above was a way to add multiple links to the top of the page.tpl.php by using a theme setting widget. You would specify the link text and the anchor you would like each link text to go to. And by putting it into the theme settings form, it would be more likely the themer would become aware of the page navigation links.

Which ever method we decide to go with (1 or 2 above), we can also improve the themers' awareness of page navigation links by implementing #308254: Make "skip to nav" styling more useful and less intrusive.

JohnAlbin’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev
JohnAlbin’s picture

Component: Code » CSS/HTML Markup
Status: Active » Closed (won't fix)

what would probably be much more useful is a short list of page navigation links that appear at the top of the page. “Jump to: content, site navigation, section navigation, search, etc.”

Actually, what's most useful is H* tags associated with each main part of the page. Accessibility software can use the headings to navigate easily. A long list of page navigation links is therefore redundant.

However, a single "jump to navigation" or "jump to content" link is still useful. But instead of linking to a hard-coded anchor link, over in #308254: Make "skip to nav" styling more useful and less intrusive I made the "jump to navigation" link go to #main-menu which is the CSS ID associated with the Primary Links menu in the page.tpl. That way if the themer moves that code outside of the navbar, the jump link will still work.

So this issue is pretty much dead.