Plenty of interfaces mimic a form process. If that's the case, and it's really just a page positional thing (not state), I see no problem making button-based navigation.
We don't scream and shout that page nav links all look like content links, after all. Well, maybe you do, but it's not 1996 any more.
Disclaimer: Ana is a very dear friend of mine and may well be the Best Person™. Ana, if you’re reading this, the live-coded karaoke talk you gave at State of the Browser was the best I’d seen in years.
All of my pals laugh at me for carrying a packing square with USB C–C, A–C, Lightning, EU adapters, and three-pin plugs. Until they need to borrow one.
I’m a web performance engineer — I help clients find and fix site speed issues — but recently I spotted what I thought might be a security/privacy issue. Security not being my specialism, I asked Fable to help me triage and, if necessary, raise the issue with my client.
It refused. It’s so so so adjacent to the work we’d already been doing, but the moment I asked it to help me understand what I thought I’d found, it left me high and dry!
Sometimes the context where Fable drops to Opus 4.8 is enough for Opus 4.8 to do a first pass on everything, then I start a new session and Fable will happily refactor/improve it.
Please, just use a link. This has a destination, so making it masquerade as a button gives so many false affordances.