Your `

That is it. One word, doing the disambiguating work, sitting next to a role the platform is already announcing for free.

The principle generalises

The source extends the same idea to alt text, and it is worth carrying across because it is the same shape of bug. An is announced as an image. Writing alt="Image of a red bicycle" tells the user “image, image of a red bicycle.” The word “image” inside the alt value is restating the role of the element it lives on.

The corrected version is the obvious one:

 src="bike.jpg" alt="A red bicycle leaning against a brick wall">

The image-ness comes from the element. The alt value describes what the image shows. Two different jobs, two different places to do them, no overlap.

You can apply the same test wherever you write an accessible name. If the role of the element already announces a noun — navigation, image, button, list — that noun does not need to appear inside the name you write. The name is for the thing only you know: which navigation, which image, which button.

Why this keeps happening

The habit usually comes from a good instinct. Authors want to be explicit. They want the label to read cleanly when they say it out loud in a design review. “Primary navigation” sounds more complete than “Primary.” It is the kind of small extra word that feels respectful, the way you might write “click the Submit button” in instructions.

But the audience for an accessible name is not a sighted reviewer reading the attribute. It is a person hearing the role and the name back-to-back. “Complete” sentences in that channel become repetition. Graham closes the link-post with the related guidance that accessible text should be kept succinct — per the source, “it doesn’t have to be a novel.” That instruction is doing more work than it looks like.

Once you start listening for the doubled role-name, you start noticing it everywhere — the