Live data from Hacker News

Replying to comments about our web page design

research.exoticsilicon.com

151–160 of 211 posts

Re: Replying to comments about our web page design

#151
post #141

Per original link >>Arghhhh! Your pages give me a headache, and/or eyestrain. >Stop using the site immediately and consult a qualified ophthalmologist. Seriously, no static display on a modern and correctly adjusted VDU such as a computer monitor or phone screen should ever be inducing headaches or eyestrain in a healthy individual when properly used for reasonable time periods, and with sufficient breaks. If it is,…

I find it wildly ridiculous that we've more or less abandoned the practically simple idea of "the web is text, so just let people render the text how they want in their browsers. " Yet another reminder of the overblown nature of UX/UI in general. Given the current push for accessibility, seems like "make the text accessible" should be the goal above all else.

You can use a userstyle on the webpage. It works. It's quite straightforward actually.

Re: Replying to comments about our web page design

#152
post #134

Earlier quoted context omitted.

Playing Devil's advocate, if the themes are inaccessible, the user can always pick another one. Monochrome might provide the contrast ratio you want.

But why would they? It's much easier just to move on to another site.

Isn't that why HN sucks?

Re: Replying to comments about our web page design

#153
post #61

I think the one thing that strains the eyes a bit about the layout (besides people just using it as a metaphor for saying they don't like it) is that a lot of their themes use text shadow on all of the text, which makes it look slightly blurry, which in turn makes your eyes strain trying to focus on it.

They address this and tell you your browser is broken. But also that if you are using a non-broken browser and it's still hard to read for you then that's on purpose, they want it to be hard to read for you, because their content is for healthy people only.

they don't actually go into any detail how it's supposed to render, though. they refer to the standard but don't actually say what the browsers are supposedly doing wrong. It's not that the shadow being applied makes the text blurry somehow, it's that the shadow itself makes the text look like it's blurry, because it's very subtle. So, I don't buy it.

Re: Replying to comments about our web page design

#155

Reminds me of Lings Cars: https://www.lingscars.com/ Not a niche or hobbyist website, but a genuine car leasing company. Who's owner deliberately styled the site like this to act as a differentiator in a crowded market. It's certainly unique, I'll give them that.

> You can trust me… I am Ling! Hope you enjoying your visit to LINGsCARS.com

Sometimes marketing is so bad it’s good

Re: Replying to comments about our web page design

#156
post #141

Per original link >>Arghhhh! Your pages give me a headache, and/or eyestrain. >Stop using the site immediately and consult a qualified ophthalmologist. Seriously, no static display on a modern and correctly adjusted VDU such as a computer monitor or phone screen should ever be inducing headaches or eyestrain in a healthy individual when properly used for reasonable time periods, and with sufficient breaks. If it is,…

I find it wildly ridiculous that we've more or less abandoned the practically simple idea of "the web is text, so just let people render the text how they want in their browsers. " Yet another reminder of the overblown nature of UX/UI in general. Given the current push for accessibility, seems like "make the text accessible" should be the goal above all else.

Time to hop over to Gemini.

Re: Replying to comments about our web page design

#157
post #141

Earlier quoted context omitted.

I find it wildly ridiculous that we've more or less abandoned the practically simple idea of "the web is text, so just let people render the text how they want in their browsers. " Yet another reminder of the overblown nature of UX/UI in general. Given the current push for accessibility, seems like "make the text accessible" should be the goal above all else.

You can use a userstyle on the webpage. It works. It's quite straightforward actually.

They even offer ten themes and a chooser which is 9 themes more than 99% of websites.

Re: Replying to comments about our web page design

#158
post #85

Earlier quoted context omitted.

This is shockingly common but do these people resize their window for every site they visit? Or they keep the window narrow and then sites with side navigation need to put it somewhere else? Having a large window should be telling the site "you have this space, make the best of it". Maybe it would be nice to have a built-in CSS property for "desired reading text width" but I think most people can pick a number and it…

I'm one of those non-fullscreen browser (and most things in general, other than vim) window people. > Having a large window should be telling the site "you have this space, make the best of it" I 100% agree but I interpret this in reverse: if I made my browser window gigantic I expect you to use it. If I make my browser window small I expect you to responsively shrink. The reason this doesn't happen is that it's pret…

Well, you could do something smart with CSS columns, but nobody does that.

Re: Replying to comments about our web page design

#159

Earlier quoted context omitted.

So the answer is no, you don't know anyone who can't read the text. People post all kind of things online, especially hyperbole. As one of the other FAQ questions notes a lot of people also complain about their eyes bleeding, but this has never actually happened.

When users complain about headaches and eyestrain, it’s probably better to take them seriously.

Please rewrite your comments. I'm finding them quite offending.

Re: Replying to comments about our web page design

#160

does anyone know what's the string above the "NO CARRIER" written at the bottom of the page?

Kind of looks like an attempt at simulating the "modem dropped because someone picked up an extension phone while modem was connected" result. There was often a burst of random characters like that when the link went down due to "external causes".
Post reply on HN