A button without a label should fail the build

A button without a label should fail the build.

Not warn. Not pass with a note in a report someone reads later. Fail — the same way broken code fails.

That is the point of highly opinionated components. A button requires a clear label. A form field requires a label tied to it in code. Color pairings come from tokens tested for contrast, not from a hex value typed in on deadline.

When those rules live in the component and in the pipeline, accessibility stops depending on memory, good intentions, or a final audit. The inaccessible version is simply harder to ship than the accessible one.

Designers and developers still make the real decisions — content, hierarchy, flow. The system just refuses to let the basics break underneath them.

Build the guardrails into the shipping process. Then good practice is not extra work. It is the default path.