[proposal] enable input-label association without explicit ids

[samrichardsontylertech]

Proposal

It's currently necessary for consumers to supply each <input> element slotted into a Forge component with an id and the associated <label> element with a for attribute pointing to that id. This is usually a reasonable ask, but with larger forms that may be dynamically generated or split across different files it can be hard to ensure that ids are all present and unique. It's become a common gotcha and a source of occasionally hard to track down bugs.

We should be able to implement a solution to allow creating accessible form fields without requiring explicit id and for attributes. There are a few initial options to consider:

• An optional label property like the one exposed by the forge-select component
• The components could auto-generate id and for attributes if missing
• If possible, we could allow the native <label><input /></label> pattern

None of these solutions would replace the current pattern, but provide a simpler syntax for basic use cases.

Affected components

All components that accept slotted <input> and <label> elements, like the text field and radio button.

Benefits

Simpler, cleaner, and less bug-prone code.

Caveats

Allowing multiple ways to label inputs might result in conflicts or confusion.