I've been using only English interfaces for more than a decade, but recently-ish relived the phenomenon with MS Office, and it doesn't get easier with experience.
Speaking of computing and translations: the most annoying case I've had was not with UIs, but with books. Back in the day, I bought two C++ books by Scott Meyers (Effective C++ and More Effective C++), both published in Polish, and each by a different publisher. In the first one, they translated "template" -> "szablon" and "pattern" -> "wzorzec", and in the other, they translated "template" -> "wzorzec" and "pattern" -> "szablon". Took my teenage mind quite a while to make sense of the confusion.
1. The user is drunk, and can't understand meaning of the text.
2. The user is preoccupied with other tasks, and skips over the words.
3. The user is illiterate. Functional illiteracy is prevalent in the United States, and being unable to recognize the characters of one's own language continues in many countries, too
My company invests in ensuring many of their products are usable for the illiterate. I doubt it's the only company that does so.
Adding to this, I'm curious how someone who cannot recognise the characters of their languages would use input fields, too? I don't think I know of many input fields which are particularly accessible if one doesn't recognise language characters without using speech recognition (which kind of sidesteps the issue).
Put in my postcode & choose my address; choose a pizza size & toppings from icons/photos.
Add credit card info into a standard looking form & that's it (or even, touch the fingerprint sensor when the fingerprint icon comes up)
I think the trouble isn't that you wouldn't know the Spanish for "OK" (or "pepperoni") but if the app lacks proper information hierarchy so you don't know what to do next.
It is the goal, if you’re designing any kind of graphical app.
Drivers and platforms definitely don't want too intoxicated passengers. Reasonably drunk? Sure. Completely high/passed out/etc? Nope. It's just too much of a mess to handle. There is indeed a vomiting fee, but it's more used as a deterrent for the users: it does not cover the actual cleaning + lost rides on a busy Saturday night...
Bit of anecdata: sexual intercourse in the car is also not ok, and gets you banned. Yes, it happens. Drivers don't like it.
To expand on this: the mapping between images and other cues to a precise meaning is often actually pretty poor. To correctly navigate using images you often have to have prior knowledge, with the exception of the most downright obvious images or visual cues possible. On the other hand, text can have essentially arbitrary precision (although past a certain point it becomes difficult to parse) - and is thus actually often superior for first-use (or infrequent use) scenarios. The ideal is to have the best communication possible, and while I'm not sure as to the extent that Uber reaches that goal, text being unreadable and the app being unnavigable because you changed the language is, in my view, more on you than on the app developers.
Let's say you're in Europe and and have a card in dollars:
[] 1000€
[] 1000€ (1€/1.2$ -> 1200$)
But they’re usually designed in such a way that it’s impossible to hit a wall, and worst case you pay a $5 fee.
Anyway, I digress...
The correct user-focused interface solution for that particular problem is to show the actual costs next to each button. And then I'd think one would make the cheaper option the obvious default (e.g., bigger, greener), with the more expensive option less favored.
This is good design and an illiterate person could be walked through this a few times and could then do it anywhere.
Bad design is relying on your users continually having to teach themselves how to use your app.