An ARIA label is the aria-label attribute, a small piece of HTML that gives an element a name spoken by assistive technology. When a control has no visible text of its own, a screen reader has nothing to announce, so it might just say “button” and leave the user guessing. The ARIA label fills that gap with a clear name like “Close menu” or “Add to cart”.
The classic example is a button that shows only an icon, like a magnifying glass for search or an X to close a pop-up. To a sighted visitor the meaning is obvious, but a screen reader sees no words at all. Adding aria-label="Search" is like writing the name under a wordless pictogram in an airport: the symbol stays, and now everyone knows what it means. It is one of the most common pieces of ARIA, and it lives directly in your HTML markup.
The label is invisible on screen. It changes nothing about the look of the page and only affects what gets read aloud, so it costs nothing in design while making icon-driven interfaces usable for people who cannot see them.
There is a right and a wrong way to use it. The name should describe the action, “Close” rather than “X icon”, and it should not repeat text that is already visible, because the screen reader would then announce the same thing twice. There is also a sibling attribute, aria-labelledby, that points to text already on the page instead of typing a new string. Used with a little care, the label is one of the cheapest wins in UX design.
At TopDevs we add ARIA labels to every icon button and ambiguous control we build, so a clean, minimal interface stays fully usable for screen-reader visitors.
