Steps to reproduce:

Firefox/Chrome address bar:

data:text/html, <label for="spin">Spin</label><input id="spin" type="number" min=3 max=10 />

For IE and Edge, paste this in a HTML file.

Expected behavior:

Equal presentation in Browse mode and equal quick navigation behavior

Actual behavior:

• Firefox 54: presented as spin button with edit control, navigable with e and f quicknav
• Chrome Canary 61: presented as spin button editable, value presentation is entirely broken. only f quicknav works
• Edge: Presented as spun button, no value presented. Focus mode allows to change the value accessibly. No quicknav possible
• IE: presented as edit box

Things to do

• Add UIAHandler.UIA_SpinnerControlTypeId to quick nav for form fields and probably buttons

Nuts to crack

• Should we treat spinners as edit boxes or buttons, or even both?
• Should we treat oleacc.ROLE_SYSTEM_SPINBUTTON as buttons?
• Should we force the NVDA role in IE to spin button for input="number"? Probably not, as it seems IE entirely lacks support for spin buttons.