The aim is to show that providing a semantically rich HTML gives much more value to your code: using a semantically rich HTML code allows a better use of CSS, makes your HTML intelligible to a wider range of user agents (especially search engines bots).
Have you been using this tool to your advantage? ;)
Works just fine for me, jtara. What error message are you getting? Bear in mind that the tool expects a full URI to a resource, not just the domain name, ie. http://www.example.com/ rather than www.example.com.
The tool itself is a simple and interesting little utility to see if you can extract the correct meaning from the way the page uses markup. It can be useful in pointing out potentially confusing associations. A good example which I tried showed that the contents of a sidebar (using
h4 elements for each header) were seen as being appended on the final node created by the article links in the main content area (which were marked up with h3 elements). The fix would be to have a h2 or h3 element introducing the sidebar sub-headings.
Using org.apache.xerces.parsers.SAXParser Exception net.sf.saxon.trans.DynamicError: org.xml.sax.SAXParseException: Content is not allowed in prolog. org.xml.sax.SAXParseException: Content is not allowed in prolog.