GOV.UK found that type=number actually hurts accessibility and is riddled with usability problems:
https://technology.blog.gov.uk/2020/02/24/why-the-gov-uk-des...
https://technology.blog.gov.uk/2020/02/24/why-the-gov-uk-des...
> cannot be dictated or selected when using Dragon Naturally Speaking
Isn't this just a speech-to-text engine? I can say that I haven't ran into anyone using this for web control in my entire career. I'm certain it has an accessibility use-case and all, but I haven't ran into a practical example. I'm very apt to write this off as "moot," and would also suspect it may have been addressed since 2020.
Does anyone here use Dragon Naturally Speaking for web control? Good faith real question.
> appears as unlabeled in NVDA's element list
Fixed - https://github.com/alphagov/reported-bugs/issues/41#issuecom...
> appears as a spin button in NVDA's object navigation, which has an edit field and two buttons inside - those buttons are unlabeled, but decrease/increase the value
Fixed - https://github.com/nvaccess/nvda/issues/9675#issuecomment-59...
> is reported as unlabeled edit field when using nvda+tab
Fixed - https://github.com/nvaccess/nvda/issues/9675#issuecomment-59...
---
I want to point out that this article is out of date and basing any sort of modern FE development decisions on it merits much more research than just "GOV.UK tried it and it hurts accessibility" ... I attest that not using the correct input type on fields is more of an accessibility issue - especially numeric fields.