有效性错误不是主要问题，是吗？
我刚刚通过 w3c 的验证器运行我的网站，结果出现 144 个错误和 122 个警告。我将其发送给我的网络开发人员，他们负责设计、开发和维护该网站，他们说没有什么大问题，而我的一位朋友说，这实际上对 SEO 和性能等方面来说是一个巨大的问题。你们觉得怎么样？
I just ran my website through the validator at w3c and it came up with 144 errors and 122 warnings. I sent it to my web developers, who designed, developed and take care of the site and they said that there are no major problems, while one of my friends said that it is in fact a huge problem to things like SEO and performance. What do you guys think?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
这有两个方面：
由于浏览器错误和时间限制，通常不可能构建 100% 标准兼容的页面。当然，可能有一个解决方案，但是您是否愿意花费整整一周的开发时间，只是为了在所有浏览器正确显示时消除几个验证器警告。
越来越多的程序试图了解您的网站。因此，将标准违规行为控制在最低限度也很重要。
在生活中，善与恶之间需要保持平衡:-) 因此，如果您可以向网页设计师支付几千美元以使您的网站 100% 符合标准，为什么不呢？
也就是说，它不应该包含那么多错误。我的猜测是 2-3 个错误出现了 144 次。因此，为了平衡您的需求和网店的需求，请找到最重要的需求并进行修复。
There are two sides to this:
It's often impossible to build pages which are 100% standard compliant because of browser bugs and time constraints. Sure, there might be a solution, but are you willing to pay a full week worth of development time just to get rid of a couple of validator warnings when all browsers display it correctly.
There are more and more programs out there who try to make sense of your site. So keeping the standard violations to a minimum is important, too.
As always in life, there needs to be a balance between good and evil :-) So if you can pay a couple of thousand dollars to your web designers to make your site 100% standards compliant, why not?
That said, it should not contain that many errors. My guess is that it's 2-3 errors which appear 144 times. So to balance your needs and those of your web shop, find the most important ones and have them fixed.
老实说，任何构建网页的人如果不关心正确性或最佳实践，更不用说有效性标志，那么工作就很糟糕。我一眼就同意你朋友的观点。
To be brutally honest, anyone building web pages that is not concerned with correctness or best practice, let alone a badge of validity, is doing poor work. I'd be inclined to agree with your friend at passing glance.
标准确实很重要，是的，您的网站应该尽可能合规，这样它就可以在任何设备/浏览器/未来的互联网上一样有效，而无需您支付更多的费用进行返工。
提示宗教辩论
Standards are really important, and yes your site should be as compliant as it can be, so that it can be as effective on any device / browser / future interweb thingy without you having to pay a load more $$ for a rework.
cue religious debate
有效性错误并不是问题，除非您尚未手动测试过的软件（浏览器、屏幕阅读器等）出现页面中断，或者在验证时出现需要三个小时才能修复的问题如果它没有隐藏在另外一百五十个错误中，本可以在一分钟内帮助您解决它。
Validity errors are not problems right up until the point the the page breaks in a piece of software (browser, screen readers, whatever) that you haven't tested in manually or until you have a problem that takes you three hours to fix when validation would have helped you solve it in one minute if it wasn't hidden among another hundred and fifty errors.
您对辅助功能有任何警告吗？ (http://www.w3.org/WAI/gettingstarted/Overview.html) 在许多国家，不解决可访问性问题的网页是不可接受的？
Are any of your warnings about accessibility? (http://www.w3.org/WAI/gettingstarted/Overview.html ) In many countries it is unacceptable to have web pages that do not address accessibility?
您需要寻找新的网络开发人员。这里的错误由 a) 错误或 b) Web 开发人员应该知道的事情组成。此外，他们不承担责任也是不专业的。到目前为止，所有答案都没有讨论实际问题。这里只是一些：
启用 NET 的开始标记需要 SHORTTAG YES - 这只是偷懒。关闭标签。 “每个人”都知道这一点。
此处文档类型不允许使用元素“ABCD” - 这不是理解 DOCTYPES。事实上，这里有很多与 DOCTYPE 相关的问题，这可能会导致浏览器出现意外的结果。
未打开的元素“TD”的结束标记 - 这是一个错误，并且非常损坏。有些浏览器会“修复”这个问题。有些不会。
You need to find new web developers. The errors here are composed of a) mistakes or b) things a web developer should know. Additionally, the fact that they have not taken responsibility is unprofessional. None of the answers thus far have discussed the actual problems. Here are just a few:
NET-enabling start-tag requires SHORTTAG YES - This is just being lazy. Close the tag. "Everyone" knows this.
document type does not allow element "ABCD" here - This is not understanding DOCTYPES. In fact, there are a lot of problems here related to DOCTYPE, and this can lead to unexpected results with browsers.
end tag for element "TD" which is not open - This is a mistake and is very broken. Some browsers will "fix" this. Some won't.