Non-role input types require an accessible name

[WilcoFiers]

Noticed this when reviewing the form control rule. I think we need to do the same for the Form field label is descriptive rule. Leaving this as a draft PR until then.

Need for Call for Review: 1 week

---

How to Review And Approve

• Go to the “Files changed” tab
• Here you will have the option to leave comments on different lines.
• Once the review is completed, find the “Review changes” button in the top right, select “Approve” (if you are really confident in the rule) or "Request changes" and click “Submit review”.
• Make sure to also review the proposed Call for Review period. In case of disagreement, the longer period wins.

[Jym77]

Closes #2123.

[giacomo-petri]

Already approving. Good catch @Jym77

Changes made

[Jym77]

Minor improvement on the background note.

[Jym77]

Suggested change

	This rule does not test other control-like roles such as `button` and `menuitem`, because these do not inherit from `input` or `select`. These should be tested separately. Because certain input types such as date and color have no semantic role, these are listed as a separate item in the applicability.
	This rule does not test other control-like roles such as `button` and `menuitem`, because these do not inherit from `input` or `select`; these should be tested separately. This rule does test certain specific input types such as date and color because they have no semantic role, but still require an accessible name.