Title: html5rules's Replies | WordPress.org --- # html5rules [ ](https://wordpress.org/support/users/html5rules/) * [Profile](https://wordpress.org/support/users/html5rules/) * [Topics Started](https://wordpress.org/support/users/html5rules/topics/) * [Replies Created](https://wordpress.org/support/users/html5rules/replies/) * [Reviews Written](https://wordpress.org/support/users/html5rules/reviews/) * [Topics Replied To](https://wordpress.org/support/users/html5rules/replied-to/) * [Engagements](https://wordpress.org/support/users/html5rules/engagements/) * [Favorites](https://wordpress.org/support/users/html5rules/favorites/) Search replies: ## Forum Replies Created Viewing 5 replies - 1 through 5 (of 5 total) * Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/) In reply to: [HTML5 Lang Attribute problems](https://wordpress.org/support/topic/html5-lang-attribute-problems/) * Thread Starter [html5rules](https://wordpress.org/support/users/html5rules/) * (@html5rules) * [14 years, 11 months ago](https://wordpress.org/support/topic/html5-lang-attribute-problems/#post-2135493) * Yes actually it was completely because of the W3 Total Cache plugin meaning there’s a bug or something there, more specifically it was the Minify feature causing this so I’m looking into it now. * Thanks for everyone’s help! * Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/) In reply to: [HTML5 Lang Attribute problems](https://wordpress.org/support/topic/html5-lang-attribute-problems/) * Thread Starter [html5rules](https://wordpress.org/support/users/html5rules/) * (@html5rules) * [14 years, 11 months ago](https://wordpress.org/support/topic/html5-lang-attribute-problems/#post-2135481) * Eric, it’s not the cache, I’ve tried that many times. If I were to remove the‘ lang’ attribute from the header and try the [http://achecker.ca/checker/](http://achecker.ca/checker/) validator again after flushing the cache you can see the change because then the ‘lang’ attribute isn’t there but the XML namespace still is. * > > * You can see that I don’t really want the XML namespace there because it’s HTML5 and like I said, when you look at the source from [http://achecker.ca/checker/](http://achecker.ca/checker/) you can see how it’s changed my code and on the W3C validator the source is just as it should be. * Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/) In reply to: [HTML5 Lang Attribute problems](https://wordpress.org/support/topic/html5-lang-attribute-problems/) * Thread Starter [html5rules](https://wordpress.org/support/users/html5rules/) * (@html5rules) * [14 years, 11 months ago](https://wordpress.org/support/topic/html5-lang-attribute-problems/#post-2135474) * Thanks, I’ve reported this as a bug and tagged that it needs more documentation. On the support files it actually says we don’t need to know about XML namespace which I think is a bit biased if you’re a developer… Nevertheless, we’ll see what they have to say. * Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/) In reply to: [HTML5 Lang Attribute problems](https://wordpress.org/support/topic/html5-lang-attribute-problems/) * Thread Starter [html5rules](https://wordpress.org/support/users/html5rules/) * (@html5rules) * [14 years, 11 months ago](https://wordpress.org/support/topic/html5-lang-attribute-problems/#post-2135420) * Thanks for your reply, I am aware of this. I removed the XML namespace from within my code that was giving me the WCAG error. However, I noticed that using the above WAI validator, the XML namespace appeared in the code, and when I validate the HTML using W3Cs service, the XML namespace isn’t there like it should be. I then took that code and pasted it in the WAI validator which came out valid. * I think what WordPress does is add the XML namespace to certain user agents, I don’t know which ones but that seems to be the root of the problem and perhaps something the official team should have a look at when make the transition to HTML5 in the future as the namespace is only used in XHTML so it shouldn’t be there in the first place. * Well that’s managed to sort out the problem in a kind of way but definitely something that should be looked in to. Viewing 5 replies - 1 through 5 (of 5 total)