<a> stands for anchor
If you include the [href] attribute on an <a> element, it is an anchor that points to a location, which means that you could go to a new page, a particular fragment of the current page (hence the # being called the fragment identifier), or a particular fragment of a new page.
<a> elements without an [href] attribute were historically assigned a [name] attribute, which could be used as the destination of the fragment identifier. Browsers later added support for linking to any item’s [id] attribute, and this is now the preferred method for linking to a document fragment.
What does this mean for standalone <a> elements?
An a[href] element is a link (which is why they are matched with :link in css). links are clickable. An a element without the [href] attribute is otherwise just a placeholder for where a link might otherwise have been placed, and not clickable, nor are they in the tabbing order of the page.
If you want your links to be keyboard navigable which is important for accessibility (WAI-ARIA), you’ll need to do one of the following:
- change the element to
<button type="button"> - keep the
[href]attribute - add
[tabindex="0"]and one of[role="button"]or[role="link"](and possibly some styling)
More information about the [role] attribute can be found in the Roles Model section of the WAI-ARIA docs.
Changing the markup
If you don’t have a reason to keep the [href] attribute, you might as well be using a <button> element:
<button type="button">
^^^^^^^^^^^^^
The [type] attribute is used to make the element a generic button, otherwise <button> will default to [type="submit"], which may not be desirable as it could trigger form submission.
If you can’t use a <button> (usually occurs when the inner markup must contain a <div>) you can fake a <button> using:
<div role="button" tabindex="0">Some clickable text</div>
You’ll need to listen for keypress events and trigger click events for Enter and Space.
Keeping the markup
If you’re keeping the <a> element and its [href] attribute, there are a number of options for its value.
A real link
E.x.
<a href="https://stackoverflow.com/some/location/for/users/without/js"><a href="#document-fragment">
If you need to provide support for users with JS disabled, you might as well direct them to a page that performs equivalent functionality without JS.
By extension, this also includes providing document fragment links to link to the content within the same document. For example, a toggleable region may be marked up as:
<a href="#more" class="toggleable">Read More</a>
<div id="more">Lorem ipsum dolor sit amet</div>
So that with JS the region can be collapsed and expanded, and without JS the link will take the user to the appropriate content on the page.
A dud href
E.x.
<a href="#"><a href="https://stackoverflow.com/questions/11144653/javascript:void(0)"><a href="https://stackoverflow.com/questions/11144653/about:blank">
If you’re preventing the default behavior behind-the-scenes in JavaScript, and you’re not supporting users with JS disabled, you can use a “dud” href value to keep the link in the tabbing order and automatically enable Enter to trigger the click event. You should add [role="button"] as semantically the <a> tag is no longer being used as a link, but as a button.
<a href="#" role="button">Some clickable text</a>