#Jotform form software

#Jotform form software

So, Safari is on 15 and according to it is 0.02% the market share.Д®very time we create software targeting the browser as a presentation layer we have to ask ourselves what the acceptable market cut-off for browser support is. Doesn't make this less of a disaster for users on Safari 5.1 Most people aren't inputting numbers that large into an application and it can actually be considered a bad UIX practice (ex: making someone enter a large value in bytes vs. While I have ran into these use cases, I 100% consider them to be edge. Sometimes yes, those extreme values can cause weird non-intuitive behavior from the number field. Your point is valid for very large numbers, or numbers with incredible precision.

type='number' specifically is for when a field is a numeric 'value' - this is not the case with a CC number as it's a sequence of digits (as-in the value of the digits doesn't mean anything). Whatever the case is, it is considered a bad practice to use type='number' for a CC field. and funnily enough many people will sorta hijack the functionality of the using 'pattern' and other attributes to input them correctly. So, just like a telephone number - CC #'s are not technically numeric as they're more accurately thought of as a 'sequence of numbers'. Because while it might look like your credit card number is 4000 0566 5566 5556, what you want to put into the form is 4.000056655665556e+15 > Values in a number input are automatically rounded or even converted to exponential notation by the browser. Yeah - I guess I expect the section named 'Accessibility' to be about the concept of accessibility. > But you appear to have confused the article section titled 'Accessibility' with the concept of accessibility. It is not necessary to dispatch mouse events to child elements - anyone who clicks on the input element to focus there has now positioned their cursor directly over the input element. It's not hard to run into the mousewheel issue. > The arguments made against the 'numeric' field here are out of date, and not something I have ever ran into with my own testing. NVDA now has better visibility into number input elements.Дў. which ones sound like they're worse problems? Imagine this changelog:ДЎ. Values within a number input change at random if the user's mouse has a mouse wheel.Д«etween the issues that have been fixed, and the issues that haven't been fixed. Doesn't make this less of a disaster for users on Safari 5.1.) Safari 5.1 inserts commas into 'number's with at least 16 digits. Because while it might look like your credit card number is 4000 0566 5566 5556, what you want to put into the form is 4.000056655665556e+15. Values in a number input are automatically rounded or even converted to exponential notation by the browser. Here are some accessibility issues, also mentioned in the article, that you didn't bother to address: and they're unlabeled when using nvda+tabД«ut you appear to have confused the article section titled 'Accessibility' with the concept of accessibility. plus, they look weird in NVDA's object navigation

number inputs appear unlabeled in NVDA's element list A number input blocks dictation and selection when using Dragon Naturally Speaking 'Many of the issues are resolved since it came out'. Reading that response was a surreal experience. gov.uk article and it's from 2020 and many of the issues are resolved in the years since it came out. I attest that not using the correct input type on fields is more of an accessibility issue - especially numeric fields. 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'. > is reported as unlabeled edit field when using nvda+tab > 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 > appears as unlabeled in NVDA's element list I'm very apt to write this off as 'moot,' and would also suspect it may have been addressed since 2020.Дoes anyone here use Dragon Naturally Speaking for web control? Good faith real question. I'm certain it has an accessibility use-case and all, but I haven't ran into a practical example. 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. > cannot be dictated or selected when using Dragon Naturally Speaking

many of these issues are no longer a thing and/or are just really weird to call out.