Links that open in a new tab or window

Opening links in a new tab is a habit on many shops: payment provider pages, size guides, social media links, sometimes every external link. WCAG does not forbid it, but an unexpected new tab is a real barrier for some people. This page explains what WCAG says, when a new tab is reasonable and how to warn users correctly. It is part of the accessible UI patterns series.

What WCAG says

There is no level A or AA success criterion that forbids target="_blank". The relevant W3C material is:

• Technique G201, "Giving users advanced warning when opening a new window". W3C lists it as an advisory technique for 2.4.4 Link Purpose (In Context), 2.4.6 Headings and Labels, 2.4.9 Link Purpose (Link Only) and 3.2.5 Change on Request. It "is not required" to meet those criteria — it is good practice.
• 3.2.5 Change on Request (level AAA) is the criterion that covers opening new windows only when the user asks for it.
• 3.2.2 On Input (level A) is relevant when a new window opens not from a link but when someone changes a radio button, checkbox or select. W3C failure F37 is "launching a new window without prior warning when the selection of a radio button, check box or select list is changed".

G201 explains the reason: unexpected new windows can disorient people who have trouble perceiving visual content and some people with cognitive disabilities, and the Back button will not return them to the previous page.

When a new tab is reasonable

• The user is in the middle of a task and the link opens help they need alongside it: a size guide or terms during checkout, where leaving would lose entered data.
• A third-party page the user will come back from, such as a parcel tracking page, if the user is warned.

When it is usually not helpful: ordinary navigation inside your shop, social media icons in the footer, blog articles, every external link "so users do not leave". Users who want a new tab can open one themselves; the reverse is not possible.

Code example

<!-- Warning in the visible link text: works for everyone -->
<a href="/en/size-guide" target="_blank">Size guide (opens in a new tab)</a>

<!-- Icon with a text alternative referenced by aria-describedby -->
<a href="https://tracking.example.com/123" target="_blank" aria-describedby="new-tab-note">
  Track your parcel
  <svg aria-hidden="true" focusable="false" class="icon"><use href="#icon-external"></use></svg>
</a>
<span id="new-tab-note" class="visually-hidden">Opens in a new tab</span>

<!-- A file: say what it is instead of forcing a new tab -->
<a href="/files/returns-form.pdf">Returns form (PDF, 120 KB)</a>

Notes:

• G201 shows both approaches: the warning in the link text, or an icon hidden with aria-hidden plus a text description connected with aria-describedby so that screen reader users hear it too.
• An icon with no text alternative helps only sighted users who know the icon. A text alternative alone helps only screen reader users. G201 tests both: assistive technology announces the new window, and there is a visual indicator.
• The warning becomes part of the link purpose, so keep it short and consistent across the site.

Keyboard and interaction

G201 applies to regular activation (click, Enter). Opening a link in a new tab through the context menu or a middle-click is the user's own choice and needs no warning.

Common mistakes on online shops

• All footer and social links open new tabs without any indication.
• An external-link icon without a text alternative, or a decorative icon with an alt that says "icon".
• Warning only in the title attribute. Browsers show it on mouse hover, so keyboard and touch users do not see it.
• Payment or 3-D Secure steps opening in a new window that screen reader users do not notice, so they think the checkout froze.
• Language or country switchers built as a select that opens a new window on change — that is the F37 failure for 3.2.2.
• Product links in reviews or blog posts with target="_blank" that break the Back button on mobile.

What automated checks catch vs manual testing

Our automated checks do not flag target="_blank", because there is no level A or AA requirement and a warning can be written in many ways. Related cards in the rule library:

Manual testing: list all links with target="_blank" (the browser developer tools can search for it), decide which really need a new tab, and check with a screen reader that the warning is announced and visible. The browser extension and the steps in how to test WCAG help with the manual part.

Start with the free one-page check. It is an automated check, not a full audit.

Frequently asked questions

Does WCAG forbid links that open in a new tab?

No. No level A or AA success criterion forbids target="_blank". WCAG lists warning users before a new window opens as an advisory technique (G201), and the AAA criterion 3.2.5 Change on Request deals with opening new windows.

Why can a new tab be a problem?

According to the W3C technique G201, an unexpected new window can disorient people who cannot see that it opened and some people with cognitive disabilities. The Back button no longer takes them to the page they came from.

How do I warn that a link opens in a new tab?

Add the warning to the link text, for example "Size guide (opens in a new tab)", or show an icon and give it a text alternative that assistive technology announces. Both sighted and screen reader users need the warning.

Should links to PDFs open in a new tab?

Not necessarily. It is usually better to say in the link text that it is a PDF and how large it is, and to let the user decide how to open it.

Can an automated check find links that open in a new tab without a warning?

Our automated checks do not flag target="_blank". Whether a warning exists and is announced has to be checked by a person.

Sources

• W3C, Technique G201 Giving users advanced warning when opening a new window: https://www.w3.org/WAI/WCAG22/Techniques/general/G201
• W3C, Understanding 3.2.2 On Input: https://www.w3.org/WAI/WCAG22/Understanding/on-input.html
• W3C WAI, APG Link pattern: https://www.w3.org/WAI/ARIA/apg/patterns/link/