Why use separate validation tools to check your web pages when you only need one?
The Total Validator Tool performs the most important validations on your web pages: True (X)HTML validation against published W3C/ISO DTDs; accessibility validation against the W3C and US Section 508 guidelines; spell checking against one of five languages; and testing for broken links.
Why these 4 validations ...
Search engine robots/spiders are very fussy and will not search or index some or all of a site if they come across invalid HTML. So if you want to be properly listed you need to be sure your HTML is valid.
Just because you can use your website doesn't mean that someone with a disability can. You should ensure your sites conform to the W3C WAI Accessibility Guidelines, (and that also means strictly W3C validated HTML), or US Section 508 standard, if you want your site to be accessible to all.
Spelling is often left unchecked and will make your site look and feel unprofessional and even unusable.
Broken links are the bane of every webmaster, you may get your internal links correct, but external sites tend to change all the time, and there's nothing that makes your site look worse than a link to nowhere. So you need to regularly check your site for broken links.
If you need more than the this tool provides then keep a look out for the full version that allows you to test more than a page at a time, has many more options and CSS Validation.
What is new in this release:
- New Firefox Extension which operates like the Chrome Extension
- Minor improvements to the original Firefox Extension, which is now deprecated, along with support for SeaMonkey
- New Pro Tool menu option allows manual editing of the list of valid HTML5 meta names between Total Validator releases
- Improved handling of ambiguous and non-ambiguous ampersands
- Support of <title>, and <textarea> elements containing raw data in HTML5 documents
- The minimum amount of memory required to run Total Validator has been halved to better support older computers
- HTML5 Image Description Extension updated to 26 February 2015
- Early support for Filter Effects Module Level 1 (25 November 2014)
- CSS Box Alignment Module Level 3 updated to 18 December 2014
- Compositing and Blending Level 1 updated to 13 January 2015
- CSS Exclusions Module Level 1 updated to 15 January 2015
- CSS Fragmentation Module Level 3 updated to 29 January 2015
- CSS Positioned Layout Module Level 3 updated to 3 February 2015
- CSS Counter Styles Level 3 updated to 6 February 2015
- CSS Basic User Interface Module Level 3 updated to 24 February 2015
- Bug Fix: With Linux, when the 'Documents' folder didn't exist, it didn't default to using the installation folder
- Bug Fix: Labelable elements within <label> incorrectly required explicit for/id linking
- Bug Fix: Duplicate attributes created additional 'nonsense' errors
- Bug Fix: Absolute URLs were not always normalized properly
What is new in version 8.6.1:
Bug Fix: Incorrect check of HTML5 Wiki based meta names
Bug Fix: CSS3 'display' definition was incorrect due to mistake in CSS
Display Module Level 3 (11 September 2014)
Bug Fix: An empty would mess up the next