Rich Caloggero | 1 Nov 00:06 2014

Re: What happened to text input

Ah, just used with html5 doctype and it used automatically:
The uploaded document was successfully checked as HTML5. This means that the resource in question identified itself as "HTML5" and that we successfully
performed a formal validation of it. The parser implementations we used for this check are based on (HTML5).
-- Rich
Sent: Friday, October 31, 2014 6:56 PM
Subject: What happened to text input
I use this thing to quickly check demo code to be sure the html is at least generally valid: i.e. element x cannot contain elements of type y.
The validator used to accept input from a textarea, but this is now gone.
-- Rich
narve | 28 Oct 08:44 2014

HTML5 Conformance Checker: Warning on element <menu>

The menu element is now supported by all major browsers, and has been 
for quite a long time. Thus; the warning "The menu element is not 
supported by browsers yet. It would probably be better to wait for 
implementations" only confuses webdesigners and acts as a brake for 

Narve Holm

- -
- -
- -
- -

Arjan den Boer | 26 Oct 22:39 2014

Incorrect error reported in Javascript

Dear W3C,

I used the HTML validator to verify the following page: and I get the following error:

Line 37, Column 209: end tag for element "A" which is not open …g id='tn"+j+"' class='"+cn+"' src='thumbnail.php?sqz=90&img="+imgs[j]+"'></a>"} This is in the HEAD section of the document and within <script ...><!-- and --></script> tags.
Why is the validator checking to-be-generated-HTML within a javascript, even within comment <!--/--> tags?

Thanks and regards,

Arjan den Boer

Roman Grinyov | 26 Oct 21:38 2014

Validator error

Validation of this page:; an error occurs in line 33. However apparent reason at no.
Dave Thompson | 21 Oct 03:53 2014

Incorrectly flagging Duplicate IDs

NOTE: Whenever possible, give the address of the document you were checking.

This is the error I am getting using the validation tool:

Validation Output: 1 Error

Line 56, Column 98: Duplicate ID blackLink. …" href="mailto://freesoftwaredave <at>">freesoftwaredave <at></a></p>

However, when the second "duplicate" id is removed to comply with the validation tool, the desired effect...that being the email link having a Bold effect on rollover and black text color, is not present.  I have to replace the ID= in the <a> tag of the emailto link in order for this to work.  Which then gets me the error.

I am not sure what I can recommend to look for bug-wise, since what I'm doing might be a gray area.  I only know that I need a clean bill of health HTML-wise or my instructor will doc me on points.  I could remove the offending tag to get this, but the effect is not what I desire design-wise.

I cannot give the link to the document as the file is on my college's server and I have no idea how long it will be there.  I am in Unit8 of 10 right now so in under 2 weeks the class will be over and that file will likely no longer be I included the text of the file here as well as the style-sheet the definition in question is defined in.

HTML File:

<!DOCTYPE html>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <meta charset="UTF-8">
    <title>Dave Thompson, I.T. Consultant - Open Source Migration Specialist</title>
    <link rel="stylesheet" type="text/css" href="externalstylesheet.css">
      <style type="text/css">
        td.bkgnd {padding: 9px;}
        table.bkgnd {border: 1px solid black; background-color: linen;}
        h1 {font-family: arial; font-size: 16pt; font-style : italic}
        th {font-size: 10pt;}
<table style="width:100%;">
<tr style="width:100%;">
  <td style="width:100%;">
    <table class="bkgnd" style="width:800px; display: block; margin: 0 auto;">
          <td style="width: 800px">
              <h1 style="align:center">Dave Thompson's Contact Page</h1>
              <ul id="list-nav" style="display: block; margin:0 auto">
                  <li><a href="index.htm">Home</a></li>
                  <li><a href="bio.htm">Bio</a></li>
                  <li><a href="career.htm">Career</a></li>
                  <li><a href="realLinks.htm">Links</a></li>
                  <li><a href="contact.htm">Contact</a></li>
              <p style="text-align:center; font-size: smaller">** All content on this site created with <a href="">Brackets</a> editor **</p>
              <p>My contact info:</p>
              <p style="font-weight:bold">
                  Dave Thompson<br>
                  <span style="font-weight:normal">
                      <span style="text-decoration: underline;">
                      <span style="text-decoration: none; color:black"><br>
                          5903 Cherokee Loop SE<br>Lacey, Wa. 98503<br><br></span>
                      <span style="text-decoration: underline;">
                      <span style="text-decoration: none; color:black"><br>
                      <span style="text-decoration: underline;">
                      <span style="text-decoration: none;"><br>
                          Personal: <a id="blackLink" href="" target="_blank"></a><br>
              <p>You can reach me at: <a id="blackLink" href="mailto://freesoftwaredave <at>">freesoftwaredave <at></a></p>
          <a href="">
              <img style="border:0;width:88px;height:31px"
                   alt="Valid CSS!" />


External Style-Sheet:

h1 {
    text-align: center;
    font-family: Arial, Verdana, Sans-Serif;
    color: #0000ff;

body {
    background-color: #ffdfd0;
    font-family: Times New Roman, Garamond, Serif;
    font-size: 18px;
    color: #00008b;

ul#list-nav li a:visited {
    padding:5px 0;
    border-left:1px solid #ffffff;

ul#list-nav {
    overflow: hidden;

ul#list-nav li {

ul#list-nav li a:link {
    padding:5px 0;
    border-left:1px solid #ffffff;

ul#list-nav li a:hover {

a:link#blackLink {
    color: black;

a:visited#blackLink {
    color: black;

a:hover#blackLink {
    font-weight: bold;
    color: black;

a:active#blackLink {
    font-weight: bold;
    color: black;

Andry Rendy | 17 Oct 04:20 2014

<input <at> accept> false positive issue.

To the Service responsibles.
An old issue about hasn't been fixed as of now, and I think it is preventing my page from being checked properly.

Error: Bad value for attribute accept on element input: Expected a token character or / but saw , instead.
From line 551, column 16; to line 551, column 439
          <input type="file" id="attachment" name="attachment[]" accept=".jpg,.png,.bmp,.tif,.jpeg,.x-png,.bm,.tiff,image/jpeg,image/pjpeg,image/png,image/bmp,image/x-windows-bmp,image/tiff,image/x-tiff" />

According to the specs, the attribute <at> accept on element <input> can have as value both a MIME type and a file extension, but the validator seems to consider invalid those values beginning with a dot.
This is an old issue which was reported long ago. Please fix it.
Andrea Rendine
Marco Davids | 15 Oct 09:47 2014



I disabled SSLv3 due to Poodle and now the HTML validator does no longer

500 SSL negotiation failed:



Attachment (smime.p7s): application/pkcs7-signature, 5706 bytes
Michael[tm] Smith | 13 Oct 16:08 2014

FYI: HTML5 validator sources have moved, build instructions changed

This is just a heads-up to anybody building and running the Nu Markup
Checker ( HTML5 validator) from the github sources.

We've moved all the sources to
and also changed the build instructions. The new instructions are at:

It just amounts to cloning
instead of

The old/existing build script has been changed such that after you pull the
latest version of it and run it (e.g., when doing "./ all"), it'll
now just exit with a message saying that the build script has moved to

But If you're not ready to update to the new build environment yet, you can
still force the old build script to run by specifying the "--legacy" option:

  python build/ --legacy all

But note that the code you'd be building and running from in that case is
frozen, so you wouldn't ever get any further updates unless/until you move
to the new build setup.

If you run into any problems with either the old or new build setups,
please either report it at or
just post a message to this list with the details.

Also keep in mind that you don't need to build from the sources in order to
run your own instance of the checker. You can now instead just use the
latest jar (or war) release:

Instructions how to run an instance of the checker service using one of
those release files are here:



Michael[tm] Smith
Guillaume Baudusseau | 10 Oct 17:38 2014

Re: RSS paid access?

Hi Zachary,

RSS Feed Validator use a software that is not developed at W3C. You can find the original project here :

This is some link which can help you :

install documentation :
to send an issue :!forum/feedvalidator-users

Best Regards,


On 09/10/2014 17:46, BURNHAM Zachary wrote:
We're trying to implement the python script in place of using your web service but there are a couple of issues we're running into. What I had hoped to do was run the command line utilitiy ( and use the result of that to determine validity. However, there doesn't appear to be a clear method to make that determination; the result code from the command always seems to be 1 no matter the validity (or lack thereof) of the rss feed. Is there something else to go by here? Do we have to implement this as a cgi? Is there another way to go? Best Regards, Zachary BURNHAM Senior SolidWorks Community Developer ----------------------- Office: +1 78 1810 3824 zachary.burnham <at> ----------------------- DS SolidWorks Corporation | 175 Wyman Street | Waltham, MA 02451 | United States -----Original Message----- From: Guillaume Baudusseau [mailto:guillaume <at>] Sent: Thursday, October 02, 2014 8:07 AM To: www-validator <at>; BURNHAM Zachary Subject: FW: RSS paid access? Hello Zachary, In the current state, the Validator Suite doesn't implement the RSS feed Validator. You can see on the main page, in "Features" section, the implemented functionalities as HTML, CSS & Internationalization validations. To use RSS Feed Validator you have to use Note that service doesn't support Website crawling and it check an only page per validation. Concerning this blocking message, the number of validations requests from an IP address is limited in time. W3C imposes restrictions to ensure the service remains available to the community. We will continue to increase Validator resources and services so feel free to ask me if you have some comments, questions or suggestions. Best regards, Guillaume -- Guillaume Baudusseau World Wide Web Consortium Validators Staff guillaume <at> Tel: +33 633 344 593 This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged. If you are not one of the named recipients or have received this email in error, (i) you should not read, disclose, or copy it, (ii) please notify sender of your receipt by reply email and delete this email and all attachments, (iii) Dassault Systemes does not accept or assume any liability or responsibility for any use of or reliance on this email. For other languages, go to

-- Guillaume Baudusseau World Wide Web Consortium Validators Staff guillaume <at> Tel: +33 633 344 593

Tell me the solution, not just the problem


Address of the document I was checking:

The Error message tells me something is wrong, but fails to suggest a solution. This is not helpful unless I’m a guru who would probably not have got it wrong in the first place.

E.g. Unable to Determine Parse Mode!

“The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:

• the MIME Media Type (text/html) can be used for XML or SGML document types

•the Document Type (-//w3c//dtd html 4.0 transitional//en) is not in the validator's catalog

•No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.

•No XML namespace (e.g <html xmlns="" xml:lang="en">) could be found at the root of the document.

As a default, the validator is falling back to SGML mode.”


Validation Output: 1 Error

Error Line 1, Column 61: invalid formal public identifier "-//w3c//dtd html 4.0 transitional//en": invalid public text class <!doctype html public "-//w3c//dtd html 4.0 transitional//en">

This is not very helpful: OK, so tell me what I should (or could) be using! HELP!



Philip Tory

Authorgraphic Ltd
Unit 29, King Edwards Avenue, Gloucester GL1 5DD   UK
Tel: 01452 - 500 639 




Fabio Adorno | 2 Oct 16:24 2014

Please where could I  identify  the exact line  on my code that is producing this Warning ?
Thank You,
Fabio Adorno – Sao Paulo – Brasil