3 ms·
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 selec
by catapart 1y ago
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.
- whstl 1y agoSure, 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.
- catapart 1y ago> that doesn't play well with automatic translation. I think I found your problem. Not sure why you think the solution is to make everything work worse for keyboard users.
- whstl 1y agoAnd you still haven't explained why normal-selectable websites like HN itself are bad for keyboard users.
- anthk 1y agoI use HN from Links daily, on a terminal. It's perfectly usable.
- TeMPOraL 1y agoThat's cheating. Terminal is in a sense the ultimate accessibility viewer, but few things work with existing terminal browsers I know of. Makes me wonder though, if anyone tried to take a SOTA screen reader/accessibility software, and use it to re-render the page purely from the "how the screen reader sees it" perspective (obviously with selectable text)?
- Ukv 1y agoWorse in what way? For keyboard use, I want text to be selectable, since I'll often use shift + arrow keys while reading.