I'm creating a navigation list which links to various different articles. In the past I've defined navigation lists as
<li role=link href=#foo>
An interactive reference to an internal or external resource that, when activated, causes the user agent to navigate to that resource.
If this is a native link in the host language (such as an HTML anchor with an href value), activating the link causes the user agent to navigate to that resource. If this is a simulated link, the web application author is responsible for managing navigation.
No, the WAI-ARIA
link role is merely descriptive and intended to help devices like screen readers. It will not introduce any functionality. It is especially helpful when the link in question is not an
That being said, some browsers will let you manipulate this by either changing settings in the browser or installing add-ons. This has no real practical purpose as the majority of users will not experience the changes, but it seems to be the only way. I found the most documentation for Firefox with the window.status page. You can set
window.status = 'www.fakeurl.com', however you need to set the
dom.disable_window_status_change preference to
about:config before that would work.
If displaying text in the status bar is absolutely necessary the only way you will accomplish that is with an
a element. As a rule of thumb, if your app allows you to use an
a element for navigation, then you should always use an
a element for navigation. And with CSS3 it's hard to imagine too many scenarios where you wouldn't be able to do so, as you could style that anchor tag to look like just about anything you wanted.