- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Sat, 18 Feb 2023 19:36:22 +0000
- To: public-css-archive@w3.org
@Myndex This is a general comment, but also applies to many of your replies here: it is not constructive to these conversations to flood them with super long comments that are pages and pages of musings. This is not the right venue for elaborate colorful prose. Please spend the time to shorten your arguments to what is actionable and relevant to the topic at hand. If you are so inclined, you can put additional background information in `<details>` or link to it, so that those without the time to dive in (likely the majority of us) can just read what that is immediately relevant, and discussion can continue. I understand that when you really care about a topic, and have spent a considerable amount of your time studying it, it is often tempting to write lengthy messages dumping *all* of the info on other people and/or having some fun with what you're writing. In my experience, it actually has the opposite effect. Either it halts the conversation, because people cannot invest that kind of time, or it gets ignored, or it gets skimmed with readers picking up bits here and there. It's much better to condense it yourself, since you know which bits are important much better than other skimming. As for the colorful prose, there's a time and a place, and technical discussions in a WG is not it. For example, if I'm <del>reading</del><ins>skimming</ins> your message above correctly, it could have been condensed to: > Laws do not actually mandate WCAG 2.1 or any other specific specification. They instead mandate actual accessibility, and APCA is strictly superior in that. [source] The source could even be one of your articles, including all of the above, but this thread is not the place for posting full-blown articles. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7358#issuecomment-1435753254 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 18 February 2023 19:36:24 UTC