extension ExtPose


CRX id


Description from extension meta

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.

Image from store Validity
Description from store 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.

Latest reviews

  • (2021-05-24) Andrés Peña: It stopped working. They must remove it from the Chrome Web Store.
  • (2019-12-21) sriram venkataramani: gentlemen,gentiles,and mail.-G,g-mail.
  • (2017-09-01) Rafi Strauss: Works fantastically, speeds up my validation workflow by an order of magnitude
  • (2017-07-19) Stuart McMillan: 12/10 would validate again
  • (2017-06-15) Jimmy “Jay” Hellas: Getting "The character encoding was not declared. Proceeding using “windows-1252”." for all websites. Particularly, mine does declare UTF-8
  • (2017-05-11) Nguyen Long: very good
  • (2017-03-13) Omar Fadl: مفيد جدا يكتشف الاخطاء التكويدية الخاصة بالصفحة بدلا من رفع الصفحة على الانترنت واعتماد الصفحة ان ليس بها اخطاء
  • (2017-02-14) Marc Reitz: Doesn't work. Complains about character encoding not declared. But it is declared and W3-Validator shows no problems. So: Useless Extension
  • (2017-02-06) Igor Surini: the instruction are outdated/faulty, after "icon-click" it opens only menu, no validation at all...
  • (2017-02-04) Not Applicable: Lacks an option to ignore certain error/warning types which is important since the official validator flags errors for non-standard attributes which are still VALID under HTML 5. Makes the results very hard to use for anyone using AngularJS or similar on their site.
  • (2017-02-03) M Usman Nadeem: icon show in bar but did not work
  • (2016-10-12) constantine: The only validation plugin that works for me for webpages that are not online yet / on a proxy. Works like a charm, thanks.
  • (2016-10-07) Ivan Beldad: Doesn't work
  • (2016-09-13) sip
  • (2016-09-12) Артур Кайтмазов: There is no icon in adress bar(((
  • (2016-07-20) 양재상: Excellent! Auto validation!
  • (2016-06-07) Erik Blumstengel: This helped me a lot, I think I'll use it from now on for all of my projects. It showed me a lot of problems I didn't see before, and the usage of the Console of the Dev Tools is really nice. Really good work, thank you very much for this addon!
  • (2016-05-24) Good tool for developer!
  • (2016-05-21) Mike Kroger: Works well but doesn't validate dynamically loaded (AJAX) content.
  • (2016-05-10) Steve Sloan: Icon appears in Chrome menu, but button does nothing. Restarted chrome, reloaded all pages, still nothing.
  • (2016-04-12) Radek Juřica: Great extension. How can i set rule for validation domain with all third-subdomains? For example: www.example.com test.example.com a.example.com b.example.com a-b-c.example.com
  • (2016-04-06) Vermus: Хрень по-моему, в w3c validator хоть какой-то кусочек кода показывают - тут вообще только строка и столбец. Ну и что мне делать с этим, если у меня html сжатый в одну строку, искать 5456 столбец? Как? Копировать в редактор и смотреть столбец? Короче бесполезное приложение, надеялся на какую-то интерактивность, типа подсвечивание на странице "view-source:", раз устанавливается как приложение в бразуер - но нет. w3c validator online выполняет те же функции, да еще удобнее.
  • (2016-01-02) Neville Dastur: Doesn't show where the error in the source file is. Doesn't work properly with local files which is main reason for using something like this. For non local files just run it through validator.w3.org and it will give you far more useful output
  • (2015-12-20) Vadim Ribak: Very useful and easy to use! Thanks!
  • (2015-11-18) Dawid K: "Could not contact validator"
  • (2015-10-28) maksim: Good app, but it is too week... 1. It does not display, where is error occured. The message in console is not informative.. just number of line.. 2. It can not work with local pages (file:// ...) Seems, like this app is just a wrapper around https://validator.w3.org
  • (2015-10-28) Eric Bertrand: No icon appears in the address bar. Shortcut doesn't work. Removed from my chrome apps.

Latest issues

  • (2015-02-19, v:2.0.2) Doaa Magdy: could not contact validator : bad Gateway
    Hello, While i'm trying to validate a page located on a local server with the local IP ... the URL looks like that http:\\\app1\page1.php i keep getting this error "could not contact validator : bad Gateway" please adivse what can i do to get it to work
  • (2014-11-26, v:2.0.2) Gareth Elms: Permissions for Validity
    Hi, can you please explain what "Read and change all your data on the websites you visit" means and why your extension needs it, and what it actually does with the data? Thanks


36,322 history
3.8 (212 votes)
Last update / version
2022-11-07 / 4.1.0
Listing languages