Custom tag names do not supply native semantics

Naming an element like a button does not give it native keyboard behavior or accessibility semantics.

A compact custom tag can hide implementation complexity while leaving essential interaction responsibilities entirely with its author.

HTML explains that browsers and accessibility tools do not recognize button semantics from a custom name.

Authors must provide appropriate names, states, focus handling, and keyboard interactions whenever native behavior is not inherited.

If semantics preserve meaning, keyboard testing must verify behavior beyond a component's visual appearance.

ElementInternals supports default accessibility semantics and form integration, but those hooks still require a complete implementation.

Prefer native controls within reusable components when possible, and justify replacements through demonstrated interaction requirements rather than shorter markup.