I think this an uncharitable take – the parent comment is just proposing an improvement that would really help them given their colour-blindness (they also say they like the visualisation). Personally I find part of the reason for putting things on the internet is to allow other people to use them and obtain their feedback.

Every product has flaws which are outside of design scope. Pointing that is unnecessary. If I want feedback on my quick and dirty project, I want it on within the scope of design, not the missing features, bad accessibility etc.

Specially HN crowd is very susceptible to feeling for accessibility comment. Return of "think of poor kids in Africa".

> If I want feedback on my quick and dirty project, I want it on within the scope of design, not the missing features, bad accessibility etc.

This wasn't posted with that directive.

And if your "design is great" but your implementation sucks then maybe the design sucks too.

Maybe we should be building accessible UIs by default rather than treating an actual disability as a 'my workflow' problem.

This was not a harsh criticism. Accessibility on the web is important, especially if you want people to actually engage with what you have published.

Color blindness is nothing new, there are freely available color blind friendly color plates. Pointing out to the author that they could make a small tweak to make their work more accessible is good feedback and should continue to be given.

Sorry it came across that way, that was not my intent at all… it was meant as a simple suggestion for a potential low-hanging fruit improvement that would benefit people like me. Clearly you did not perceive it that way.

I totally understand being frustrated about people demanding workflow changes or huge accessibility features, but this is literally just a color swap that can be done with a touch of CSS it's really not a big deal.

Oh, calm down. Some people aren’t aware of this, someone pointed it out.