It is often the small things that are the most contentious in a community. As a vigorous debate on the LinkedIn ‘Intranet Professionals’ group showed, “should links open in a new window?” is one such topic.

While these discussions echo the policies established for public-facing websites, intranets may require very different approaches.

Even on public sites, browsing the web shows that practices have changed greatly over the last few years. Previously, any link to an ‘external’ site (managed by another organisation) would open in a new window (or a new tab, in modern browsers). On government sites, there would even be an intermediate page, warning that ‘you are leaving this site and we are not responsible for the content that you may read’.

On recent websites, links opening in new windows have become much rarer, suggesting that both practices and user expectations are changing. So what should be done on intranets?

Many possibilities

There are a wide range of policies that could be put in place:

all links open in the same window (no new windows)

links to public (external) sites open in new windows (or new tabs)

links to systems or applications open in new windows

links to documents or other non-web content open in new windows

any link that takes the user away from the current task open in new windows

links to other internal ‘intranet sites’ open in new windows

Depending on the policy chosen, and the nature of content and tools on the intranet, these approaches could generate just a few links that open in a new window, or many.

Benefits of a new window

Opening in a new window or tab can help to differentiate between ‘internal’ (intranet) and ‘external’ (web or system) content.

They can also help when there is a link to a document such as a Word or Excel file, where the browser is set to display the file within the window rather than opening up a full copy of the relevant application.

Usability challenges

There are some significant usability issues with opening links in a new window. The most used option in a browser is the ‘back button’, and this is broken when a new window is opened.

Users may also miss that a new window is opened, particularly in more recent browsers that follow a tab metaphor. This can generate further confusion.

It can also generate a lot of windows during a single intranet session, arguably making the intranet harder to use.

A longer term view

So what is the correct answer? Our recommendation would be to avoid opening links in new windows (or tabs) entirely.

If the strategic goal is to provide staff with a seamless environment for all the tools and information they need to do their job (and it should be), intranets must increasingly blur the line between technology solutions.

In this world view, why should staff have to know they are going to an ‘external system’ to apply for leave, or to lodge an expense form? Instead, we should be making the transition invisible wherever possible.

This would eliminate all new windows, as well as bring together content and systems.

Establishing a practical policy

There are a range of practical policies that can be put in place, drawing on the earlier list, or creating a different combination of rules.

Any decision that is made must work well for staff and match their usage practices. It must also be practical to implement (and enforce?) in a decentralised authoring model, with the chosen technology.

If in doubt, keep it simple, and err on the side of fewer new windows and tabs rather than more.

Comments

We had this debate for our own intranet. It’s Sharepoint so here’s what I set: – links to Office/PDF docs open in new window Why? Many people clicked on the office doc link but when they were finished closed the browser by mistake so had to enter the intranet again. Resaearch showed us that this was a problem.

– links to other applications/external web sites open in new window Why? Security mostly. Our intranet is password controlled and so are other applications on different platforms. Different passwords on different systems sometimes caused an issue.

And because we have intranet passwords we want people to keep the intranet open for them to use so that’s why we have new windows opening.

Also, links that are inside a workflow or application, for example to read reference policies.

It would be good if we could depend on the back button getting you to your form in the exact state that you left it, but this is often not the case. There’s nothing worse that half filling in a form – then nipping out to another page to check some detail and then nipping back to find you’ve just lost your work.

Of course, for this reason its usually a bad idea to have links at all in the middle of a form and some in context help is better, but depending on the information this may not be possible. If you must put in a link state clearly it opens a new window. Oh and never ever break a users ability to right/middle click that link.

The importance of getting this new window issue right was brought home to me when I visited the Shaw Trust, a UK-based charity, who employ people with a range of disabilities to complete accessibility tests on intranets.

A blind tester clicked on a link that opened a new window. Using screen reader software they could understand the content of the page but, importantly, when they used the voice command ‘back’, there was no back available given it was a new window. This was tremendously disorientating and confusing for several minutes until the tester figured it out.

The solution proposed was that if you must open a new window (for an application maybe, or for other aesthetic and usability reasons), you must label the link correctly.

ie. Expenses System becomes Expenses System (Opens new window)

In itself, that’s clumsy which is why I always choose to avoid the new window issue by keeping as much content as I can in the same window instance.

@Jonathan, the accessibility argument is a powerful one for not using new windows! Unfortunately, many organisations pay little attention to their accessibility obligations regarding their intranet (and not much more for their public facing websites)…

I disagree that all external links should open in the same browser window. My work involves maintaining an organisation’s intranet. Our policy states to open external websites in a new browser window and I support this 100 per cent. On the other hand, I also support links to documents, such as, Word and Excel that open in the same browser window.

The usability challenge is when the external website does not open in a new window. In this case, you, delve deeply into an external website, immersing yourself in information, only to lose your original starting point. This is extremely annoying when having to find your way back. The quickest and easiest way back is to close the browser window, that is, if the link to the external website did open in a new browser window.

In my work environment, the external website is just for additional information. Considering we are not at the start of the intranet/internet age, I would like to think that our users are web savvy and can close a browser window after they have found the information needed.

@Ann, I agree there is no one right answer on this. In terms of staff getting lost however – the most used button is always the back button. Whether this is good or bad philosophically, it does mean that people can “find their way back”. There’s no evidence that staff build up a mental map, so “lost” may be less of a consideration.

I too have seen the frustrations of the “Open in New Window” situation. Not just opening links to other webpages, but also in opening documents through other applications that leave rogue windows behind (depending on browser and version).

Before the average user knows what’s happening they can have two or three intranet windows open and can start completing multiple tasks in different windows. It’s an easy way to lose information when you attempt to close one window, but accidentally close and lose everything.

Having also worked closely with a number of UK Public Sector organisations, the single window method is also imperative in following the DDA (Disability Discrimination Act) standards they are required to adhere to.

My advice would be to ensure internal links always remain in the same window, while external links open in a new window (clearly illustrated to the user)

There are strong arguments here for both approaches, but essentially all boil down to the user’s understanding of what is happening.

Good usability requires the following: 1. Anticipate the user’s expectations This is best achieved through research into the target user and the usage context. 2. Manage the user’s expectations This is achieved through careful interface design and behaviours that both explain and afford the activities occuring 3. Mitigate against of expecation/goal This includes error messaging, good navigation that enables users to understand where they are and how to move about etc.

In this scenario, the expectations of users are largely unpredictable across the general public, but within an organisation that we can assume has a legacy system, the way things are already don (if it is consistent) will be a strong influence on expecations. So if the current intranet practice is to open apps, docs or external sites in a new window, then most people will expect that to happen when they go to work tomorrow too.

However you choose to resolve this issue, ensuring the users understand what’s occuring is critical. Does the link state that the destination is an external page, a document or an application? Does the design of the page coherently express the relationship between the source and destination?

There is much at stake when you open in the same window and deny the users the escape route of using the ‘back’ button to return. Mitigating against unmet expectations needs to be supported. Think of an online banking system: before moving to a new area, users are prompted to confirm they want to leave the system. Pop-up messages are annoying, but can be preferable to sending users down blind alleys.

Essentially, bringing all the content within the intranet is ideal – I’ve seen too much critical content housed in word documents, excel spreadsheets and vanity sub-sites that could be better placed in HTML format on an intranet where it could be effectively managed, discovered (through search indexes and navigation) and accessed by alternative technologies.