Accessibility, HTML, CSS, Broken Links, Spell Check

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

There is a known issue with some older versions when you try to use the Install button to upgrade the Windows (.msi) version (Basic and Pro). After downloading the new version the installer fails to run, and a Windows Installer message is displayed instead.

Close this window, restart the TV application, and use the Download button instead. Then close the TV application and manually run the .msi file you downloaded to upgrade.

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

Any error messages that are displayed 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 Contact Form to report the problem.

If no error messages appear on screen, and Total Validator does not appear, or fails to start up fully, then please check any anti-virus program you have as this is the most common reason for Total Validator failing to start. Otherwise, complete our Contact Form to report the problem.

This message appears when Total Validator cannot make a network connection to the start web page. Try using the same URL in your browser to check there is no underlying network issue.

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 test 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 Contact Form to report your issue.

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. When running for the first time a message may appear asking for permission to write there. If you do not allow this the tests will stop and an error may appear. With the Pro version, if you wish to, you can specify a different folder for the results.

When you try to install Total Validator you may see an 'unrecognised app' message from Microsoft's SmartScreen together with 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 an 'Unknown publisher' message from User Account Control. This is because we currently do not sign our Windows installer. One of the main reasons for signing, is to verify the original program is unaltered. 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, you can be sure you have the original, complete, and unmodified program provided by us.

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 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, you can be sure you have 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.

When the test is finished, your browser should display the results. There can be a number of reasons why this doesn't happen:

First try using the Last Results File menu option. If the message Could not locate results appears then the results are not being displayed because they have not been saved: With the Pro version check that the Results folder exists and is writable. Some anti-virus programs may also block access to this location, so check any anti-virus settings as well. With the Pro version try entering a different Results folder, one which Total Validator does have permission to write to, and is on your local computer and not on a remote network drive.

Normally, Total Validator tries to display the results using your default browser. With Windows in particular, this can often become unset, so please follow your browser's help to set it as the default again.

With the Pro version check that Browser: None has not been selected accidentally. Otherwise, check the browser selected. A blank entry implies using your default browser. If you have entered anything here, then try blanking this out, otherwise try entering the path/name (as appropriate to your O/S) of a browser to see if that resolves the issue.

It could also be that the results are stored somewhere your browser cannot access. 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, one which is on your local computer.

If all else fails you may have to open the folder where the results are stored and double-click the TotalValidator.html file to view the results.

By default, when displaying web pages from your computer, Safari blocks css, images and javascript files. So the Total Validator results may be difficult to read.

You could use another browser to display the results, or you can configure Safari to allow it to display local resources:

• Open Safari's Preferences and in the Advanced section select Show Develop menu ...
• In the main menu, click Develop
• Select Disable Local File Restrictions
• Restart Safari

The Total Validator results pages should now display correctly.

First try testing a different site, such as totalvalidator.com or google.com. If it works, then there must be something about the site you are trying to test which is causing the number of pages to be restricted.

By default, Total Validator respects any robots.txt file on the site and so may be ignoring many pages. So uncheck this option and try again.

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 number of pages that will be tested. Note that using links within JavaScript is an accessibility failure and will also exclude those people who choose to disable JavaScript for security reasons.

If your website uses a JavaScript framework or libraries to draw most of the web page, then Total Validator may not see links to many other pages. Please see the My web pages are written using JavaScript topic below for more information.

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 some pages require authentication to view them, then see the Login forms topic. The next section may also be of use.

Because Total Validator follows links, different parts of the same website that are unconnected 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 file system, 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 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.

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 test 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 test web pages that users actually see.

You can start a DOM test from the application or the browser, whichever you prefer. With the Pro and CI versions you can test an entire website this way with just one click.

There could be several reasons why Total Validator may appear to operate slowly when testing 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 broken links option waits for a response from the web server. If you do have any broken links then this will naturally slow down testing. With the Pro version you can reduce the timeout from the default of 20 seconds and raise the concurrency (or set it to 0 or leave it blank for unlimited). Alternatively turn off the broken link check altogether.
• The spell check has a double impact on performance. Loading the dictionaries uses a lot of memory, and it can take time to spell check each word. Try turning this option off to see if this helps.
• Try limiting the number of other applications that are running concurrently
• When testing remote pages close any other applications that may be using the network

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 Contact Form. We are always happy to investigate, and if necessary, fix any issues with our products, to provide the best user experience.

Accessibility standards are typically guidelines and not rules. They are designed to guide you into making good decisions, rather than providing prescriptive rules. Some human judgement may also be called for, making it impossible to check everything with automated tools: For example, checking that a text description of an image (in any language) describes that image.

However, tools like Total Validator can help you quickly identify potential issues, and can be used during all parts of the initial development process, and afterwards when updating a website. They can provide automated checks for anything you may have missed, across large numbers of pages, where manual checks would be too impractical and costly.

Conforming to accessibility standards also means strictly validated HTML and CSS, so that accessibility aids will operate correctly. It also means spell checking, to ensure users can understand the content. That's why with Total Validator you can test Accessibility, HTML, CSS, and spelling in one go, saving time and effort, whilst ensuring your site is truly accessible.

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:

• Open the folder where Total Validator was installed. For example: C:\Program Files\TotalValidator
• Press the key combination: Shift+F10
• Select the option Open command window here or Open PowerShell window here
• Type the following into the command window: runtime\bin\jabswitch -enable
• Download the 64-bit Access Bridge for Windows into the C:\Windows\System32 folder
• Download the 32-bit Access Bridge for Windows into the C:\Windows\SysWOW64 folder

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