Keyboard access starts with the right element. A native button already has a tab stop and activation behavior; a styled div doesn't gain those properties from its appearance. Keep controls in a sensible source order and avoid positive tabindex values that create a second, competing order. Some controls need extra information. An icon action needs a useful name, and a field can connect to help text through aria-describedby without replacing its visible label. You'll inspect those relationships and activate the controls in the preview. An empty count, nested icon, or repeated action should not change which control receives focus or what its name means.