There is no objectively "wrong" CSS, and four reasons support this claim. First, if CSS works without practical disadvantages, there's no reason to change it, especially given the web platform's strong backwards-compatibility guarantees. Second, any consequences of suboptimal CSS fall on the developer or organization, making it their call to address. Third, CSS is easy to refactor when a better approach is needed, so no mistake is truly grave. Fourth, when CSS creates real barriers for users, that's arguably a platform-level responsibility rather than a developer failure. CSS advice should always be understood as context-dependent guidance, not universal law — and distinguishing advice from dogma is key to evaluating criticism of your code.