Links
Users often need to navigate through information inside or outside of the application by using links. These links should follow this guideline.
When to Use
- Navigating between pages inside of the application.
- Navigating to pages outside of the application.
- Open a slide-in panel or modal (if a button could not be used)
When Not to Use
When initiating an action or a process
Style
Accessibility
Full Guideline Reference: http://www.w3.org/TR/WCAG10-HTML-TECHS/#links
Links Text
- Clearly identify the target of each link. (Good link text should not be overly general; don't use "click here.")
- Provide a text equivalent for every non-text element
Grouping and Bypassing Links
- Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.
- Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.
Keyboard Access
- Create a logical tab order through links, form controls, and objects.
- Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.
Anchors and Target
- Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.
Usage Examples
Links in forms/body of text that goes to an external page
Breadcrumbs
Guideline:
- Must always locate above the title as shown.
- Not be used if all the pages are on the same level. Breadcrumbs are intended to show hierarchy.
- Show hierarchy and not history. To go back, users use the browser's back button. Replicating this facility defies the purpose of having breadcrumbs.
- Progress from the highest level to the lowest, one step at a time.
- Have a simple link for each level.
- Include the full page title in the breadcrumb trail. Also ensure consistency between the page address and the breadcrumb. If the page titles include keywords, then this will make your breadcrumbs both human and search engine friendly.
- Include the full navigational path from the homepage to last level of current page. Not displaying certain levels will confuse users.
- Never replace primary navigation. They have been devised as a secondary navigation aid and should always be used as such.
Example:
