1. Decide according to the visitor’s task
In our fictional catalogue, a course page links to a partner organisation’s programme. Record why visitors need to follow it and what they should return to afterwards. Changing domains alone does not justify a new window. Choose an explicit rule for this link rather than automatically opening every partner elsewhere.
W3C advises limiting unnecessary new tabs and gives help during form completion as a possible context-preserving exception. This is an advisory technique, not a universal requirement. For our programme, the team chooses the same tab; it makes a separate decision about form help.
Source : W3C — G200: Opening new windows and tabs only when necessary
2. Describe the destination before the click
Prepare “Read the programme on the partner organisation’s website” instead of repeating “Learn more” everywhere. W3C requires a link’s purpose to be understandable from its text or associated context. A long address alone rarely tells readers what they will find.
Record the text, full address and destination language in the editorial worksheet. If the partner page is available only in English, explain this alongside the link. Check the real content before approval: a general home page does not necessarily replace the specific programme promised.
3. Announce a new tab imposed by the website
If another window or tab is chosen, warn before activation, for example “Read the help (new tab)”. W3C technique G201 proposes a warning that assistive technology users can also perceive. It excludes tabs visitors choose themselves through their browser and does not independently certify accessibility.
Review the visible label and accessible announcement together. A small unexplained arrow can remain ambiguous. In our example, the help message announces the opening; the partner programme stays an ordinary link. Keep the same decision in French, English and Arabic, using natural wording.
4. Separate the navigation decision from technical protections
Ask the team to check the protection appropriate to the chosen openings. In HTML, noopener prevents the new page from having an opener reference to the original page. noreferrer also removes transmitted referrer information and implies noopener. These effects are not two names for the same editorial decision.
Do not add a privacy rule at random just to obtain another tab. Confirm the technical intention and expected behaviour in the preview environment. These protections verify neither the partner’s identity nor the safety of its content: checking the address and destination remains necessary.
5. Repeat departure and return on mobile and by keyboard
In the preview, start from the course page, read the announcement and activate the link normally. Record the number of tabs and destination. For the same tab, try the browser’s Back button. If another window opens, find the original tab and check that continuing remains understandable. A screenshot of the destination alone does not prove this return journey.
Repeat by keyboard and on a phone, then reload the starting page. Use only fictional values when checking help during data entry, without submitting the form. Distinguish this test from deliberately opening a tab through the browser menu. In Arabic, read the announcement and foreign names in their right-to-left context too.
6. Keep a testable decision and handle differences
For each link, keep the starting address, label, destination, language, chosen behaviour and its reason. Add the device, browser, tested version and observed steps. If two comparable links behave differently without a known reason, have their consistency decided before accepting delivery.
Record a removed destination, unexpected language change or unannounced opening, then repeat the check after correction. Do not accept a link just because it responds. This check covers selected link journeys; it demonstrates neither full compliance nor improved conversions or search rankings.
Link decision and acceptance worksheet
| Check | Expected decision | Evidence to keep |
|---|---|---|
| Link purpose | Useful destination for the task | Approved text and address |
| Chosen tab | Justified behaviour | Reason and observed opening |
| Warning | Announcement before imposed opening | Label and accessible reading |
| Language | Change explained where needed | Starting and destination language |
| Return | Understandable continuation | Outward and return steps |
| Correction | Same case checked again | Version and result |
Frequently asked questions
Should every external link open elsewhere?
No. Decide according to the task and the need to preserve context. An automatic rule based only on the domain does not replace that decision.
Does a new window prevent lost input?
It can help retain context, but it does not guarantee that data is kept. Check the real journey using fictional values in the preview, without submission.
Is an icon enough to warn readers?
Check its visual meaning and what assistive technologies announce. Clear text associated with the link provides wording that is easier to review and translate.
Prepare your next acceptance check
Choose a partner link and a help link in your preview. Approve the destination, tab decision and wording, then record departure and return in each published language.
Sources and scope
Primary W3C and WHATWG sources consulted on November 6, 2026. The catalogue and wording are fictional editorial examples. The proposed steps claim neither checks performed on your website nor a new Dev Ring feature.
