Alt text, labels and buttons: small defects, large barriers
Many accessibility problems are small in code but significant in use. An image without an alternative, an unlabeled checkout field or an icon button without a name can hide information or functionality from screen-reader users.
Alt text needs purpose
Alternative text should communicate the function or meaning of an image in context. Decorative images usually need an empty alt; product imagery may convey important information.
Automation can detect a missing alt attribute, but usually cannot decide whether the wording is genuinely appropriate.
- Describe relevant meaning rather than every visual detail.
- Use alt="" for truly decorative images.
- Avoid filenames or generic text such as “image”.
Labels and accessible names
Inputs need programmatically determinable names. So do icon-only search, menu and cart buttons.
Prefer visible labels where possible. ARIA is useful when native HTML is insufficient, but it should not mask unclear interfaces.
- Associate labels and inputs correctly.
- Give icon buttons a meaningful name.
- Ensure ARIA references point to existing IDs.
FAQ
Is any non-empty alt text sufficient?
No. It needs to be appropriate to the image’s purpose and context, which often requires human review.
Should aria-label replace visible labels?
Usually not. Visible labels are robust and also help sighted users.
Official sources: European Accessibility Act and W3C WCAG
W3C WCAG 2.2
General information, not legal advice or a formal WCAG conformance statement. Automated checks do not cover every accessibility criterion.
Map your technical accessibility risks first
The free Quick Scan checks up to 5 representative pages. The paid Risk Report scans up to 1,000 publicly discoverable pages in the background and is emailed automatically when complete.