[PP-1] Make the titles for the field creation flow more consistent and communicate that it is a multipage form

Problem/Motivation

This issue is a followup for 📌 [PP1] Refine field descriptions Active . It was raised during today's ux meeting 📌 Drupal Usability Meeting 2025-05-23 Active . The attendees were @benjifisher, @rkoller, and @simohell. 📌 Drupal Usability Meeting 2025-05-23 Active is about refining the labels and descriptions used within the workflow for creating a new field - that happens in a multi-step form within a dialog modal.

Problem is, currently there is no consistent naming pattern for the titles of the dialog modal for each step. At the moment the two to three steps are labeled as follows:

1. Add field
2. Add field: Formatted text
3. Info text settings for test (info text -> field type label, test -> content type)

One problem with the example of the three step process, add field is front loaded for the second step, that way the first two words are redundant. Then in regards of consistency, the third step is adding the name of the content type the field is added to, while the other two steps omit that information. But overall the two to three titles have the same problem like before when the flow was on dedicated pages, just based on the title it is not necessarily apparent that you are in a multi step flow, neither for people with a short working memory nor screenreader users.

Steps to reproduce

Proposed resolution

The suggestion would be to follow a modified variant of the pattern outlined in approach 1 on https://www.w3.org/WAI/tutorials/forms/multi-page/ . But instead of using Step x of y: simply go with Step x: , that avoids any complications, cuz the decision if the multistep form has two or three steps is based on the choice made on step 1. We haven't discussed the exact wording of the titles yet, we just wanted to move the discussion about the wording of the title into a followup issue to contain the scope for 📌 [PP1] Refine field descriptions Active .

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet