Are you interested in reviewing HTML5 for errors?
Jump in! All feedback is welcome, from anyone.
- Open the specification: either the one-page version, or the multipage version or the PDF copy (A4, Letter)
- Start reading! See below for ideas of what to look for.
- If you find a problem, either send an e-mail to the list ([email protected]), File a bug, or send an e-mail directly to [email protected]
If everything goes according to plan, all issues will get a response from the editor before October. You can track how many issues remain to be responded to on our graph.
What to look for
You don't really need any experience to find the simplest class of problems: things that are confusing! If you don't understand something, then that's a problem. Not all the introduction sections and examples are yet written, but if there is a section with an introduction section that isn't clear, then you've found an issue.
Something else that would now be good to search for is typos, spelling errors, grammar errors, and the like.
If you have a specific need as a Web designer, then try to see if the need is met. If it isn't, and you haven't discussed this need before, then send an e-mail to the list. (So for example, if you want HTML to support date picker widgets, you'd look in the spec to see if it was covered. As it turns out, that one is!)
If you have some specific expertise that lets you review a particular part of the spec for correctness, then that's another thing to look for. For example if you know about graphics, then reviewing the 2D Canvas API section would be a good use of your resources.
You are encouraged to join our IRC channel #whatwg on Freenode to stay in touch with what other people are doing.
Once you've reviewed a section, add a note here to let others know that you've looked at it. That way people can coordinate their efforts and we can make better use of our resources.