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 (firstname.lastname@example.org), File a bug, or send an e-mail directly to email@example.com.
Issues should get a response 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.