&gt; I don&#x27;t get the point of those settings. You seem to prefer white-on-black text, but the &quot;Only with High Contrast themes&quot; override means that it will almost never apply.<p>The idea of defaults is to be default. I don&#x27;t mind sites specifying the use of particular colours, and it&#x27;s useful e.g. for syntax highlighting, for text above background images, for transparent images assuming a particular background colour (e.g. pre-rendered LaTeX images, like those on Wikipedia), etc.<p>The problem is setting either the foreground or the background, but not both.<p>&gt; I tried setting this in my Firefox and visited a bunch of sites. None of them showed me white text on black background, because almost every site sets both background and foreground color styles, which override the preference setting. In fact the only site that was affected was the BMFW.<p>If only that were true. Many sites set either just the foreground colour, assuming the background will be white; or just the background, assuming the foreground will be black. I&#x27;ve emailed many sites about this over the years, ended up opening countless others in a separate browser with different settings, and just rage-quitted many more.<p>Last week I emailed ticketmaster.es about the black-on-black text in their registration form (amongst many other issues; their service is terrible, I recommend avoiding them if possible)<p>This is also the reason I stopped using Yahoo Mail back in 2007 when they switched off access to their old Web UI (with no option to use IMAP or POP without paying) <a href="http:&#x2F;&#x2F;2.bp.blogspot.com&#x2F;_6BhjMzysLTs&#x2F;Rg1mh0pLjMI&#x2F;AAAAAAAAAAM&#x2F;Ty6EJEILx04&#x2F;s1600&#x2F;crapoo.png" rel="nofollow">http:&#x2F;&#x2F;2.bp.blogspot.com&#x2F;_6BhjMzysLTs&#x2F;Rg1mh0pLjMI&#x2F;AAAAAAAAAA...</a><p>I&#x27;ve even tried fixing pages with custom Javascript <a href="http:&#x2F;&#x2F;chriswarbo.net&#x2F;blog&#x2F;2015-10-01-web_colours.html" rel="nofollow">http:&#x2F;&#x2F;chriswarbo.net&#x2F;blog&#x2F;2015-10-01-web_colours.html</a> with mixed success. I also have a key bound to `xcalib -invert -alter` so I can quickly invert my screen colours.<p>The MFW concludes with the following:<p>&gt; What I&#x27;m saying is that all the problems we have with websites are ones we create ourselves. Websites aren&#x27;t broken by default, they are functional, high-performing, and accessible. You break them. You son-of-a-bitch.<p>In their attempts to be &quot;better&quot;, BMFW&#x27;s authors broke it. Sure, it can be argued that light-on-dark default colours are an edge case; that the authors say they were &quot;going to&quot; add a background colour but didn&#x27;t; etc. and those are all perfectly reasonable arguments. But those are exactly the arguments MFW and BMFW are <i>disagreeing with</i>, only with &quot;light-on-dark default colours&quot; instead of &quot;disabled Javascript&quot; or &quot;out-of-date Android browser&quot; or &quot;retina display&quot;, etc.; or with &quot;background colour&quot; instead of &quot;server-side rendering&quot;, &quot;error handler&quot;, &quot;CDN&quot;, etc.