That’s aligned with semantic intent: native elements give you built-in keyboard and screen reader behavior, and separating “action” vs “navigation” avoids a lot of a11y debt. When your “button-looking link” is disabled, how do you implement that so it remains accessible (including keyboard and screen reader behavior)?