mpetroff

5 ms·

1.
by mpetroff 1y ago
> My initial instinct is that finding 12 colors that are visually distinguishable for all users is likely impossible. Without going to lightness extremes, I agree that this likely isn't possible, at least when trying to accommodate
2.
by mpetroff 1y ago
While not completely identical, it looks very similar (I also only have strong protanomaly, not complete protanopia, so I wouldn't expect it to look identical). Color-vision deficiency simulations collapse colors along the confusion li
3.
by mpetroff 1y ago
Please don't use rainbow-type palettes, as they generally have poor accessibility for colorblind individuals. With my red deficiency, the middle two colors in this palette look virtually identical.
4.
by mpetroff 1y ago
I wrote a simple web-based night sky viewer a while ago [1], which renders the 750 brightest stars from coordinates in a data file (along with the moon). It uses D3.js to do fully client-side SVG-based rendering for interactive use, but it
5.
by mpetroff 1y ago
Figure 24 in Paul Tol's Notes is a reasonable thing to try: https://web.archive.org/web/20250201164619/https://personal.... However, to properly screen for color vision deficiencies requires calibra
6.
by mpetroff 2y ago
> Always fun to bump into Polies here :) Definitely! I wasn't expecting to see a mention of BICEP while reading HN from Pole, particularly not on something as arcane as its star camera.
7.
by mpetroff 2y ago
With images taken at night, you can run the images through Astrometry.net, which is a blind astrometric solver and will provide you with RA / Dec for most images, as long as you have at least a dozen or two stars visible. The code comp
8.
by mpetroff 2y ago
BICEP3 actually uses a >20 year old CCD camera with analog video output (BICEP Array uses newer cameras, with more modern sensors). Daytime star pointings are possible by using a low-pass filter to block visible light and take advantage
9.
by mpetroff 3y ago
> the default color palette is colorblind-friendly No, it very much isn't. The second and third colors, the orange and the green, look extremely similar to protanopes (red deficiency). Fortunately, there's a plan to fix this fo
10.
by mpetroff 3y ago
I implemented it as part of a GSoC project a decade ago, which was first included in the 0.91 release in 2015.
11.
by mpetroff 3y ago
You're correct, and the other responses saying otherwise are misinformed. Protanopes do not have long-wavelength cones and thus have reduced sensitivity to that end of the visible spectrum, i.e., red light appears dimmer to such indivi
12.
NeRF in the Dark: High Dynamic Range View Synthesis from Noisy Raw Images(arxiv.org)
2 points by mpetroff 5y ago|0 comments
13.
by mpetroff 5y ago
That's to be expected since the Coblis methods, particularly the v1/ColorMatrix version, are known to be very inaccurate. Unfortunately, it's usually the top search result for "colorblindness simulator," which leads
14.
by mpetroff 5y ago
It applied a linear transform to RGB values, like the current method, but the original matrices were the "colorjack.com matrices" [1] that have been floating around the internet for a while. They weren't derived scientificall
15.
by mpetroff 5y ago
For those interested, I've done some recent research on this topic [1], which tries to find cycles of colors that optimize both accessibility for color vision deficiencies, using simulations and minimum perceptual distances, and aesthe
16.
by mpetroff 5y ago
The simulation technique [1] currently used by the Firefox / Chrome dev tools is reasonable, so it's definitely much better than not checking for color vision deficiency accessibility at all. Ideally, color should only be used for
17.
by mpetroff 6y ago
I'd argue that the 147 named CSS colors are still too many (but definitely better than the ~16.8 million sRGB colors). Regardless, since hex codes are used in practice, they would still need to be dealt with.
18.
by mpetroff 6y ago
This would be true if the CSS color names were actually reasonable, but many of them are not. One would be better off using the results [1] of Heer & Stone (2012) [2] (or a similar analysis) to assign names to sRGB colors. You end up wi
19.
by mpetroff 6y ago
The WCAG also define the contrast ratio in terms of sRGB, which is not a perceptually-uniform color space. This makes the WCAG contrast ratios somewhat meaningless in terms of human visual perception. It's accessibility by edict, not s
20.
by mpetroff 6y ago
The issue isn't with referring to colors on a chart by name but with using a color name as the sole identifier. Referring to parts of a chart by color is fine, and provides additional information, as long as a line style or shape ident
21.
by mpetroff 6y ago
> The key would be to spend an absurd amount of time carefully cataloguing good colors – by hand – and training it to extrapolate from that information. It's a bit more nuanced than that. Not only do you need to catalog good colors
22.
by mpetroff 6y ago
I linked to the supplementary information [1] in my previous comment, but here's the link for the paper [2]. The method is implemented by the Colorspacious library [3] for Python, and the source for my color picker [4] contains both Ja
23.
by mpetroff 6y ago
Adding to this, the Chrome (83+) and Firefox (81+) developer tools both do a reasonable job at the simulation, using the method of Machado et al. (2009) [1]. Unfortunately, the linked to simulator, like many of the online simulators, does a
24.
by mpetroff 6y ago
It's possible, but the markup is very, very messy. I made a proof-of-concept by hand a couple months ago [1], but it would require quite a bit more work to automate it. It's probably best to just wait for browsers to implement CSS
25.
by mpetroff 6y ago
Bertin's Semiology of Graphics ?
26.
by mpetroff 6y ago
I have `hyphens: auto` set for the browser default comparison in the demo, which is roughly equivalent to inserting soft hyphens for Firefox (where I was doing most of the development), as well as for Chrome on Android and macOS. While brow
27.
by mpetroff 6y ago
This had me wondering about whether it was possible to use pre-calculated line breaks to implement improved text justification in current browsers. I was able to come up with a demo [1][2] that does so, although it falls back to default lin
28.
by mpetroff 6y ago
The problem is that CSS uses greedy line breaks. In theory, this should improve once browsers implement CSS Text Module Level 4, specifically the `pretty` value for the `text-wrap` property [1][2]. Until then, we're stuck with poor-qua
29.
by mpetroff 6y ago
Thanks for passing this along. I also commented on the relevant Chromium issue [1] (as well as the relevant Firefox issue [2]). It should be a simple fix, since the transformation matrices just need to be updated. Edit: I should have looked
30.
by mpetroff 6y ago
Unfortunately, this uses a horribly inaccurate algorithm that's been floating around the internet for more than a decade [1]. It seems that the Firefox dev tools do the same thing [2]. As far as I'm concerned, this is worse than n

More ›