Everyone thinking about 2-state vs. 3-state controls is automatically honoring the device's color scheme setting. The controls are an extra to let users choose to not use the device setting on a particular site.
Rather than each site making its own design for such a control, I wish browsers would make it a per-site setting users could use.
However, we should go a step further and provide a framework of UI elements that can be used consistently to create a uniform and accessible interface and they could even be pre-compiled into native controls for more efficient...hold on a gosh darn minute...
Honoring the dark/light color scheme set on the device might be a requirement in some cases (I haven't seen a straight answer about it for the EAA) but it is a good accessibility practice.
Including a toggle in an app/site UI so users can choose to not use their device setting is an extra.
I'll just note that the EAA is not the only accessibility law operating in the world.
Furthermore there might be accessibility use cases in which your site works better for some people in dark mode and better for other people in light mode, expecting that people will switch their device settings when they come on your site if you have this problem would not be nice.
I'm most familiar with the U.S., where it's not a requirement. Europe is the only place where I've heard there might be a requirement to honor a device's color scheme, I think it's very unlikely it exists anywhere else.
If a site honors the dark/light setting, I don't know what accessibility need would be served by being in the opposite mode for that one site. Having a toggle to meet preferences, yes, need, I don't know.
That's not what it's for, that's solved by showing the link when it's focused.
My guess is there was a desire to make Find-in-page automatically expand <details> elements and someone realized they could make it also work for custom disclosure widgets by giving the boolean attribute `hidden` an optional value.
That's fine, everything doesn't have to look the same everywhere. It does matter when there's functionality a site relies on but it's not available in one out more browser/OS combinations.
Yes, I agree that using the native OS UI is the right choice. Imagine if every web browser had a different file picker dialog, it would be a pain to have to reorient yourself just for that product.
However, I do lament the antiquated Windows 95 color picker. It seems less functional than others that I've used.
CSS now also has `reading-flow` to instruct the browser to change the reading order to match the visual order created by Flex or Grid. Unfortunately, not all browsers support it and it has some limitations.
All current browsers support anchor positioning including popover buttons being the implicit anchor. However, the anchor positioning polyfill does not support this, it requires an explicit anchor-name.
It is significant because cancer is much more detectable today than in 1956-80, both because of better tests and more testing being conducted. In that earlier era, if you knew you had cancer, it was likely because it was already bad.
I also expect that of the 39.2% of the population, the cancer is diagnosed much later in life than it was for the 91 movie crew members, I doubt 41% of the crew was over 50 in 1956.
Think about this for a minute. If three months of filming actually cause an increase in cancer rates the long-term residents of St. George (the downwinders), would have have devastatingly high cancer rates, right? The nearby residents were exposed to fallout from 100+ above ground nuclear tests and they were exposed for multiple decades, not just three months. This issue has actually has been studied and published in peer reviewed journals. A paper that studied the mortality of residents in that area concluded:
>...There was no excess risk of cancer mortality in southwestern Utah, for single or grouped sites, with the single exception of leukemia which showed statistically significant odds ratios of 1.45 based on 62 deaths at all ages, and 2.84 based on nine deaths at ages 0-14. The finding for childhood leukemia was based on different time periods and geographic comparisons from those of two earlier studies in which no such excess was found. Mortality from all cancer sites combined was significantly lower in southwestern Utah than in the remainder of the state, even after adjustment for the higher proportion of (lower risk) Mormons in southwestern Utah.
Trying to figure out when this strange idea about The Conqueror first appeared, I saw references to a 1980 article in People magazine. People magazine is not actually a peer reviewed journal.
Rather than each site making its own design for such a control, I wish browsers would make it a per-site setting users could use.
reply