The summary page provides a summary of the tests performed, together with links to results pages for each page on your website that was found to contain problems. Note that pages that do not have any problems are not listed unless you use the show success option.
Each results page provides a list of problems found for the particular web page or style sheet that was tested.
The summary page is stored in a file called 'TotalValidator.html' and the results pages are stored with this in a sub-folder called 'Results'. These are normally overwritten each time you run the tool so that you don't run out of disk space.
The typical location of these files depending on your operating system is as follows:
- Windows 2000/XP: My Documents\TotalValidatorTool
- Windows Vista/7/8: <drive>:\Users\<your login name>\Documents\TotalValidatorTool
- Linux: <user_home>/Documents/totalvalidatortool/, or the folder you installed the tool into
- OS X: <user_home>/Documents/TotalvalidatorTool/
A the top of the summary page is the name of, and a link to, the starting page you supplied. There then appears a summary of the report - including the version of the tool used, the options selected, and number of problems found:
Under this is a list of the pages tested together with a summary of the problems for each:
The list of problems is a link to the detailed results for that page as described below.
At the top of the page is the name of, and a link to, the page that was tested. There then appears a summary of the report, followed by a representation of the web page tested:
Normally the representation of the web page shows each of the tags within it on a separate line, with indentation showing how the tags are nested within each other. This should make it easy to read the results even with the most poorly formatted source web page or where the layout style varies across the site. It is particularly useful when the pages are generated by a computer program, as these tend to generate the most irregular web page source.
Similarly, CSS stylesheets and statements within <style> tags are reformatted and reorganised to allow errors to be easily reported on.
To simplify the report further you can also use the short report option to just display lines with problems on.
The line numbers on the left refer to lines in the original source so you can quickly get to and amend the faulty tag or CSS statements in the original web page source.
Line numbers marked as '0' refer to tags added by the tool. These are optional tags that are implicit in the standards, but are sometimes displayed in the results as somewhere to attach errors/warnings to relating to the subsequent page.
The image below shows an example of how an error is displayed. These are highlighted and begin with an 'E' followed by a unique number for the error, then some explanatory text. Probable errors begin with a 'P' and Warnings begin with a 'W'. In most cases the number is a link to further information about the problem at the bottom of the page. There are also up and down arrows next to the problem to allow you to quickly navigate to other problems on the page.
If there is more than one error associated with a tag then these are listed one after another on separate lines before the tag itself:
Note that column numbers referring to the original source are not displayed. This is deliberate as many problems apply to the whole tag. Also we've found that having column numbers often detracts from understanding the problem. Instead where possible the item in question will be highlighted in red as shown above.
Potential spelling mistakes are dealt with as shown in the image below. The word that is not recognised by the dictionary is highlighted and followed by a list of suggested replacements:
If the spelling validator highlights a word which isn't a mistake, you can always create your own set of additional words to use.
Note that the line number given refers to the first line of the content containing the spelling mistake. So if the content spans multiple lines it may not be match the line with the mistake on. But it should still be simple to find the mistake in the original page.