Release v4.4.1
The NumberInput pages claimed role="spinbutton" with aria-valuenow and a formatted aria-valuetext. React Aria deliberately does not take that role — it suppresses text editing in several screen readers — and names the control with an aria-roledescription instead.
The practical consequence is that there is no range announcement, which is exactly what a consumer needs to know when choosing between this control and the native NumberField. Found while migrating an application off a third-party numeric input, where the documented contract did not match the rendered DOM.
Fixed
- Document the real accessibility contract of
NumberInputandNumberInputField, including the missing range announcement and why thespinbuttonrole is not used (#175)