Click the icon in the address bar or press Alt+Shift+V to validate the current page. Results can be seen in Chrome's JS console.

Latest Version

Version
4.1.0
Update
November 7, 2022
Size
108KiB
Developer
validity.org.uk
Category
Users
30,000+
Rating
3.8381 ★
Manifest Version
2
Web Store Status
Languages Support
English (UK)
See more
Permissions
Http://*/*
Https://*/*
Storage
See more

Validity Extension

Validity can be used to quickly validate your HTML documents from the toolbar.

Just click the icon in the toolbar to validate the current document without leaving the page. The number of validation errors can be seen in the tool tip and the detail can be seen in the console tab of Chrome's developer tools.

Validity also gives you the option to use your own installation of the W3C Validation Service. (For more information on installing the W3C Validation Service see the documentation at http://validator.w3.org/docs/install.html).

*** PLEASE DO NOT POST BUG REPORTS AND FEATURE REQUESTS IN THE REVIEWS ON THIS PAGE as they are unlikely to be actioned, use the GitHub issue system instead (https://github.com/renyard/validity/issues). ***

Change Log:

4.1.0 (05/11/2022)
* Correctly label info messages. (Thanks to Eugene - https://github.com/chefranov)

4.0.2 (12/10/2021)
* Removed unused permission.

4.0.0 (06/11/2016)
* Validity now uses the Nu Validator (https://validator.w3.org/nu/) by default.
* Added option to use legacy W3C Validator for custom instances.

3.3.1 (29/09/2016)
* Added developer info to options dialog.

3.3.0 (28/09/2016)
* Warnings are now shown for valid documents. (#70)

3.2.2 (23/08/2016)
* Changed default validator, due to breaking change in W3C hosted instance.

3.2.1 (07/08/2016)
* Corrected the default validator in the options UI.

3.2.0 (31/07/2016)
* Changed default validator to W3C hosted instance.
* Fixed #68 error pages (response other then 200) cannot be validated.

3.1.0 (17/01/2016)
* Suppressed the \"This interface to HTML5 document checking is obsolete.\" message.

3.0.1 (26/04/2015)
* Changed the default validator to an instance run specifically for Validity.
* The validator uses SSL encryption by default, scoring an A on SSL Check (https://sslcheck.globalsign.com/en_GB/sslcheck/?host=html.validity.org.uk).
* The new validator instance should also fix the \"Bad Gateway\" errors, which are believed to be due to rate limiting on the W3C Validator.

2.0.2 (14/07/2014)
* Fixed a bug in loading the custom validator value on the options page.

2.0.1 (11/07/2014)
* Fixed a bug when the validator message contains a quote.

2.0.0 (09/07/2014)
* Support for Retina & high dpi displays.
* Regular expressions are now supported for host matching in options.
* The keyboard shortcut can now be changed via the \"Keyboard shortcuts\" dialog on the extension management page.
* Options are now synced via your Google or Opera Sync account.
* Regular expressions can now be used to match hosts.
* Rewrote the build script to use Grunt and include unit tests and linting.

1.3.0 (23/05/2013)
* Wildcards are now supported in specified and automatically validated hosts.
(Thanks to David Godfrey - https://github.com/ReactiveRaven)

1.2.4 (23/03/2012)
* Fixed bug with keyboard shortcut, introduced in 1.2.3.
* Restored default of true to collapse result option.

1.2.3 (14/03/2012)
* Collapse results option is now honoured.

1.2.2 (22/09/2011)
* No line is given when an error is not specific to a line.
* When one error is found, console output is no longer plural.
* An error is no longer thrown when a message contains a line break.
(Thanks to Mathieu Turcotte - https://github.com/MathieuTurcotte)

1.2.1 (17/08/2011):

* Fixed a bug where domains with hyphens were not recognised for auto validation and enabling for specific hosts.
(Thanks to Luke Armstrong - https://github.com/lukearmstrong)

1.2.0 (19/07/2011):

* HTTPS pages are now supported.
* More improvements to the Options UI.
* Reduced memory and CPU footprint.

1.1.0 (23/01/2011):

* Validator warnings are now displayed with errors in the console.
* Improvements to the options UI.

1.0.0 (13/11/2010):

* Complete rewrite.
* Supports installs of legacy versions of the W3C Validator commonly found in software repositories.
* Source code is now hosted on GitHub (https://github.com/renyard/validity).

0.3:
* Pages are now sent to the validator as a fragment, meaning that pages are not required to be accessible to the validator.
* Validation errors are now detailed in the Javascript console.
Read more

Source Manifest.json

{"update_url": "https://clients2.google.com/service/update2/crx","name": "__MSG_extn_name__","version": "4.1.0","default_locale": "en_GB","minimum_chrome_version": "53","description": "__MSG_extn_description__","icons": {"16": "icons/16.png","32": "icons/32.png","48": "icons/48.png","64": "icons/64.png","128": "icons/128.png"},"permissions": ["http://*/*", "https://*/*", "storage"],"content_security_policy": "script-src 'self' https://ssl.google-analytics.com; object-src 'self'","content_scripts": [{"matches": ["http://*/*", "https://*/*"],"js": ["validity.js"]}],"background": {"scripts": ["background/controller.js","background/net.js","background/stats.js","background/nu.js","background/xml.js","background/ui.js","background/util.js","background/opts.js","background/upgrade.js"]},"page_action": {"default_icon": {"19": "icons/19.png","38": "icons/38.png"},"default_title": "__MSG_page_action_title__"},"commands": {"_execute_page_action": {"suggested_key": {"default": "Alt+Shift+V","mac": "Alt+Shift+V"},"description": "__MSG_page_action_title__"}},"options_page": "options.html","manifest_version": 2}
Read more

How to download and manually install Validity extension for Chrome

Looking for a way to install Validity extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.

However, you may need to install Validity extensions manually, this article outlines two simple methods to effortlessly install Validity extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.

Method 1: Download Validity extension and manually install through Drag &Drop

If you ever need to manually install a Validity extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.

Step 1: Download the Validity Extension by clicking the "Download CRX" button on the website.

Look for the Validity extension you wish to install. Go to the website and download the Validity extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for Validity extension that contains all the data.

Step 2: Extract &Arrange Files

Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.

Step 3: Go to the Chrome Extensions Page

Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.

Step 4: Drag and Drop the Extension

Now, go to the folder where you extracted the Validity extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.

Step 5: Complete the Installation

Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.

Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.

Method 2: Download Validity extension for Chrome and install in Developer Mode

This is another method to install Validity extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.

Step 1: Download the Validity extension file

Select and download the Validity extension by clicking the 'Download CRX' button on the website.

Step 2: Extract the downloaded contents

Convert the file to a ZIP file if it is in CRX format then extract the Validity extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your Validity extension running.

Step 3: Open Chrome Extension Setting Page

In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.

Step 4: Enable Developer Mode

After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.

Step 5: Load the Unpacked Extension

Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."

Step 6: Select the Extension Folder

Once the pop-up opens upon clicking Load unpacked, select the Validity extension directory and click on the "Select Folder "button.

Step 7: Confirm and Install

After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.

Conclusion

Here we've made a step-by-step guide on How to manually install Validity extension in 2 ways. We hope this guide proves helpful.

Similar Extensions

icon

HTML Validator Extension · Developer Tools 30,000+ 37 ★ 2.5MiB

icon

Web Developer Extension · Developer Tools 30,000+ 2829 ★ 574KiB

icon

Web Developer Checklist Extension · Developer Tools 30,000+ 54 ★ 32.65KiB

icon

CSS3 Generator Extension · Developer Tools 30,000+ 60 ★ 346KiB

icon

jQuery Debugger Extension · Developer Tools 30,000+ 110 ★ 88.52KiB

icon

axe DevTools - Web Accessibility Testing Extension · Accessibility 30,000+ 114 ★ 2.89MiB

icon

HeadingsMap Extension · Developer Tools 30,000+ 70 ★ 575KiB

icon

CSS Shapes Editor Extension · Developer Tools 30,000+ 101 ★ 84.76KiB

icon

Xdebug helper Extension · Developer Tools 30,000+ 429 ★ 70.13KiB

icon

WAVE Evaluation Tool Extension · Accessibility 30,000+ 143 ★ 344KiB

icon

Emmet Re:view Extension · Developer Tools 30,000+ 162 ★ 74.65KiB

icon

LiveReload Extension · Developer Tools 30,000+ 808 ★ 60.78KiB

icon

PageSpeed Insights (MV3) Extension · Developer Tools 30,000+ 77 ★ 524KiB

icon

Kingsquare HTML Validator Extension · Developer Tools 30,000+ 36 ★ 1.0MiB

icon

Emmet LiveStyle Extension · Developer Tools 30,000+ 351 ★ 356KiB

icon

HTML5 Outliner Extension · Productivity 30,000+ 262 ★ 25.23KiB

icon

Grid Ruler Extension · Developer Tools 30,000+ 335 ★ 288KiB

icon

CSS remove and combine Extension · Developer Tools 30,000+ 115 ★ 270KiB

icon

CSSViewer Extension · Developer Tools 30,000+ 371 ★ 301KiB

icon

Code Cola Extension · Developer Tools 30,000+ 188 ★ 189KiB

icon

Dimensions Extension · Developer Tools 30,000+ 454 ★ 17.28KiB

icon

Check My Links Extension · Developer Tools 30,000+ 411 ★ 161KiB

icon

DevTools Theme: Zero Dark Matrix Extension · Developer Tools 30,000+ 545 ★ 56.82KiB

icon

PerfectPixel by WellDoneCode (pixel perfect) Extension · Developer Tools 30,000+ 605 ★ 732KiB

User reviews

icon

Andrés Peña (ID: 00000083ca2e719c) Voted 1 ★ - Updated 05/24/2021 It stopped working. They must remove it from the Chrome Web Store.

icon

Rafi Strauss (ID: 000000e8decdb08f) Voted 5 ★ - Updated 09/01/2017 Works fantastically, speeds up my validation workflow by an order of magnitude

icon

Stuart McMillan (ID: 0000007c19aae234) Voted 5 ★ - Updated 07/19/2017 12/10 would validate again

icon

Jimmy (ID: 00000008691966fe) Voted 3 ★ - Updated 06/15/2017 Getting "The character encoding was not declared. Proceeding using “windows-1252”." for all websites. Particularly, mine does declare UTF-8

icon

Nguyen Long (ID: 000000d20453efe8) Voted 5 ★ - Updated 05/11/2017 very good