label–input relationship

[IschaGast]

The annotation kit does a great job documenting input attributes, but currently misses an important semantic dependency: the label–input relationship.

In the current UI, inputs (text, checkbox, radio, etc.) are shown with extensive attribute details (type, required, autocomplete, etc.), but there’s no clear indication whether an input has an associated label or where its accessible name comes from.

It would be really helpful to make designers and developers more aware that an input can’t really exist without a label, and to surface that relationship more explicitly in the annotations.

A possible solution could be something simple, like adding a label section at the top of the input details.