chore(documentation): removed obsolete target=blank occurences from the DS documentation

[myrta2302]

Removed obsolete target="blank" occurences across the DS documentation.

🔮 Design review

• Design review done
• No design review needed

🧪 Visual regression tests

• Visual changes detected and approved (Check this box if VRT fails and changes are intentional)

📝 Checklist

• ✅ My code follows the style guidelines of this project
• 🛠️ I have performed a self-review of my own code
• 📄 I have made corresponding changes to the documentation
• ⚠️ My changes generate no new warnings or errors
• 🧪 I have added tests that prove my fix is effective or that my feature works
• ✔️ New and existing unit tests pass locally with my changes

[changeset-bot]

🦋 Changeset detected

Latest commit: 5fc8f1d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@swisspost/design-system-documentation	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[swisspost-bot]

Related Previews

• https://preview-8220--swisspost-design-system.netlify.app?devModeEnabled=true

[oliverschuerch]

Is there a ticket for that?
And should we create a changeset, since our users are directly affected by this change?

[myrta2302]

Is there a ticket for that? And should we create a changeset, since our users are directly affected by this change?

Sorry for not including this from the start in the PR description. This was actually a review comment i got on the Blueprint update. I did not create a ticket, because of the small size of the task.

Changeset added.

[oliverschuerch]

As a general statement about target="_blank":

AI Generated Flags content which is completely or mostly generated by AI.

The a11y position on target="_blank"

There's no WCAG rule that forbids it outright. The relevant guidance:

• WCAG 3.2.5 Change on Request (AAA): opening a new window without warning is a failure at the AAA level. It's not a failure at AA — but it's listed as a technique to avoid.
• G200 (Opening new windows on user request): the accepted practice is to only open new tabs/windows when there's a genuine reason, and to warn the user when you do.
  So the recommendation is: don't reach for target="_blank" by default. Use it deliberately, and when you do, make it perceivable.

If you do use it

Two things are needed:

Security: pair it with rel="noopener noreferrer" (modern browsers imply noopener, but be explicit).
Warn the user: expose "(opens in new tab)" — ideally visible text, or at minimum for AT, e.g. a visually-hidden span:

<a href={this.url} target="_blank" rel="noopener noreferrer">
  <slot />
  <span class="visually-hidden">(opens in new tab)</span>
</a>

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud