Is this really not a mostly “solved” problem using assistive browser (or OS-level) settings/extensions that apply high-contrast/large type consistently across all sites/apps? Is it necessary to performatively sacrifice aesthetics to signal to everyone else you’re especially sensitive to these needs?
At what point is it enough? If they use high contrast, large fonts, and translations for every language—including Swahili’s default Kiunjuga dialect, but fail to include the Kimvita, Kiamu, Kingwana, Chimiini, Bajuni, AND Comorian dialects, will they be accosted for saying “f off” to everyone speaking Swahili outside of Zanzibar?
> Is this really not a mostly “solved” problem using assistive browser (or OS-level) ...
> ... performatively sacrifice aesthetics ...
One doesn't need to sacrifice aesthetics to make the design legible to an average user.
> At what point is it enough?
It depends on who your audience is. The more people you want to reach, the more you need to cater to everyone's needs. There are fundamental anti-patterns to avoid like writing with a dark font on a dark background.
I generally agree with the first point. As to the second, this is clearly designed for people who will have the technical know-how to facilitate custom CSS, browser extensions, reader modes, and other assistive technology.
Considering its branding is entirely centered on late night socialization, I feel low-contrast dark mode is precisely the aesthetic that fits its identity.
> people who will have the technical know-how to facilitate custom CSS
I think anyone with access to an LLM doesn't necessarily need the technical know-how. They can just ask as an extra step for a design check including text contrast.
> I feel low-contrast dark mode is precisely the aesthetic
Yeah, it is a very nice way of saying “f off” if you’re poor, whatever with your display (low res mobile) or eyesight.
Is this really not a mostly “solved” problem using assistive browser (or OS-level) settings/extensions that apply high-contrast/large type consistently across all sites/apps? Is it necessary to performatively sacrifice aesthetics to signal to everyone else you’re especially sensitive to these needs?
At what point is it enough? If they use high contrast, large fonts, and translations for every language—including Swahili’s default Kiunjuga dialect, but fail to include the Kimvita, Kiamu, Kingwana, Chimiini, Bajuni, AND Comorian dialects, will they be accosted for saying “f off” to everyone speaking Swahili outside of Zanzibar?
> Is this really not a mostly “solved” problem using assistive browser (or OS-level) ... > ... performatively sacrifice aesthetics ...
One doesn't need to sacrifice aesthetics to make the design legible to an average user.
> At what point is it enough?
It depends on who your audience is. The more people you want to reach, the more you need to cater to everyone's needs. There are fundamental anti-patterns to avoid like writing with a dark font on a dark background.
I generally agree with the first point. As to the second, this is clearly designed for people who will have the technical know-how to facilitate custom CSS, browser extensions, reader modes, and other assistive technology.
Considering its branding is entirely centered on late night socialization, I feel low-contrast dark mode is precisely the aesthetic that fits its identity.
> people who will have the technical know-how to facilitate custom CSS
I think anyone with access to an LLM doesn't necessarily need the technical know-how. They can just ask as an extra step for a design check including text contrast.
> I feel low-contrast dark mode is precisely the aesthetic
Agreed, and I like it too, if legible.