Unrealsolutions's List: The Prius Project Site Audit

Validation Output: 22 Errors

Line 91, Column 18: document type does not allow element "style" here
type='text/css'>
✉
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).

Line 102, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…riusProject' target='_blank'><img src=http://thepriusproject.com/wp-content/pl…
✉
Line 102, Column 127: NET-enabling start-tag not immediately followed by null end-tag
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
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).

Line 102, Column 127: required attribute "alt" not specified
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
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>.

Line 102, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 102, Column 112: start tag was here
….com/ThePriusProject' target='_blank'><img src=http://thepriusproject.com/wp-c…
Line 102, Column 312: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…riusproject' target='_blank'><img src=http://thepriusproject.com/wp-content/pl…
✉
Line 102, Column 318: NET-enabling start-tag not immediately followed by null end-tag
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
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).

Line 102, Column 318: required attribute "alt" not specified
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
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>.

Line 102, Column 318: end tag for "img" omitted, but OMITTAG NO was specified
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 102, Column 303: start tag was here
….com/thepriusproject' target='_blank'><img src=http://thepriusproject.com/wp-c…
Line 102, Column 507: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…riusproject' target='_blank'><img src=http://thepriusproject.com/wp-content/pl…
✉
Line 102, Column 513: NET-enabling start-tag not immediately followed by null end-tag
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
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).

Line 102, Column 513: required attribute "alt" not specified
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
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>.

Line 102, Column 513: end tag for "img" omitted, but OMITTAG NO was specified
…oject' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 102, Column 498: start tag was here
…user/thepriusproject' target='_blank'><img src=http://thepriusproject.com/wp-c…
Line 102, Column 690: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
…ct.com/feed' target='_blank'><img src=http://thepriusproject.com/wp-content/pl…
✉
Line 102, Column 696: NET-enabling start-tag not immediately followed by null end-tag
…/feed' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
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).

Line 102, Column 696: required attribute "alt" not specified
…/feed' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
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>.

Line 102, Column 696: end tag for "img" omitted, but OMITTAG NO was specified
…/feed' target='_blank'><img src=http://thepriusproject.com/wp-content/plugins/…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 102, Column 681: start tag was here
…riusproject.com/feed' target='_blank'><img src=http://thepriusproject.com/wp-c…
Line 182, Column 329: there is no attribute "aria-required"
…uthor" name="author" type="text" value="" size="30" aria-required='true' /></p>
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 185, Column 152: there is no attribute "aria-required"
…ent" cols="45" rows="8" aria-required="true"></textarea></p> <p class="fo…
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 209, Column 23: document type does not allow element "style" here
<style type="text/css">
✉
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).

Line 322, Column 245: end tag for "a" omitted, but OMITTAG NO was specified
…tin Bergman</a> and <a href="http://www.ivegonegraphic.com">Amanda Wallace </p>
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 322, Column 187: start tag was here
…oded.com">Seth Austin Bergman</a> and <a href="http://www.ivegonegraphic.com">…
Line 507, Column 23: document type does not allow element "style" here
<style type='text/css'>img#wpstats{display:none}</style>
✉
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).