Title: W3C Validation errors
Last modified: November 4, 2023

---

# W3C Validation errors

 *  Resolved [septero](https://wordpress.org/support/users/septero/)
 * (@septero)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/w3c-validation-errors-17/)
 * Hi,
 * I’m using Stackable plugin with Blocksy theme. I am in the process of removing
   errors found with W3C validator.
 * I still have to fix some CSS parse errors and incorrect divs in the layout. The
   bugs that remain are related to Stackable classes.
 * Example page with errors: [https://validator.w3.org/nu/?showsource=yes&showoutline=yes&doc=https%3A%2F%2Fseptero.pl%2F#l14c109](https://validator.w3.org/nu/?showsource=yes&showoutline=yes&doc=https%3A%2F%2Fseptero.pl%2F#l14c109)
 * How to get rid of above-mentioned errors?
 * Thank you for support.
 * With best regards

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Benjamin Intal](https://wordpress.org/support/users/bfintal/)
 * (@bfintal)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/w3c-validation-errors-17/#post-17179972)
 * Hello, thanks for posting!
   Regarding the CSS parse errors on the optimized CSS,
   they seem to be false positives because they look to be valid CSS (at least for
   the CSS which are outputted by Stackable) – I’m not sure about why they are pointed
   as errors though, but I saw that validation sometimes reports these things, maybe
   because of CSS optimizations.Thanks for the report about the incorrect divs, 
   we’ll add this to our list of todos that we will address in a future update. 
   The good thing is that these validation errors don’t have any immediate, critical
   impact on the website’s functionality or appearance.
 * Thanks!
 *  Thread Starter [septero](https://wordpress.org/support/users/septero/)
 * (@septero)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/w3c-validation-errors-17/#post-17181269)
 * Hi [@bfintal](https://wordpress.org/support/users/bfintal/),
 * Thanks for answer and clarification that CSS parse errors have no impact on the
   functionality or appearance of the website. I’m waiting for the div bug to be
   fixed. I mark this topic as solved.
 * Best regards

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘W3C Validation errors’ is closed to new replies.

 * ![](https://ps.w.org/stackable-ultimate-gutenberg-blocks/assets/icon-256x256.
   png?rev=2749547)
 * [Stackable - Page Builder Gutenberg Blocks](https://wordpress.org/plugins/stackable-ultimate-gutenberg-blocks/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/stackable-ultimate-gutenberg-blocks/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/stackable-ultimate-gutenberg-blocks/)
 * [Active Topics](https://wordpress.org/support/plugin/stackable-ultimate-gutenberg-blocks/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/stackable-ultimate-gutenberg-blocks/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/stackable-ultimate-gutenberg-blocks/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [septero](https://wordpress.org/support/users/septero/)
 * Last activity: [2 years, 6 months ago](https://wordpress.org/support/topic/w3c-validation-errors-17/#post-17181269)
 * Status: resolved