Improve back button and progress wording during sign up

[andrewserong]

This issue continues discussion raised in #34299

We have a back button, that replicates the browser back, to reassure people that nothing is going to blow up if they press our back button.

Agreed with @fditrapani here.

--

Based on this definition, we might choose to update the Back button's label:

Regardless of the behavior of the back button, I really like the idea of improving the label. @ramonjd's suggestion of "Back to {{step title here}}" might be a little too verbose. We could take a cue from iOS and just shorten the label to "{{step title here}", like this:

This could get tricky on smaller screens, where our horizontal space is limited. We could remove the label and/or adjust the layout to make room.

Another option is to remove the back button and list the steps available:

I like this option, as its more clear what's happening. But, if steps change, we'll need to do something to accommodate. That is, can we accurately list the future steps without knowing the answer to the current question?

This also presents some challenges on mobile. We could get creative and show the list in some sort of dropdown, or revert to a more standard back button.

Originally posted by @shaunandrews in #34299 (comment)

[andrewserong]

The tasks out of this issue are:

Short term

• Update the back button text to: "{{step title here}}", and carefully test the length of the step titles on mobile.

Long term

• Explore the idea of listing the steps available instead of the back button, like in the design above ☝️ — this can be discussed here, but might need to be split out into separate issues if we reach consensus on the approach.

[ramonjd]

Did an experiment for the short term work

#35082

Might need shorter titles....

[ramonjd]

Related issue: #34598

[ramonjd]

Related issue: https://github.com/Automattic/zelda-private/issues/121

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.