Screen Readers Don't Care About Your Vanity Slug
Photo: InclusiveGameLab, CC BY-SA 4.0, via Wikimedia Commons
Open a screen reader, load a page dense with links, and pull up the links list. This is a routine navigation move for blind and low-vision users: a flat, alphabetical-ish roster of every link on the page, stripped of the paragraphs around it.
Now imagine what that roster looks like when half the entries read as gowww.link/8f3k2, three of them say click here, and two more are identical because the same destination got linked twice under the same label. That is the experience of a huge number of marketing emails, help center articles, newsletters, and government notices in 2026.
This is not an exotic edge case. It is the default output of the link-shortening workflow, and it is fixable without giving up a single byte of tracking.
What assistive technology actually announces
Screen readers do not read the URL bar and they do not read your redirect headers. They read the document object model — specifically, the accessible name of each link, computed from its visible text, its image alt text, or an ARIA attribute when one is present.
That means three things happen constantly with shortened links:
The slug becomes the name. When the anchor text is the short URL itself, a user hears it character by character. g-o-w-w-w dot l-i-n-k slash 8-f-3-k-2. Long slugs are worse. Hashes are the worst.
Context is annihilated. Screen reader users jump between links without hearing the surrounding sentence, so "read the full report" has to survive on its own. If you wrote "the report is available here, and the appendix is here too," both links announce as here and the user has a coin flip.
Duplicates compound. Link lists surface duplicates flatly. If your email template wraps a hero image and a button in the same destination with the same label, you have created two identical entries and no way to tell which is which.
What the standard actually requires
WCAG 2.2 has a level A criterion aimed squarely at this. 2.4.4, Link Purpose (In Context), requires that the purpose of each link be determinable from the link text, or from the link text together with its programmatically determined context. "Here" and "read more" and bare short URLs fail it. "Download the 2026 shareholder letter" passes cleanly.
There is a stricter version, 2.4.9, Link Purpose (Link Only), at level AAA, which drops the escape hatch of surrounding context — the link text has to stand alone. Worth aiming for even if you are only obligated to hit AA, because link lists and search results are precisely the contexts where surrounding text does not travel with the link.
And yes, this applies to shortened links. A short URL is not exempt because it is short. The criterion governs the accessible name, not the length of the string.
Why 2026 raises the stakes
The Department of Justice's web accessibility rule for state and local governments, finalized in 2024, put WCAG 2.1 AA on a compliance clock: April 2026 for larger public entities, April 2027 for smaller ones and certain special districts. If you work for a school district, a transit authority, or a county agency, and your emails and notices route through a shortener, the accessible names on those links are now part of an obligation with a date attached, not a nice-to-have.
Private organizations face the same practical exposure through ADA litigation and procurement questionnaires. Shorteners have become infrastructure. Accessibility review has started asking about infrastructure.
Patterns that work
1. Descriptive anchor text, always
The single highest-value change: never use the short URL as the anchor text. Use a short, meaningful phrase that survives being read out of context.
Bad: Read the filing here: gowww.link/8f3k2
Good: Read the 2026 rate filing (PDF, 2.1 MB)
The short URL still exists. It is in the href. Nobody sees it, and nothing about tracking changes.
2. Append, do not replace
If you want to add clarity for screen readers, add to the visible text rather than overriding the accessible name with aria-label. WCAG's 2.5.3, Label in Name, requires that the accessible name contain the visible label, because voice control users say the text they see out loud. Replacing "Read the filing" with "Read the 2026 rate filing PDF" in an ARIA attribute breaks the person saying "click Read the filing."
A visually hidden suffix inside the same anchor preserves both:
<a href="https://gowww.link/8f3k2">
Read the filing
<span class="sr-only">(PDF, 2.1 MB, opens in a new tab)</span>
</a>
Visible label intact. Extra detail available. Voice control still works.
3. One link, one name
If two links go to the same place, give them distinct labels or merge them into one link. A hero image and a button pointing at the same filing should not both announce as identical buttons in a link list. Name the image link something different — or drop the duplicate link entirely and keep the image link inside the text link.
4. Keep the redirect boring
If any part of your flow involves an interstitial — a countdown, a "you are now leaving" splash, an app-install prompt — that page needs a real heading, the destination announced in text, and a way to continue without waiting. Auto-forwarding that fires without warning yanks a screen reader user into an unannounced page load, and focus can end up back at the top of the document or nowhere at all.
A clean 302 straight to the destination is more accessible than a clever interstitial. It always was.
5. Test with the tools people actually use
Open your page in NVDA on Windows or VoiceOver on macOS and iOS and hit the links list. Not a developer audit panel. The actual rotor and the actual list. If the entries read like a sequence of unrelated hash strings, you have your bug report and you do not need anyone else to write it for you.
Branding survives this
Every objection to this list tends to land in the same place: we need the short domain, we need to measure clicks, we need brand consistency. None of that conflicts with accessible link text. Your branded short domain lives in the href where it belongs. Your click tracking lives in the path or the query string or the redirect log. The anchor text is the one place you get to spend for free on clarity.
Shorten the URL. Do not shorten the meaning. Someone is going to read that link list, and it will be the only thing they hear.