is-aesthetic

All checks

Controls are labelled on screen

Functional and interaction support · essential check · measured from the page’s layout and styles · C108.1

Fields need visible labels, and icon-only buttons should be few and use familiar icons.

When it fails
Controls have no visible label: a field has no visible label after the documented search-field exceptions
Warns when
A nonstandard standalone icon control needs a label
Passes when
Fields are visibly identified and standalone icon controls are clear
How to fix it
Give every field a visible label, since placeholders vanish while typing. Add text to icon-only buttons, or keep them to familiar icons (search, close, menu) with an accessible name and a tooltip.

Its threshold is a starting value that we still calibrate against real pages.

On the public reports

warns on 5passes on 2of 7 sites

figma.com7 controls without a visible label · scores 78
  • Flagged element on figma.com at 1440 px1440 px
vercel.com3 controls without a visible label · scores 73
  • Flagged element on vercel.com at 1440 px1440 px
  • Flagged element on vercel.com at 1440 px1440 px
www.benchflow.ai2 controls without a visible label · scores 50
  • Flagged element on www.benchflow.ai at 1440 px1440 px
  • Flagged element on www.benchflow.ai at 1440 px1440 px
www.python.org1 control without a visible label · scores 71
  • Flagged element on www.python.org at 1440 px1440 px
  • Flagged element on www.python.org at 1440 px1440 px
www.wikipedia.org2 controls without a visible label · scores 79

No element pictures were kept for this result.

Passes on is-aesthetic.com and www.gov.uk.

Public reports are the sites listed on the home page, each as last scanned. Pasted pages are never included.