extra88

Absolutely not, unless you're using your hobby site to learn Drupal.

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.

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.

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 can see it, the Sign Up dialog has a Close button.

Sure it does. Open a modal <dialog> using <button command="show-modal">.

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.

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.

On iOS, the filled-in ones are all in colors set by the font but in macOS Safari they inherit the text `color`.

I have a personal site on a shared host that was recently suspended for excessive CPU use caused by incessant AI bot crawling. I don't have a problem with crawling per se, there's just so many and they're so bad at it.

Same. Also, proper names should be excluded entirely; the only "Advanced" one I got wrong was a place name.