Result for http://vaprogressive.com/

Jump To:

Results

Result:	Failed validation, 54 errors
Address:
Encoding:	utf-8
Doctype:	XHTML 1.0 Transitional
Root Namespace:	http://www.w3.org/1999/xhtml

Result:

Failed validation, 54 errors

Address:

Encoding:

utf-8

Doctype:

XHTML 1.0 Transitional

Root Namespace:

http://www.w3.org/1999/xhtml

Revalidate With Options

Show Source	Show Outline
Show Parse Tree	...no attributes
Validate error pages	Verbose Output

Help on the options is available.

Note: The Validator XML support has some limitations.

This page is not Valid XHTML 1.0 Transitional!

Below are the results of checking this document for XML well-formedness and validity.

Error Line 49 column 252: "Uptown" is not a member of a group specified for any attribute.
```
...e="Comment on The CCC is the "Uptown KKK"">[2] Comments</a>&nbsp;</div>
```
✉
Error Line 49 column 255: an attribute value literal can occur in an attribute specification list only after a VI delimiter.
```
...Comment on The CCC is the "Uptown KKK"">[2] Comments</a>&nbsp;</div>
```
Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

✉
Error Line 295 column 2: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
```
<p>
```
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

✉
Error Line 296 column 3: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
```
<ul>
```
✉
Error Line 297 column 7: document type does not allow element "center" here; assuming missing "li" start-tag.
```
<center>
```
✉
Error Line 298 column 83: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
```
...James Webb for US Senate 2006"target=_blank><img src="http://img.photobucket.
```
✉
Error Line 298 column 201: end tag for "img" omitted, but OMITTAG NO was specified.
```
...g" alt="James Webb for US Senate"></a>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

✉

Info Line 298 column 90: start tag was here.

...ebb for US Senate 2006"target=_blank><img src="http://img.photobucket.com/alb

Error Line 300 column 4: end tag for "li" omitted, but OMITTAG NO was specified.
```
</ul>
```
✉
Info Line 297 column 0: start tag was here.
```
<center>
```
Error Line 301 column 3: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
```
<ul>
```
✉
Error Line 302 column 7: document type does not allow element "center" here; assuming missing "li" start-tag.
```
<center>
```
✉
Warning Line 303 column 68: cannot generate system identifier for general entity "ran".
```
...ds.com/stories/story.cfm?story=94209&ran=222708"title="Creigh Deeds"><img src
```
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

✉
Error Line 303 column 68: general entity "ran" not defined and no default entity.
```
...ds.com/stories/story.cfm?story=94209&ran=222708"title="Creigh Deeds"><img src
```
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

✉
Warning Line 303 column 71: reference not terminated by REFC delimiter.
```
...com/stories/story.cfm?story=94209&ran=222708"title="Creigh Deeds"><img src="h
```
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

✉
Warning Line 303 column 71: reference to external entity in attribute value.
```
...com/stories/story.cfm?story=94209&ran=222708"title="Creigh Deeds"><img src="h
```
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.

✉
Error Line 303 column 71: reference to entity "ran" for which no system identifier could be generated.
```
...com/stories/story.cfm?story=94209&ran=222708"title="Creigh Deeds"><img src="h
```
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

✉

Info Line 303 column 67: entity was defined here.

...ads.com/stories/story.cfm?story=94209&ran=222708"title="Creigh Deeds"><img sr

Error Line 303 column 208: end tag for "img" omitted, but OMITTAG NO was specified.
```
...jpg" alt="Mark Warner for President"> </a></center></center></ul>
```
✉

Info Line 303 column 100: start tag was here.

...4209&ran=222708"title="Creigh Deeds"><img src="http://vaprogressive.com/wp-co

Error Line 303 column 230: end tag for element "center" which is not open.
```
...for President"> </a></center></center></ul>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occured in a script section of your document, you should probably read this FAQ entry.

✉
Error Line 303 column 235: end tag for "li" omitted, but OMITTAG NO was specified.
```
...resident"> </a></center></center></ul>
```
✉
Info Line 302 column 0: start tag was here.
```
<center>
```
Error Line 304 column 3: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
```
<ul>
```
✉
Error Line 305 column 7: document type does not allow element "center" here; assuming missing "li" start-tag.
```
<center>
```
✉
Error Line 306 column 84: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
```
...le="Mark Warner for President"target=_blank><img src="http://www.draftmarkwar
```
✉
Error Line 306 column 194: end tag for "img" omitted, but OMITTAG NO was specified.
```
..." alt="Mark Warner for President"></a></center></center></ul>
```
✉

Info Line 306 column 91: start tag was here.

...k Warner for President"target=_blank><img src="http://www.draftmarkwarner.com

Error Line 306 column 212: end tag for element "center" which is not open.
```
... for President"></a></center></center></ul>
```
✉
Error Line 306 column 217: end tag for "li" omitted, but OMITTAG NO was specified.
```
...President"></a></center></center></ul>
```
✉
Info Line 305 column 0: start tag was here.
```
<center>
```
Error Line 307 column 5: end tag for "p" omitted, but OMITTAG NO was specified.
```
 </li>
```
✉
Info Line 295 column 0: start tag was here.
```
<p>
```
Error Line 307 column 5: end tag for "p" omitted, but OMITTAG NO was specified.
```
 </li>
```
✉
Info Line 294 column 0: start tag was here.
```
<p>
```
Error Line 326 column 9: ID "meta" already defined.
```
 <li id="meta"><h4>Meta:</h4>
```
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

✉
Info Line 293 column 9: ID "meta" first defined here.
```
 <li id="meta"><h4>Democrats We Support:</h4>
```
Error Line 337 column 9: ID "meta" already defined.
```
 <li id="meta"><h4>Acknowledgements:</h4>
```
✉
Info Line 293 column 9: ID "meta" first defined here.
```
 <li id="meta"><h4>Democrats We Support:</h4>
```
Error Line 337 column 14: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag.
```
 <li id="meta"><h4>Acknowledgements:</h4>
```
✉
Error Line 339 column 7: document type does not allow element "center" here; assuming missing "li" start-tag.
```
<center>
```
✉
Warning Line 340 column 80: cannot generate system identifier for general entity "user".
```
...og=http%3A%2F%2Fvaprogressive.com%2F&user=45205"><img src="http://blogshares.
```
✉
Error Line 340 column 80: general entity "user" not defined and no default entity.
```
...og=http%3A%2F%2Fvaprogressive.com%2F&user=45205"><img src="http://blogshares.
```
✉

Warning Line 340 column 84: reference not terminated by REFC delimiter.

...ttp%3A%2F%2Fvaprogressive.com%2F&user=45205"><img src="http://blogshares.com/

✉

Warning Line 340 column 84: reference to external entity in attribute value.

...ttp%3A%2F%2Fvaprogressive.com%2F&user=45205"><img src="http://blogshares.com/

✉

Error Line 340 column 84: reference to entity "user" for which no system identifier could be generated.
```
...ttp%3A%2F%2Fvaprogressive.com%2F&user=45205"><img src="http://blogshares.com/
```
✉

Info Line 340 column 79: entity was defined here.

...log=http%3A%2F%2Fvaprogressive.com%2F&user=45205"><img src="http://blogshares

Error Line 341 column 4: end tag for "li" omitted, but OMITTAG NO was specified.
```
</ul>
```
✉
Info Line 339 column 0: start tag was here.
```
<center>
```
Error Line 343 column 7: document type does not allow element "center" here; assuming missing "li" start-tag.
```
<center>
```
✉
Error Line 344 column 165: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
```
...treet.gif?XYSHCGMB1143739224' border=0 /></a></center>
```
✉
Error Line 344 column 168: required attribute "alt" not specified.
```
...et.gif?XYSHCGMB1143739224' border=0 /></a></center>
```
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

✉
Error Line 345 column 4: end tag for "li" omitted, but OMITTAG NO was specified.
```
</ul>
```
✉
Info Line 343 column 0: start tag was here.
```
<center>
```
Error Line 347 column 7: document type does not allow element "center" here; assuming missing "li" start-tag.
```
<center>
```
✉
Error Line 348 column 8: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
```
<a href=http://www.leftyblogs.com><img src=http://www.leftyblogs.com/button.gif 
```
✉
Error Line 348 column 14: NET-enabling start-tag not immediately followed by null end-tag.
```
<a href=http://www.leftyblogs.com><img src=http://www.leftyblogs.com/button.gif 
```
This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

✉
Error Line 348 column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.
```
...f=http://www.leftyblogs.com><img src=http://www.leftyblogs.com/button.gif bor
```
✉
Error Line 348 column 49: NET-enabling start-tag not immediately followed by null end-tag.
```
...://www.leftyblogs.com><img src=http://www.leftyblogs.com/button.gif border=0>
```
✉

Error Line 348 column 49: required attribute "alt" not specified.

...://www.leftyblogs.com><img src=http://www.leftyblogs.com/button.gif border=0>

✉

Error Line 348 column 49: end tag for "img" omitted, but OMITTAG NO was specified.
```
...://www.leftyblogs.com><img src=http://www.leftyblogs.com/button.gif border=0>
```
✉

Info Line 348 column 34: start tag was here.

<a href=http://www.leftyblogs.com><img src=http://www.leftyblogs.com/button.gif

Error Line 348 column 92: end tag for element "a" which is not open.
```
...eftyblogs.com/button.gif border=0></a></center>
```
✉
Error Line 349 column 4: end tag for "li" omitted, but OMITTAG NO was specified.
```
</ul>
```
✉
Info Line 347 column 0: start tag was here.
```
<center>
```
Error Line 351 column 7: document type does not allow element "center" here; assuming missing "li" start-tag.
```
<center>
```
✉
Error Line 356 column 4: end tag for "li" omitted, but OMITTAG NO was specified.
```
</ul> 
```
✉
Info Line 351 column 0: start tag was here.
```
<center>
```
Error Line 358 column 7: document type does not allow element "center" here; assuming missing "li" start-tag.
```
<center>
```
✉
Error Line 360 column 4: end tag for "li" omitted, but OMITTAG NO was specified.
```
</ul>
```
✉
Info Line 358 column 0: start tag was here.
```
<center>
```
Error Line 362 column 17: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag.
```
  <li id="search">
```
✉
Error Line 371 column 4: end tag for "li" omitted, but OMITTAG NO was specified.
```
</ul>
```
✉

Info Line 337 column 1: start tag was here.

 <li id="meta"><h4>Acknowledgements:</h4>

Error Line 371 column 4: end tag for "li" omitted, but OMITTAG NO was specified.
```
</ul>
```
✉
Info Line 326 column 1: start tag was here.
```
 <li id="meta"><h4>Meta:</h4>
```
Warning Line 372 column 108: cannot generate system identifier for general entity "style".
```
...ls.php?url=http://vaprogressive.com/&style=javascript"></script > 
```
✉
Error Line 372 column 108: general entity "style" not defined and no default entity.
```
...ls.php?url=http://vaprogressive.com/&style=javascript"></script > 
```
✉
Warning Line 372 column 113: reference not terminated by REFC delimiter.
```
...p?url=http://vaprogressive.com/&style=javascript"></script > 
```
✉
Warning Line 372 column 113: reference to external entity in attribute value.
```
...p?url=http://vaprogressive.com/&style=javascript"></script > 
```
✉
Error Line 372 column 113: reference to entity "style" for which no system identifier could be generated.
```
...p?url=http://vaprogressive.com/&style=javascript"></script > 
```
✉

Info Line 372 column 107: entity was defined here.

...ils.php?url=http://vaprogressive.com/&style=javascript"></script >

Error Line 372 column 125: required attribute "type" not specified.
```
.../vaprogressive.com/&style=javascript"></script > 
```
✉
Error Line 397 column 103: document type does not allow element "script" here.
```
...unter.js?site=s24VirginiaProgressive">
```
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

✉

Markup Validation Service

This page is not Valid XHTML 1.0 Transitional!