Read Me Page Checks Accessibility, HTML, CSS, Links, and Spelling

Documentation > FAQ

Common issues encountered while using Total Validator are described below. For licensing issues, please see the Licence FAQ

Total Validator doesn't start or displays an error message

Please ensure that you have the latest version of Total Validator installed.

Error messages are normally self-explanatory and should help you to correct the problem yourself. But if there is a message doesn't make sense, complete our Feedback Form to report the problem.

A 'Could not connect ...' message appears

This message appears when Total Validator cannot make a network connection to the starting web page, so ensure that you can connect using the exact same URL in your browser first.

If you can see the page with your browser, it may be that there are one or more proxy servers between you and the page, or the page requires authentication to view it. Unfortunately, if you are using the Basic version there are no options available to allow you to authenticate yourself or to specify a proxy server, but you can still use one of our browser extensions to check the source code of the page. Total Validator Pro users should look to the Proxy Server and Network options for further information. Test users can specify proxy settings using the Options menu.

If you are using the Test or Pro versions and you still can't get through a proxy server, then complete our Feedback Form to report your issue.

macOS security warnings

When you run Total Validator for the first time, a message may appear saying that it has been downloaded from the Internet. This is perfectly normal, just click the 'Open' button to continue.

If you have configured macOS to only run apps downloaded from the App Store, you will have to temporarily allow apps downloaded from elsewhere:

  1. In System Preferences: Select Security & Privacy
  2. If required, click the lock icon that reads 'Click the lock to make changes.'
  3. On the 'General' tab, change 'Allow apps downloaded from:' to 'App Store and identified developers''
  4. Start Total Validator, ignoring any Internet warning as described above
  5. You may then reset your security settings back to 'App Store'

Total Validator stores its results in your 'Documents' folder. So when running for the first time a message may also appear asking for permission to write there. If you do not allow this the tests will not be completed and an error may appear. With the Pro version, if you wish to, you can specify a different folder for the results.

Windows security warnings

When you try to install Total Validator you may see a message from Microsoft's SmartScreen saying that it is an unrecognised app, displaying a "Don't run" button. If you have downloaded Total Validator from our website this is most likely a false positive. If you click the "More info" link a "Run anyway" button will appear, which will allow you to install Total Validator.

If you used Microsoft Edge to download Total Validator, you may see additional SmartScreen messages before the above, requiring you to "Keep" and/or "Keep Anyway" to continue.

With the .exe installer, you may also see a warning message from "User Account Control" saying that it is from an "Unknown publisher". This is because we currently do not sign our Windows installer. One of the main aspects of signing, is to verify that the original program has not been altered. Instead, you can achieve the same thing by verifying the checksum of the download ...

If you are at all unsure, then please verify the checksum of the download against the appropriate one on our download pages. If the checksums match, then you can be sure that you are running the original, complete, and unmodified program provided by us.

Total Validator is quarantined by Symantec/Norton

When certain Symantec/Norton products detect a program they have never seen, this is automatically marked as WS.Reputation.1 and placed into quarantine, even though no virus has been detected. The first thing to note is that you already have a copy of Total Validator, and you do not need to download it again. Please consult your Symantec/Norton documentation to restore this file from quarantine and exclude it from further scans.

We believe that each time a user takes the program out of quarantine and excludes it from further scans, the reputation of the program increases until WS.Reputation.1 is finally removed. However, Symantec's system resets with each new version of Total Validator, and so you may continue to see this message with each update you download.

If you are at all unsure, then please verify the checksum of the download against the appropriate one on our download pages. If the checksums match, then you can be sure that you are running the original, complete, and unmodified program provided by us.

Note: If you obtained Total Validator from anywhere other than our website, or your program highlights a different issue other than 'WS.Reputation.1' or 'Reputation', please let us know before using it.

Browser doesn't display the results

When the test is finished your browser should display the results. If this doesn't happen, first check that 'Hide results' in the Options menu has not been accidentally selected.

Otherwise try using the 'Last Results' File menu option. If this doesn't work then (Pro version only) check the browser you have selected in the Results options; a blank entry implies using your default browser. If nothing else is obviously wrong then it could be that you have a browser installed that is not set as the 'default'. In this case please consult your browser's help for information on setting it as the default.

If you are still having problems it could be that the results are stored somewhere inaccessible. Some organisations mount the Windows Documents folder (the default place for the results) on a network drive, which can cause problems with browsers. With the Pro version you can enter a different results folder in the Results options. Otherwise you may have to open the folder where the results are stored and double-click the TotalValidator.html file to see the results.

Fewer pages than expected are being tested (Pro version only)

By default, Total Validator will only follow links on the same website as the start page, so if you start from www.mysite.com, then pages on mysite.com will not be tested because technically-speaking mysite.com and www.mysite.com could host completely different websites.

Any links embedded within javascript will be ignored, which may reduce the pages that will be checked. Note that using links within javascript is an accessibility failure and will also exclude those people who choose to disable javascript for security reasons.

Many Include options can be used to restrict which pages are tested, so if you've set any of those ensure you've understood how they work.

If the pages require authentication to view them, then see the Login forms topic. The next section may also be of use.

How do I check multiple sites or areas (Pro version only)?

Because Total Validator follows links, different parts of the same website that are not connected will not be tested. Also by default only pages on the same website as the start page will be tested.

To avoid these restrictions, create a simple web page consisting of absolute links to the various parts of the site, or to other websites. This page may be saved to the local filesystem so there's no need to deploy it to a website. Then use this page as the start page together with the Follow remote links option.

The Follow remote links option tells Total Validator to follow all links on the start page only even those on different websites. Total Validator will then treat each link (on this first page only) as if was the start page and report on all the results together.

For finer control you can also use the Only follow below, Exclude, Include and Depth options as well.

When I use AngularJS there are lots of errors

When AngularJS was first created it used attributes starting with ng-. This was a problem because this is not valid HTML and so can cause errors. But this was fixed by the AngularJS team a long time ago and developers should now use attributes starting with data-ng- instead.

As the Wikipedia for AngularJS entry explains: 'Since ng-* attributes are not valid in HTML specifications, data-ng-* can also be used as a prefix. For example, both ng-app and data-ng-app are valid in AngularJS.'

If you are using AngularJS, you may wish to consider using our Validate DOM option so that pages will only be tested after all the initial javascript has run.

My web pages are written using Javascript

Many modern websites are now written using a simple HTML web page and a Javascript framework or libraries to draw most of the web page. But Total Validator will normally just check the simple HTML web page sent by the web server, because it does not execute any javascript.

The solution is to use our browser extensions. These can send the DOM (the web page after the initial javascript has run) from the browser to the Total Validator application to be tested. In this way you can check web pages that users actually see.

You can start a DOM validation from the application or the browser, whichever you prefer. With the Pro version you can check an entire website this way with just one click.

Can I make it run faster?

There could be several reasons why Total Validator may appear to operate slowly when checking each page. It could be that your system has reached the limit of its own performance in terms of CPU power and/or the amount of available memory. However, there are several things you can try to improve matters as listed below:

The results are wrong

Please note that we originally developed Total Validator because of mistakes and limitations with other tools. So if you have used another tool that reports different results, it could be a problem with that tool.

Many other validators and help sites do not use the official standards but are interpretations of them. As a result they tend to be rife with popular assumptions which are actually mistakes. Free tools and sites in particular tend not to be regularly updated, and so often fall behind constantly evolving standards.

However, if you do think you've found a genuine error, then please report it using our Feedback Form. We are always happy to investigate, and if necessary, fix any issues with our products in order to provide the best user experience.

How do I test for Accessibility?

Please note that accessibility standards are generally guidelines and not rules, and so in many cases are open to different interpretations. They are designed to guide you into making good decisions, rather than providing prescriptive rules. As such it is not currently possible for automated test tools to test every part of each standard.

Test tools such as Total Validator can only guide you and should never be regarded as a stamp of approval. Never let zero errors and warnings be your only target. Bear in mind that it is possible to write a web page that passes all the tests of all validators and yet would still be difficult for people with accessibility issues to use. Equally, errors and warnings in validators are just there to alert you to potential issues, and so may appear when there is no accessibility issue at all.

We recommend that you always design pages from the start with accessibility in mind, and manually check them against the guidelines to ensure they meet your accessibility requirements. Use Total Validator to guide you and to help check for anything you may have missed, especially when making minor amendments to existing pages.

We've tried to follow the spirit and meaning of the accessibility guidelines, rather than blindly coding rules, so you may find many 'warnings' and 'notes' reported by other validators that simply don't appear in our results. This tends to be generic advice, which applies to both valid and invalid pages, and so is of little use. With Total Validator we try to keep this 'noise' to a minimum to make it easier to focus on what really needs addressing.

Note that conforming to accessibility standards also means strictly validated HTML, so that accessibility aids can properly read a site. It also means spell checking to ensure those with reading issues can use the site. Of course with Total Validator you can run an accessibility, HTML, and spell check test in one go, saving time and effort.

Using Total Validator with accessibility aids

We regularly test that Total Validator can be used entirely by keyboard, and that the web page results we generate are accessible.

To support screen readers, we make use of the Java Access Bridge for Windows, which is supported by many accessibility aids. After installing Total Validator for the first time, you may have to restart your screen reader for this to work. If restarting doesn't work then try manually switching on the Java Access Bridge as follows:

Restart both your screen reader and Total Validator, and try again.