Skip to main content
edited body
Source Link
Wyck
  • 18k
  • 4
  • 46
  • 67

The simple reason is thethat WC3 CSS validation is not very important, you can do better things with your time that will effect your actual users. I'm not saying standards are not important , but with proper testing it is rather easy to ensure compatibility, but strict validation is not followed because many useful techniques are just not valid. For example google.com is not valid CSS ( or the vast majority ifof sites, small and large), do you think that it matters?

The simple reason is the WC3 CSS validation is not very important, you can do better things with your time that will effect your actual users. I'm not saying standards are not important , but with proper testing it is rather easy to ensure compatibility, but strict validation is not followed because many useful techniques are just not valid. For example google.com is not valid CSS ( or the vast majority if sites small and large), do you think that it matters?

The simple reason is that WC3 CSS validation is not very important, you can do better things with your time that will effect your actual users. I'm not saying standards are not important , but with proper testing it is rather easy to ensure compatibility, but strict validation is not followed because many useful techniques are just not valid. For example google.com is not valid CSS ( or the vast majority of sites, small and large), do you think that it matters?

Source Link
Wyck
  • 18k
  • 4
  • 46
  • 67

The simple reason is the WC3 CSS validation is not very important, you can do better things with your time that will effect your actual users. I'm not saying standards are not important , but with proper testing it is rather easy to ensure compatibility, but strict validation is not followed because many useful techniques are just not valid. For example google.com is not valid CSS ( or the vast majority if sites small and large), do you think that it matters?