Revisit lang attribute #1879
Comments
|
What about adding an HTML comment encouraging them to make the change? That seems more consistent with the current tips (like changing the GA tracking code) |
Yeah I think that would work fine too. |
|
As far as real-world sites that have this issue, a couple of the more well-known ones I’ve noticed are https://www.bookofthemonth.com/ and https://www.thehartford.com/ but there are many more. |
roblarsen
changed the title
|
Discussion that created the current format: #1542 I'm against "change_me" or "change." All that will do is spread a meaningless language attribute. That works for no one. If we were going to do that, we might as well go back to An empty lang attribute is what you're supposed to use if the language is undetermined. |
|
Closing because I don't think there's a better answer. I've got some thoughts on how we might do some things going forward that might help this (and some other things) but... nothing for now. |
and others
I maintain the W3C HTML Checker and in looking at statistics logged by it I notice there are a significant number of sites built from HTML5 Boilerplate that have
<html class="no-js" lang="">. That is, they have the empty string as the value for thelangattribute, even when the document is clearly in English or another identifiable language.I think this problem could maybe be prevented if HTML5 Boilerplate instead used something like
<html class="no-js" lang="CHANGE_ME">rather than<html class="no-js" lang="">.The text was updated successfully, but these errors were encountered: