91–100 of 621 posts
On Android, long press home button activates Google Assistant that can OCR the current screen and translate immediately. Unironically one of the only two features keeping me on Android until now.
Earlier quoted context omitted.
That was not implied by the post.
The post implied the opposite. However, if the German girl writes in German, probably she wants to date in German, the dating platform follows her wish by making it hard to extract the text, translate it, and eventually waste her time.
In the case that it is in another language, I'd probably just use google translate if I'm not fluent enough in reading the language.
But for apps... good luck finding a solution.
At least Twitter, which I use the most, lets you select text.
The one I hate the most is Spotify. Copying the name of a song or an artist is something I do regularly, yet there’s no way to do it in the app.
Earlier quoted context omitted.
I think a way to resolve things like this is to have media features. For example: @media(prefers-user-select: all){ * {user-select: all;} } But that wouldn't guarantee you could select text on an interactive element, plenty of other things could prevent it. If it was an established known issue, then maybe people would do something like: :not(:lang('base-lang')) { * {user-select: all;} } It looks like there are plenty…
Yeah that's possible for us geeks ;) But UX talks about how everyone interacts with our site. We couldn't just ask all visitors to be experts.
It doesn't. It should, in an ideal world, but it definitely isn't the goal of people who design human-computer interfaces to allow everyone who interacts with a computer to be happy with the way it functions.
As a web dev, I fully agree with this, but with a huge exception: clickable text. Anything that is meant to be read as content should absolutely, without fail, be selectable and copyable (assuming appropriate permissions). But stuff like tab headers, buttons, or even text-sparse tiles - things meant for the user to click on - can, and usually should , prevent text selection. It is super annoying to be clicking back a…
Real-world example I use nearly daily: Selecting the nav header that's the ticket number in our ticketing system. I copy-paste the number elsewhere. Of course there are many other bad design decisions that go into requiring me to do this, but it's still a real example of why all text should be selectable.
Earlier quoted context omitted.
Give me an example of a real-world use case where this caused you an issue, and I'll show you where their UX design is poorly made, rather than a need for selectable text in a clickable element.
Sure, I had one recently. There is a certain page of one of the Bundesagentur für Arbeit websites that doesn't play well with automatic translation. I speak B2 level German, but even then some of the technical terms are still complicated or unknown for me. This included one very long German word that was in a BIG RED button and the text in the big red button was not selectable, in the manner described in the article.
I think I found your problem. Not sure why you think the solution is to make everything work worse for keyboard users.