We're currently updating our site for ADA compliance and want to implement a skip navigation menu on the main landing pages. The menu will offer skip nav links to "Login," "Main Content," and "Footer." The business offers three principle services, each of which has it's own landing page. The question I'm wrestling with is, is it useful or appropriate to offer two additional links in the skip navigation menu that redirect users to the two other business service landing pages?
This would absolutely be an inappropriate use of skip links.
"Skip links are internal page links which aid navigation around the current page, rather than to completely new pages. They are mainly used by screen reader users for bypassing or 'skipping' over repetitive web page content."
https://www.nomensa.com/blog/2004/what-are-skip-links
The whole purpose of skip links is to help bypass navigation structures so that visitors don't have to listen to repetitive links on every page.
Is it useful or appropriate to offer two additional links in the skip navigation menu that redirect users to the two other business service landing pages?
Although it's not forbidden by any WCAG rule, mixing anchor links and internal links can be confusing for user experience. It would be quite hard to find a correct alternative name for the navigation menu.
Related
I read through all the other questions/answers I could find. Most solutions were quite old already and given that most websites nowadays are single page sites I am hoping there's an easier solution today?
I have a single page website i.e. home, banner, services, team, contact all on the same page with links at the top to scroll using href # to the section on the page.
Since all content is on one page, Google Analytcs only tracks the page as a whole. Is there an easy way to track whether a visitor has scrolled down to a specific section (website is a simple Bootstrap site) and/or clicked on a menu item to scroll down?
You can set a Virtual Pageview based on visibility element. Each section has a div, by assigning an ID to each section you can send a pageview as soon as the ID appears in the screen.
Depend on how your SPA works youca use History change trigger: https://support.google.com/tagmanager/answer/7679322?hl=en&dark=0
I am developing application for shopify, which replace login and register links to another links, creating a custom pages. For example when user click to login link? it is not redirect to login page, it is open a popap with login form. Also my app create custom pages. For example people page, where shows list of customers. And also a want to customize product page by adding a new fave button. In people page for each people shows count faves and last three faves product with images.
So my problems is theme layouts. Because each theme have self layout and css. I want to my app support all themes. How can i do it?
Sorry for my bad english. I just learning... ))
You have two options here, http://docs.shopify.com/api/tutorials/application-proxies and http://docs.shopify.com/api/scripttag.
App proxy sounds like the solution for your separate 'peoples' page.
If you want to assume that all themes have a log in link (which they all should but it's completely customizable so it's possible some don't), then you could always do something like this
$("a[href='/account/login']").click(funciont() {// show modal}); This isn't guaranteed to work in all themes but it probably will in most.
I've got a wordpress website with a drop down menu in the main navigation. The menu items does not link to anywhere, but rather on hover, the drop down menu displays. This is a pure CSS drop down menu.
Using the wordpress menu editor, I've assigned the URL as #, so in other words the html will be:
Link
If the user clicks this link, the URL will change to the current page's URL with a # added at the end. But the page does not refresh or reload in anyway.
The other option is to leave the URL blank in the wordpress menu system, meaning the html will be:
<a>Link</a>
This does not allow you to click the link and doesn't even change the pointer cursor to the hand as you'd expect on links.
Now, seeing as neither of these actually link anywhere, which would be best from a SEO angle?
Will google try to index all of my pages twice with the /# added at the end and causing duplicate content issues?
Thanks in advance.
Kind Regards
Willem
Willem,
Yes. According to Google www.example.com and www.example.com/# are different pages. This can lead to duplicate content penalties and can cause your links to be divided between pages as users link to both. I would recommend a different setup 301 redirect to the page without the #. There are some simple WP plugins that allow redirects to be setup in minutes without requiring use of the htaccess. Personally, I use the plugin called SEO Redirect 301s.
Hope that helps!
This is a common issue.
Both variants ( <a href="#"> and <a> ) do the same to your SEO: They are ugly from a Webdevelopers perspective, but they don't actually hurt your site or rankings. Google won't even crawl the URL '/#'. The only negative aspect is that you have more (worthless) links per URL and therefore less power to spend for the important URLs.
My personal view
Example 1:
Imagine your Homepage has a "Linkpower" value of 100. (Yes, thats a term without meaning.)
You have 2 links on your Homepage.
So every link passes a Linkpower of 50.
(Of course that's wrong, but is just to illustrate the problem.)
Example 2:
Imagine your Homepage has a "Linkpower" value of 100.
You have 3 links on your Homepage. (Including 1 worthless link for the Dropdown-Menu.)
So every link passes a Linkpower of 33.
So, remove the odd links if you want to build the perfect website, or keep them if you have something better to do respectively if you want your menu to work in outdated browsers.
I have many content pages. In master page I have added the tab About us, support, contact us. Which will come in all pages. But some pages will have different tabs from other pages. EX: group page will have users and message tab, users page will have groups tab and message tab. I can design this in master page as it varies from page to page. The tabs depends on the user permission, for each user it is going to change. What is the best way of doing this.
As a general concept, I would develop the tabs as a user control or server control. The control should render its tabs based on the current user and the current page. If that's enough to get you started, great. If not, post a comment and I'll see if I can put together a sample for you.
I do most if not all my sites to have the page title block (generally a styled h1 on my pages) to link back to the home page.
Should this be linked on the first page, i.e. the home page? I read that this shouldn't be linked, but one thing I do when I go to a page for the first time is mouseover the title to check the status bar to see if it will send me home.
What I'm asking is best practises for this... should the home page's title link back to itself for future reference for the user?
While I understand the logic behind a page not linking to itself, I personally think the title block is a defensible exception. So I think you should link it to the home page, even on the home page.
See sites such as facebook - the facebook logo always links to the homepage.
It's a strong convention, and I try to utilize it where ever practicable.
There should never be links on the page that link to itself. According to research by Jakob Nielsen, this is a bad idea. Further reading here (#10) and here (also #10 in that list).