Editorial: Clarify / make consistent naming steps for HTML form controls

[scottaohara]

This should not contain any normative changes

• Updates the listed inputs and button types to steps more consistent in wording.
• incorporates https://github.com/w3c/accname/issues/246 into the label steps for the mentioned form controls
• starting to migrate from just using "subtree" to "text equivalent computation of the element's subtree" - as the simple use of 'subtree' has come up in a handful of reviews for html aam naming steps (this is new in these steps, but the behavior is already reality)

the "other form controls" is not touched in this update - as there are also other pending PRs - re select element - that start breaking that apart.

[netlify[bot]]

✅ Deploy Preview for wai-aria ready!

Name	Link
🔨 Latest commit	9f0b2fb22b519c2d4390ff9a73b1832e76740e32
🔍 Latest deploy log	https://app.netlify.com/projects/wai-aria/deploys/68389f894f73860008436d83
😎 Deploy Preview	https://deploy-preview-2395--wai-aria.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[scottaohara]

There may be some minor conflicts to resolve with https://github.com/w3c/aria/pull/2530 since they're touching similar areas of the spec.