A hyperlink should be quick to understand: hear its descriptive text, decide whether it is relevant, and move on. In Microsoft Teams workflow on Windows with JAWS, links inside Loop components do the opposite. JAWS reads a long Microsoft redirect URL before it reaches the useful hyperlink text.

The URL is not visible on the screen. It is also not the clean address of the linked page. Because the link passes through a Microsoft redirect host, the address can be long, complicated, and meaningless to the person. it is aAn accessibility and productivity defect that Microsoft should fix in the Loop component itself.

What the screen-reader user hears

Imagine reviewing an AI summary with several links. A sighted reader sees a short phrase that identifies each destination. A JAWS user may first have to listen to a stream of domain names, path segments, parameters, and other redirect information that never appears visually. Only after that interruption does the meaningful link text arrive.

Microsoft describes Loop components as portable content that stays synchronized across Microsoft 365 apps. That portability makes the component's accessibility especially important: a defect in the component will follow the content wherever it is embedded across Microsoft's products using the same rendering engine.

Microsoft's own accessibility guidance says that hyperlink text should clearly and accurately describe its destination. That benefit is lost when the screen reader must speak a long machine-oriented address before the description, but I'm glad to see someone at Microsoft thought to properly document the preferred behavior.

This looks like a Loop rendering problem

The expected experience is straightforward: when focus reaches a hyperlink, JAWS should announce that it is a link and read its visible, descriptive text. The raw destination should remain available through a deliberate command for anyone who wants to inspect it, but it should not interrupt ordinary reading.

How to fix it?

Microsoft should test AI-generated summaries in Loop components using current versions of Teams for Windows and JAWS, then make sure that:

  • each hyperlink exposes the same meaningful text available visually
  • redirect URLs are not included in the link's accessible name or description
  • JAWS announces the link text without speaking the hidden address
  • the underlying URL remains available only when the user intentionally requests link details

Loop components are meant to make collaboration faster and easier. This is a focused bug with a clear outcome: let people hear the useful link text first just like any web browser has for decades. I suspect Microsoft will get this one fixed soon, seems easy enough, especially with Github Copilot at ones fingertips.