Does a textbox within spinbutton need to be labeled?

[JAWS-test]

https://rawgit.com/w3c/aria/master/#spinbutton:

Authors MAY create a spinbutton with children or owned elements, but MUST limit those elements to a textbox and/or two buttons.

With this variant, it is unclear whether the spinbutton or the textbox or both must be labeled.

Textbox and spinbutton have: "Accessible Name Required: True". However, the question is whether the label really needs to be specified twice

[scottaohara]

Having performed some initial testing with this variant on macOS/iOS, results of it being exposed correctly are rather poor. Obviously need to do more tests on other platforms, but I wonder why this version is necessary if having a textfield/spinbutton and adjacent buttons has far more robust support anyway, and the effort to style it similarly to a nested option would be negligible?

Interested to hear use cases where this variant pattern would be necessary, rather than the alternative to have the text field and buttons be siblings?

[JAWS-test]

@scottaohara Maybe you can share your test example, then I will test with other screenreaders

[pkra]

Just a note: since the line was last changed 4 years ago, it might see some changes related to #1213 and other 1.3 work.