2

I just filled another form on an English website that didn't have name set for the HTML "submit" button. The browser filled in "Prześlij", which is "Send" in Polish. Given how many pairs of website and browser languages there are, I wonder if this automatic naming of controls can cause problems. Does this featuer of automatic button naming can lead to actual errors in some cases when the user assumes that the name of the action is spelled out in the website's language, but it's actually in the browser's one and the same word means two different things?

  • Is this a UX question, or a technical question? – Majo0od Oct 5 '15 at 15:37
  • I'd say this is a UX question: "does the combination of browser and website language affect UX if we leave button naming to the browser"? – d33tah Oct 5 '15 at 15:43
  • In that case, consistency needs to be there. Changing continuously like that can cause confusion. – Majo0od Oct 5 '15 at 15:45
  • The problem is that we do know that people sometimes forget about consistency or don't care about it at all and let the browser fill the button name for themselves. I wonder if this can lead to serious mistakes when the names are truly misleading. – d33tah Oct 5 '15 at 15:55
1

"Submit" in English is the most benign wording for literally "send". I'd imagine it's been named consistently in all localization formats. I would say browser localization is done by native speakers of the given language, and have been vetted by browser users. So the chances of the localization using ambiguous wording is rather low.

Another thing is, web forms has been around since late 1900s. If there's a single primary button on a page. It should be pretty obvious that you'll need to press it for the page to do something.

If there's more than 1 button and the developer is too lazy to label them, then I think you have bigger problems then the browser automatically naming them "submit".

  • Ambiguous wording isn't what I was worried about - it's rather the difference between browser language and website language in context of browser deciding what the button should say. – d33tah Oct 6 '15 at 21:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.