I didn't talk about low contrast at all, I specifically mentioned WCAG2.1 as it has set minimum contrast values for certain text sizes which should be readable.

I didn't talk about low contrast at all, I specifically mentioned WCAG2.1 as it has set minimum contrast values for certain text sizes which should be readable. I forced my previous place of employment to take WCAG AA-level as a minimum for every UI element and created a separate high contrast mode for our product which fulfilled the AAA-levels even though we weren't legally obligated nor had any customer ever asked for it. In the example (yellow on black) I mentioned has too much contrast and actually hinders readability for most people with a normal visual acuity as well as certain types of impairments. Designers are also the ones responsible _for_ all the accessibility features and standards set to help developers implement accessible solutions. If you're a software engineer who cares about contrast and studies different vision problems to figure out solutions for example, you're a designer in my book. This is why I also specifically separated aesthetic and usable design. The former is more akin to "art" as it aims to simply look nice and I don't personally consider it design as design is problem solving and bad design just creates more. I've always said that if a designer or web developer doesn't actively hinder accessibility, it's already a win in my book. It requires someone to make the decision to slap a #fafafa shaded text o top of a #ffffff background, semantic html and OS default colors go a long way if you don't know better.