Title: W3C &#8211; plugin code doesn&#039;t validate
Last modified: August 22, 2016

---

# W3C – plugin code doesn't validate

 *  [vickea](https://wordpress.org/support/users/vickea/)
 * (@vickea)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/w3c-plugin-code-doesnt-validate/)
 * I just installed this over the weekend and am impressed with the UI and control
   I have to do what I want. Thank you!
 * Just one grizzle – it would be great if you could validate your code for us.
 * CSS validator = [http://jigsaw.w3.org/css-validator/](http://jigsaw.w3.org/css-validator/)
   
   HTML validator = [http://validator.w3.org/](http://validator.w3.org/)
 * [https://wordpress.org/plugins/nextgen-gallery/](https://wordpress.org/plugins/nextgen-gallery/)

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

 *  [Benjamin](https://wordpress.org/support/users/benjaminowens/)
 * (@benjaminowens)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/w3c-plugin-code-doesnt-validate/#post-5881681)
 * Validation is always useful but at the same time there are multiple standards
   that make this difficult: NextGen users may have themes that are HTML4, XHTML,
   or HTML5. We’ve done our best to ensure that everything is as close to the W3
   standards as possible but we also have to be practical about providing gallery
   displays that look nice for everybody ‘out of the box’ and that can mean including
   non-standard browser specific attributes (like those with the -moz and -webkit
   prefix).
 * If proper W3 validity is a priority we do offer customization through custom 
   templates and the NGG_SKIP_LOAD_SCRIPTS constant could let you omit our CSS entirely
   in favor of your own choice.
 *  Thread Starter [vickea](https://wordpress.org/support/users/vickea/)
 * (@vickea)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/w3c-plugin-code-doesnt-validate/#post-5881749)
 * Thank you for the response Benjamin. I do understand what you’re saying and that
   catering for many users with varying situations is difficult at the best of times.
 * LOL! No…. I have no intention of writing my own for this.

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

The topic ‘W3C – plugin code doesn't validate’ is closed to new replies.

 * ![](https://ps.w.org/nextgen-gallery/assets/icon-256x256.png?rev=2083961)
 * [Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery](https://wordpress.org/plugins/nextgen-gallery/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/nextgen-gallery/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/nextgen-gallery/)
 * [Active Topics](https://wordpress.org/support/plugin/nextgen-gallery/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/nextgen-gallery/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/nextgen-gallery/reviews/)

## Tags

 * [code errors](https://wordpress.org/support/topic-tag/code-errors/)
 * [validate](https://wordpress.org/support/topic-tag/validate/)
 * [W3C](https://wordpress.org/support/topic-tag/w3c/)

 * 2 replies
 * 2 participants
 * Last reply from: [vickea](https://wordpress.org/support/users/vickea/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/w3c-plugin-code-doesnt-validate/#post-5881749)
 * Status: not a support question