Add dark mode to 3.4 docs

[mattgarrish]

This matches the changes in #2672 for the 3.4 docs.

It also adds the css-inline code to the accessibility techniques. The rest already had it.

[iherman]

I approve it (of course), but we may want to reach out to the WG before we do such a change. It pretty much changes the outlook of the documents after all...

@wareid @shiestyle ?

[mattgarrish]

It pretty much changes the outlook of the documents after all...

Sure, but this is W3C standard for dark mode, not something we've come up with (modulo the few tweaks).

No harm in checking, though. I was going to wait until you were ready to merge the other PR, anyway. It looks like it only captures the authoring spec right now, but we should probably republish everything under 3.3 with this change for consistency.

[iherman]

It pretty much changes the outlook of the documents after all...

Sure, but this is W3C standard for dark mode, not something we've come up with (modulo the few tweaks).

That is correct: it is standard if we decide to adopt dark mode. But dark mode is not required by the W3C publication rules. Hence, it is better to check with the WG, it should not be solely the editors' decision.

No harm in checking, though. I was going to wait until you were ready to merge the other PR, anyway.

You mean #2672? I think that one should be closed, and this PR takes it over. I do not think we should change 3.3 at this point. Let dark mode be the first feature that differentiate 3.4 from 3.3!

It looks like it only captures the authoring spec right now, but we should probably republish everything under 3.3 with this change for consistency.

You mean the other notes? Yes, of course.

---

I presume we plan to move (copy) all notes from the 3.3 subtree to the 3.4 one, right? So the dark mode versions of the notes would be, sort of, 3.4 (even if they do not really change).

[mattgarrish]

it is standard if we decide to adopt dark mode

I don't think the decision is up to us. The announcement said this was coming to all specs this year or next, but we should add the meta tag to help with the transition: https://lists.w3.org/Archives/Public/spec-prod/2024AprJun/0000.html

No harm in letting the group know, but we can't really stop the change from coming.

I presume we plan to move (copy) all notes from the 3.3 subtree to the 3.4 one, right?

Oh, I was thinking we'd just do a final republish of everything in 3.3 and then only bring the notes forward to the 3.4 directory as we actually need to work on them.

But maybe it's better to copy them all forward in case there are other changes like this that need a full refresh of the notes. I'll defer to you on which approach you think is better.