W3C 合规性测试：方法论
我们将重新设计一个大型 Web 服务，该服务具有大约 25 个独特的页面模板，可提供数千个页面。主要要求之一是 w3c 合规性（html 4.01 过渡/WCAG1.0）。有无限个数。由于代码很破旧，因此出现了验证错误。
1）由于它是一个旧的应用程序，从头开始不是一个选择，因为它会破坏网站。
2）此外，网站的某些部分（不太重要的部分）没有变化。您认为我们可以在一开始就验证这一点吗？
3) 验证每个页面将花费太长时间，我们可能没有时间。
所以我的问题是，您认为进行验证的最佳方法是什么？您将如何估计这种情况？
提前致谢！
瓦桑斯
We are going to redesign a large web service which has around 25 unique page templates delivering thousands of pages. One of the major requirements is w3c compliance (html 4.01 transitional / WCAG1.0). There are an infinite no. of validation errors as the code is shabby.
1) Since its an old application, starting from scratch is not an option as it will break the site.
2) Also, there are some parts (less important parts) of the site where there are no changes. Do you think we can validate this in the beginning.
3) Validating each and every page is going take too long and we may not have the time.
So my question is, What according to you is the best methodology to go about validation? How will you estimate for such a scenario.
Thanks in advance!
Vasanth
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
决策制定和优先级
当目标是在大型站点上进行验证时，最好从优先级任务开始。
这将给您一些时间来找出网站中哪些页面最常访问，您的真实用户使用什么，并考虑到其中哪些页面使用最多，并且首先使其有效将受益。
在我看来，验证是一项要求，但在商业环境中务实也具有很高的价值。
您知道您最初想花多少时间来验证您的网站代码吗？考虑到您分配的时间，知道从哪些部分开始将使您真正领先。
估算
如果您的团队不习惯编写有效的代码并且从未执行过验证任务，那么估算对他们来说将会很困难。不过，您可以根据复杂度点进行估算，这将为您提供更多的可视性和透明度企业机构。
临时
习惯于随时纠正错误。让团队中的每个开发人员每次处理他们所处理的每个页面时修复 2 个错误。
随着时间的推移，您最终会得到一个经过良好验证的网站，并结合初始改造，这是保持页面有效、让开发人员掌握验证并在未来节省大量时间的好方法。
Decision making and prioritising
When aiming for validation across a large site it can be good to start off with a prioritisation task.
This will give you some time to find out which pages in the site are most often accessed, what do your real users use, and given that, which of those are used the most and would benefit from being made valid first.
Validation is a requirement to my mind, however being pragmatic in a business context is also of high value.
Do you know how much time you want to spend initially working on validating your website code? and given the time you've allocated, knowing which parts to start with will give you a real head start.
Estimating
If your team arn't used to writing valid code and have never undertaken a validation task, estimating is going to be hard for them. You can however estimate in terms of complexity points which will then give you more visibility and transparency to offer the business bods.
Ad-Hoc
Get used to correcting errors as you go. Have each developer on your team fix up 2 errors for each page they work on, each time they work on them.
Over time, you'll end up with a nicely validating website and combined with an initial revamp, this is a great way to keep pages valid, keep developers on top of validation and saves a lot of time in the future.
如果有很多页面，一个好的开始是设置一些内容，以便您可以抓取自己的网站并通过“单击操作”验证所有页面。如何做到这一点取决于您的环境，但实际上并不难。
当您有很多错误时，一个好的第一步可能是创建一个比 html 4.01 过渡更“宽松”的模式，它允许您从一些已知的错误开始，以掌握您必须更改的内容。当站点使用这种额外的草率模式进行验证时，是时候将其严格限制为 html 4.01 过渡（也许一直限制到 4.01 严格）。
最重要的部分：努力不仅要有验证标记，还要有相关标记，这样您网站的标题结构才合理，
只是用于强调，而不是出于其他原因将文本显示为斜体等，表格用于实际的表格数据等。重新估计：我会估计一三天才能让“单击验证事情”进行下去，并且之前我得到的输出是，我拒绝对整个修复过程做出任何估计（除非我从一开始就很好地掌握了模板中的实际问题）。
If there are many pages, a good start is to set up stuff so you can crawl your own site and validate all pages by a "single click operation". How to do it depends on your environment, but it is actually not that hard.
When you have a lot of errors, a good first step might be to create an even more "relaxed" schema than html 4.01 transitional, which allows some of your known errors to begin with, to get a grip on what you have to change. When the site validates with this extra sloppy schema, it is time to strict it up to html 4.01 transitional (and maybe all the way to 4.01 strict).
And the most important part: Try hard to not only have validating markup, but also relevant markup, so the heading structure of your site is sane,
<em>is only used for emphasis and not for other reasons to have the text in italics, etc, tables are used for actual tabular data, etc.Re estimation: I would estimate a day or three to get the "single click validation thingy" going, and before I got the output from that I would refuse to give any estimate at all about the whole fixing (unless I happened to have a really good grasp of what the actual problems are in the templates from the start).
那么我不认为你追求的是“方法论”。只安装 Firefox Validator add-on 并在浏览您的网站时启用它怎么样？网站从最常用的页面开始随时发现错误？
Then I don't think you're after a ‘methodology’. How about just installing the Firefox Validator add-on and having it enabled when you browse around your site to pick up errors as you go, starting in the most commonly-used pages?