Live data from Hacker News

Pixels and Accessibility

joshwcomeau.com

1–10 of 21 posts

Re: Pixels and Accessibility

#2
> In theory, 1px is equal to a single dot in a computer monitor or phone screen.

Even in theory, this has never been true AFAIK. Pixels (px) are relative to the properties of the viewing device, the user's OS and browser settings, etc. The author appears to be confusing "physical pixel" with "logical pixel".

Re: Pixels and Accessibility

#3
As someone with poor vision, I don't want "make everything bigger", and I don't want "make all the text bigger", I want "make the small text bigger".

(Or, ideally, "make small text and fiddly diagrams bigger, but leave most images alone", but let's walk before we try to run.)

So maybe "rems for body text, px for headings" is the way to go.

Re: Pixels and Accessibility

#4
This is one of the long form frontend blogs that I greatly enjoy, and learn sometime new every time. So, I am excited anytime a new one comes out. I hope with Josh releasing his own course[1], that the blog continues to provide excellent resources for "free".

[1](https://css-for-js.dev/)

Re: Pixels and Accessibility

#5
> 1px is equal to a single dot in a computer monitor or phone screen.

Far from always!

“For screen displays, it traditionally represents one device pixel (dot). However, for printers and high-resolution screens, one CSS pixel implies multiple device pixels. 1px = 1/96th of 1in.”

https://developer.mozilla.org/en-US/docs/Web/CSS/length

Re: Pixels and Accessibility

#6
It's quite ironic how the font settings page for Chrome doesn't do well with different font sizes itself. They got the sidebar backwards and appeared to have used px for the font-size but em for the padding.

Re: Pixels and Accessibility

#7
post #2

> In theory, 1px is equal to a single dot in a computer monitor or phone screen. Even in theory, this has never been true AFAIK. Pixels (px) are relative to the properties of the viewing device, the user's OS and browser settings, etc. The author appears to be confusing "physical pixel" with "logical pixel".

Try reading more. He’s not confusing anything, he specifically calls out how resolution changes and such effect things.

Re: Pixels and Accessibility

#8
post #3

As someone with poor vision, I don't want "make everything bigger", and I don't want "make all the text bigger", I want "make the small text bigger". (Or, ideally, "make small text and fiddly diagrams bigger, but leave most images alone", but let's walk before we try to run.) So maybe "rems for body text, px for headings" is the way to go.

Browsers typically support a minimum font size setting.

Re: Pixels and Accessibility

#9
post #7
post #2

> In theory, 1px is equal to a single dot in a computer monitor or phone screen. Even in theory, this has never been true AFAIK. Pixels (px) are relative to the properties of the viewing device, the user's OS and browser settings, etc. The author appears to be confusing "physical pixel" with "logical pixel".

Try reading more. He’s not confusing anything, he specifically calls out how resolution changes and such effect things.

I read TFA and am suggesting that this could use a correction. To be charitable, this is a misleading oversimplification and doesn’t serve readers.

Re: Pixels and Accessibility

#10
post #2

> In theory, 1px is equal to a single dot in a computer monitor or phone screen. Even in theory, this has never been true AFAIK. Pixels (px) are relative to the properties of the viewing device, the user's OS and browser settings, etc. The author appears to be confusing "physical pixel" with "logical pixel".

There is a big blue information box in the article that explains this. It's called "Hardware vs. software pixels".
Post reply on HN