Name every button: an app that works with screen readers works with AI
Toba
A sighted user sees a gear icon and knows it opens settings. A screen reader sees a button with no name. So do voice control, automated tests and the AI assistants that now operate web apps for people. They all find their way around through the names and roles the browser exposes for each element.
When Skavelo learns an app, it lists the places where those names are missing or unclear. Four kinds come up again and again, and each has a small fix.
Buttons, links or fields with no name
An icon button with no text has nothing to call it, so nothing can mention it or point at it. Give each one a name: visible text, text hidden from sight but kept for screen readers, or an aria-label, as in <button aria-label="Settings">.
Labels that aren’t tied to their field
A label that only sits above a field looks connected, but the browser doesn’t know it. Clicking the label won’t focus the field, and tools have to guess which label belongs to which field. Tie them together with matching for and id, as in <label for="street"> and <input id="street">, or put the field inside the label.
Fields named only by their placeholder
A placeholder is an example value, and it disappears as soon as someone types. A field named only by “Acme Inc.” gets described as Acme Inc. Add a real label, like Company name, and keep the placeholder for the example.
Clickable boxes that aren’t buttons or links
A div with a click handler works with a mouse, but keyboard users can’t reach it, and tools may not see it as something to click. Use a button or a link. If the div must stay, give it role="button" and tabindex="0", and handle the Enter and Space keys.
Finding them
Your browser’s accessibility inspector shows the name and role of any element. Automated checks such as Lighthouse’s accessibility audit or axe find many of these across a page.
Skavelo lists them after each learning run under Suggestions for your developers, grouped by kind with the screens where they appear. Each group has a prompt your developers can paste into a coding assistant such as Claude Code or Cursor to fix them, and fixing them makes Skavelo’s walkthroughs more reliable.
Every name you add helps someone using a screen reader today, and every tool that reads your app tomorrow.