Why This Accessibility Failure Happens In Multisite
Linked image describing appearance instead of destination is a common alt text mistake in a WordPress multisite shared media library. It happens when the image is also a link, but the accessible text describes what the image looks like instead of where the link goes or what action it performs.
For example, alt text like "blue banner with smiling team" may be acceptable for a purely informative image, but it becomes misleading when that same image links to a pricing page, a contact form, or a downloadable guide. In that case, screen reader users hear a description of appearance rather than the destination or purpose of the link.
This issue becomes harder to control in multisite because a shared asset may be inserted across many subsites by different editors, each using the same media item in different contexts. A single image can serve as a homepage hero on one site, a call-to-action on another, and a navigation shortcut somewhere else. That reuse breaks the assumption that one media-library alt value always fits every placement.
What WCAG Expects For Linked Images
When an image is the only content inside a link, the accessible name of that link should communicate the link destination or function. WCAG guidance on text alternatives and link purpose supports this principle. The user should understand what will happen after activating the link, not just what the image looks like.
Useful references include:
A linked logo that goes to the homepage might appropriately use alt text like "Home" or the organization name if that clearly functions as the home link. A linked promotional graphic pointing to a webinar registration page should expose something closer to "Register for the June webinar" than "orange illustration with laptop."
Why Shared Media Libraries Create Extra Risk
A multisite shared media library centralizes assets, which is efficient for governance and storage, but it also introduces context drift. The same attachment metadata may be pulled into multiple sites with different goals.
The Core Limitation
Attachment-level alt text is usually stored once, while link purpose is contextual.
That mismatch is the root of the problem. Editors may update alt text to suit one use case and accidentally make the image worse everywhere else.
Common Scenarios
- A shared campaign banner is linked to different landing pages on different subsites.
- A product image links to a detail page on one site and to a category archive on another.
- A decorative-looking tile becomes a functional navigation card in a local department site.
- A centrally managed logo links to different regional homepages.
How To Diagnose The Real Failure
Before changing anything, confirm whether the image itself needs descriptive alt text or whether the link needs a clearer accessible name.
Use this quick decision process:
- Check whether the image is inside a link.
- Check whether the link contains any visible text besides the image.
- Ask what a screen reader user would hear as the link name.
- Compare that name to the actual destination or action.
If the linked element contains both an image and meaningful adjacent text, the image may need empty alt text so the visible link text becomes the accessible name. If the image alone is the clickable content, the alternative text usually needs to communicate destination or function.
Comparison Of Fix Approaches In Multisite
Not every fix belongs at the media-library level. In a shared-media environment, the best solution depends on how broadly the asset is reused.
| Approach | Best For | Main Benefit | Main Limitation |
|---|---|---|---|
| Edit attachment alt text globally | Single-purpose shared assets | Fast and centralized | Can break other contexts |
| Override alt text per placement | Reused assets with different link targets | Preserves context | Requires theme or block workflow support |
| Add visible link text next to image | Cards, promos, CTA blocks | Strongest clarity | May change design |
| Use empty alt when text link already exists | Image plus descriptive text in same link | Prevents redundancy | Only works when text is truly descriptive |
| Replace image-only links with text-based components | Critical navigation and CTAs | Most robust accessibility | More design and template work |
Option 1: Fix The Shared Attachment Alt Text
This is the simplest fix, but only when the image has one stable purpose across the network.
Use it when:
- The shared image always links to the same destination.
- The asset is branded or functional in a consistent way.
- Network governance allows a single source of truth.
Avoid it when:
- Different sites point the same image to different URLs.
- The image is reused in both linked and non-linked contexts.
- Editors cannot easily audit downstream impact.
Option 2: Override Alt Text At The Point Of Use
This is often the best fix for a multisite shared media library because it respects local context.
Instead of assuming the attachment alt text should do all the work, allow the editor or template to set context-specific accessible text where the image is embedded. That could happen in a custom block, card component, template partial, or field-driven module.
This approach fits scenarios where:
- Shared assets are reused in many subsites.
- Link destinations vary by page or campaign.
- Central media governance exists, but local editorial teams control page intent.
The tradeoff is implementation complexity. WordPress does not always make per-instance overrides obvious in every editing flow, especially when custom blocks or synchronized patterns are involved.
Option 3: Use Visible Link Text And Make The Image Secondary
If the linked image is part of a promo card or callout, adding clear visible text is usually a stronger solution than trying to make the image carry all meaning.
A card with a heading like "Download The Annual Report" gives all users a clearer signal. In that setup, the image can often use empty alt text if the text in the same link already expresses the purpose.
This is especially useful for:
- Marketing panels
n- Resource cards
- News promos
- Department landing pages
It also scales better across multisite because the same image can be reused while each site controls its own linked text.
Option 4: Rebuild Problematic Image-Only Links
Some image-only links should not stay image-only.
If the link is important navigation, donation flow, application entry point, or high-value conversion action, rebuild the component so the accessible name is explicit by design. That may mean using a button-style link, a card with a heading, or a text-first block pattern.
This is the best long-term choice when:
- The asset is mission-critical.
- The image is visually attractive but semantically weak.
- Editors repeatedly misuse the same component.
Recommended Fix By Use Case
For Central Platform Teams
Prefer per-placement overrides or text-first components. Global attachment edits are risky in a multisite shared media library unless the destination is identical everywhere.
For Content Editors
If the image is the only linked content, write alt text for the destination or action, not the appearance. If there is already clear linked text, use empty alt text for the image when appropriate.
For Theme And Block Developers
Build components that separate image description from link naming. Expose a dedicated field for link label or accessible name when an image acts as a CTA.
Practical Editorial Examples
| Weak Accessible Text | Better Accessible Text | Why It Works |
|---|---|---|
| "woman using tablet" | "View Customer Success Stories" | Names the destination |
| "green download icon" | "Download The Setup Guide" | Names the action |
| "team photo" | "Meet Our Leadership Team" | Matches user intent |
| "red sale banner" | "Shop Summer Sale" | Communicates purpose |
Final Decision
For most teams using a WordPress multisite shared media library, the safest fix for linked image describing appearance instead of destination is not a blanket media-library edit. It is a context-aware approach: override the accessible text where the image is used, or pair the image with visible link text so the destination is unmistakable.
If the asset has only one destination everywhere, a shared media update may be enough. But if the same image travels across subsites and campaigns, treat link purpose as local context rather than global metadata. That is the cleanest way to improve accessibility without creating new failures elsewhere.