Häufige Fehler bei der Benennung, die Steuerelemente stumm schalten

A control with no computed name is read as just button or link. These naming mistakes leave users guessing what an element does.

A button holding only an icon often computes no name. Add an aria-label so the wordless control still announces its action.

A placeholder is not a reliable accessible name. It vanishes on typing and many readers ignore it, so add a real label.

An aria-labelledby pointing at a missing or misspelled id produces no name at all, silently undoing the label you intended.

An aria-label set to an empty string wipes out the name. The element ends up with nothing for a screen reader to announce.

Putting aria-hidden on the only text inside a button removes its name source, so the control becomes anonymous to readers.

Links named Read more or Click here are technically named but useless out of context, since users hear no destination.

Relying on title as the only name is risky. It is the lowest priority source and several screen readers skip it entirely.

A bare input with no associated label often computes no name, leaving users unsure what to type into the field.

Ten buttons all named Edit force users to guess which row they affect. Give each a distinct name that includes its target.

Open the browser accessibility panel and read the computed name for each control. If it is blank, you have a mistake to fix.

An icon button shows only a trash glyph. Why might it be silent?

You learned the traps that silence controls, from icon-only buttons to broken ids, and to verify every name in the inspector. ✅