[meta] Update the user-edit pages

I went through the idea and core issue queue looking for related issues as well as found one or two potential issues i was unable to find any existing issues for yet. I try to sort the found issues based on the categories used in the issue summary and provide a few comments for each.

Information architecture (menu structure, path structure)
Not directly related but related to the issue here since you are able to adjust the appearance and structure of the user profile page in admin/config/people/accounts
#715972 - People section(s) are very confusing

Page titles
An issue we talked about in the UX meeting a few weeks ago in the context of content types but it applies for this issue as well. Will have a chat about the issue at next weeks A11y office hour.
#2514218 - Drupal 9.4 [regression] Pages Manage Fields, Manage form, Manage display should include name of content type or entity )

Grouping fields on one or more page
The following two issues are internationalization related. The first is about creating a dedicated fieldset for all the fields related to language and time zone (but might extended in our context to a dedicated form like the email address and password form). While the second issue is about a centralized and extended internationalization support in Drupal. It would/might entail an extended configuration on a per user level as well.
#134209 - Join language and timezone settings in one single fieldset
#378468 - Add central localisation support (currency, decimals etc.)

Field labels and descriptions
In the context of canceling an account there is a mixed and inconsistent terminology. On user/2/cancel you have the option to disable or to delete an user. When you disable an account and check admin/people afterwards the status reads blocked instead of disabled. Disabled would be more consistent and clear to the user (eventhough block and disable are synonym in this case it seems while blocked is used in the code). In a similar vein is the following issue which extends the number of statuses and makes them customizable
#3225766 - Add more user status and make customizable

On the user profile you have currently two fields current password and password. It would be more clear to use something like Enter new password or New password like suggested in #1259892 - Users could not find the Change password fields

User experience (UX) when editing and submitting the form
That issue would apply to the new email & password form @jidrone is working on. It removes the need that an email is required to have a Drupal account
#286401 - Make email not required for a Drupal site account

Currently the fields on the user profile page have highly differing widths. The following issue for Claro makes those more consistent.
#3092296 - Limit width of form elements (max-width)

One detail i consider highly confusing from a user perspective is the disconnect between the node edit form and the manage form display page. Especially for the user profile page its demanding and confusing. I've added an age field to the user entity type (account_manage_fields.png). If I now compare edit_profile.png and account_manage_form_display.png there is a disconnect

edit user profile --------------- manage form display
==============================================
current password --------------> username and password (hard coded block)
email address
username
password
status
roles.
picture -----------------------> picture
language settings --------------> language settings
contact settings ----------------> contact settings
age --------------------------> timezone
locale settings -----------------> age
*NoCorrespondingComponent* ---> language code

Several fields in the edit user profile form are combined into the username and password field in the manage form display. And especially for the different fields language settings, timezone, language code its difficult to find the corresponding components on the edit user profile page. On top the order is not consistent as well for the added field age. Difficult comprehension wise (there is a similar but different pattern for content types).

With the current implementation of having to confirm the new password there is an issue about that the password confirm field type should support the #maxlength attribute as well.
#1344552 - Password confirm field type should have support for #maxlength attribute (obsolete as soon as #2293803 lands)

Then there is the issue to remove the confirm password field and introduce a show/hide functionality for password fields
#2293803 - Replace confirm password field with show/hide functionality

Related to the new password field is a potential new issue about the password suggestions block which is currently placed right after the confirm password block. I've brought up a question in the #accessibility channel on the Drupal Slack if it is a known issue and an issue already exists or if it would be reasonable to open up a new issue for that: https://drupal.slack.com/archives/C2ANFUGGG/p1639278510148000

And depending on how the password confirmation problem will be solved for changing password and email addresses there is also a related issue we talked about in one of the UX meetings
#2883755 - Introduce a submit confirmation step modal to Form API for usability

And then there is also a list of issues loosely related to the user profile page. I am unsure if those would make sense to make child issues or at least related issues? Those are about password strength and account security:
#1824800 - Require a (configurable) minimum password length for user accounts
#1497290 - Check for common words in password strength indicators
#2855328 - Password and confirm password should be mandatory fields while setting up password using one time link following by email

Those are about email verification:
#85494 - Use email verification when changing user email addresses
#286401 - Make email not required for a Drupal site account
#2346389 - Prevent registered e-mail address enumeration via user registration form

Okay thats it for now. Was uncertain if all the issues i've found would make sense to add preliminary as child or related issues for the scope of this idea/issue (am still struggling to find my way in the issue queue). So a brief feedback would be welcome as well as for the two or three points without an issue yet and then i will perform the subsequent steps.

This issue would also be relevant here.

added #3344546: The language settings field widget behaves confusing depending on if the language module and or an extra language is installed as a related issue. it is about one aspect of the manage form display account settings disconnect with the user edit pages mentioned in #2

@mgifford just created a new issue for adding a page about a11y to the user profile page: #3393367: Add a section to the user profile to store accessibility preferences. that issue would also be relevant for this issue here.

The Ideas project is being deprecated. This issue is moved to the Drupal project. Check that the selected component is correct. Also, add the relevant tags, especially any 'needs manager review' tags.

Adding 'meta' because there are child issues.

Changing to the standard issue template would also help other contributors.