Source View: http://www.alltechbuzz.net/p/contact-us.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<head>

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

e&

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&b.performance.timin

Reference not terminated by REFC delimiter.

Line 7 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

g){var a=b.performance.timing,c=b[e].load,f=a.navigationStart,a=a.responseStart;0<

Element "f" undefined.

Line 7 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

Character "&" not allowed in attribute specification list.

Line 7 HTML Validation

f&

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&

Reference not terminated by REFC delimiter.

Line 7 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

a>=

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

f

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&(c[g]("_wtsrt",void 0,f),c[g]("wtsrt_","_wtsrt",a),c[g]("tbsd_","wtsrt_"))}try{a=null,b.chrom

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

e&

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&b.chrome.cs

Reference not terminated by REFC delimiter.

Line 7 HTML Validation

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 7 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

i

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&(a=Math.floor(b.chrome.csi().pageT),

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

c

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&0<

Element "f" undefined.

Line 7 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

Character "&" not allowed in attribute specification list.

Line 7 HTML Validation

f

Character "&" is the first character of a delimiter but occurred as data.

Line 7 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&(c[g]("_tbnd",void 0,b.chrome.csi().startE),

c[g]("tbnd_","_tbnd",f))),null==

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

a&

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&b.gtbExterna

Reference not terminated by REFC delimiter.

Line 8 HTML Validation

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

l

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&(a=b.gtbExternal.pageT()),null==

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

a&

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&b.externa

Reference not terminated by REFC delimiter.

Line 8 HTML Validation

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

l

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&(a=b.external.pageT,

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

c

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&0<

Element "f" undefined.

Line 8 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

Character "&" not allowed in attribute specification list.

Line 8 HTML Validation

f

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&(c[g]("_tbnd",void 0,b.external.startE),c[g]("tbnd_","_tbnd",f))),

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

a

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&(b[e].pt=a)}catch(l){}})();b.tickAboveFold=function(d){var a=0;if(d.offsetParent){do a+=d.offsetTop;while(d=d.offsetParent)}d=a;750>=

Character "&" is the first character of a delimiter but occurred as data.

Line 8 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

d&

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&

Reference not terminated by REFC delimiter.

Line 8 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 8 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

b[e].load[g]("aft")};var h=!1;function k(){h||(h=!0,b[e].load[g]("firstScrollTime"))}b.addEventListener?b.addEventListener("scroll",k,!1):b.attachEvent("onscroll",k);

})();</scrip

End tag for "f" omitted, but OMITTAG NO was specified.

Line 9 HTML Validation

This often occurs in XHTML on tags like IMG, LINK, META and BR when the closing / has been omitted.

End tag for "f" omitted, but OMITTAG NO was specified.

Line 9 HTML Validation

This often occurs in XHTML on tags like IMG, LINK, META and BR when the closing / has been omitted.

End tag for "f" omitted, but OMITTAG NO was specified.

Line 9 HTML Validation

This often occurs in XHTML on tags like IMG, LINK, META and BR when the closing / has been omitted.

This page has markup errors, causing screen readers to miss content.

Line 9 WCAG2 A F70

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

This page has malformed tags which IE8 and later treat differently from earlier versions of IE.

Line 9 Internet Explorer

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags means IE8 and IE9 may display different content from IE6 and IE7.

Google recommends using well-formed HTML code in your webpages. This page has mismatched tags.

Line 9 Google

Fix the critical errors listed on the Standards tab of this report. Markup errors like missing end tags or unclosed comments mean search engine web crawlers may skip important content.

t>

<title>

Contact Us

</title>

Required attribute "type" not specified.

Line 20 HTML Validation

'></script>

' />

/* Use this with templates/template-twocol.html */

#navbar,.date-header,.feed-links,.post-location,.post-share-buttons,.post-icons{

display: none !important;

}

body{

color:#111;

font-family: Lora;

font-size:16px; margin:0 auto 0;

line-height: 1.5em;

background:#FFFFFF;

background:#fff;

}

body,h1,h2,h3,h4,h5,a,p,span,img,dd{

list-style:none;

text-decoration:none;

outline:none

}

ul{

margin:5px;

text-decoration:none;

outline:none;

}

a {

color: #2361a1;

text-decoration: underline;

}

a:hover {

color: #2361a1;

text-decoration: none;

}

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 56 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 56 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 56 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 56 Firefox Internet Explorer BlackBerry

a img {

border-width: 0;

}

Use relative rather than absolute units in CSS property values.

Line 59 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

/* Header

---

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

----

Multiple comments in comment declaration.

Line 61 HTML Validation

-----

*/

#mainheader {

background-c

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 64 Firefox Internet Explorer BlackBerry

ol

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 64 Firefox Internet Explorer BlackBerry

or:

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 64 Firefox Internet Explorer BlackBerry

#004

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 64 Firefox Internet Explorer BlackBerry

489;

height:100px;

}

#header-wrapper{

width:1000px;

margin:0px auto 0px;

padding:10px 0px 10px 0px;

overflow:hidden;

}

#header-inner{

width:400px;

background-position:left;

margin-left:auto;

margin-right:auto

}

The -moz-border-radius CSS property is no longer supported in Firefox 13.

Line 78 Firefox

Use the CSS3 border-radius property instead.

Property -moz-border-radius is vendor specific.

Line 78 CSS Validation

Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.

#header{

Property -webkit-border-radius is vendor specific.

Line 79 CSS Validation

Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.

margin:0;

border:0 solid $bordercolor;

color:$pagetitlecolor;

float:left;

Use relative rather than absolute units in CSS property values.

Line 83 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

overflow:hidden;

}

.header-right {

width:550px;

float: righ

Use relative rather than absolute units in CSS property values.

Line 88 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

t;

top:0;

margin:0;

font-family: 'Lora', serif;

font-weight: 700;

font-style: italic; font-size: 18px;

text-decoration: none!important;

color: #fff;

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 95 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 95 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 95 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 95 Firefox Internet Explorer BlackBerry

}

.header-right a {

color: #fff

Use relative rather than absolute units in CSS property values.

Line 98 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

;

text-decoration: none;

}

/* Menu

---

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

----

Multiple comments in comment declaration.

Line 102 HTML Validation

-----

*/

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 103 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 103 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 103 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 103 Firefox Internet Explorer BlackBerry

.menuwidth{

width:100%;

background:#004489;

border-top:1px solid #436eaa;

border-bottom:1px solid #1d3a63;

}

.navirow{

border-top:1px solid #4C4C4C;

box-shadow:0 4px 4px -4px rgba(0,0,0,0.5);

-moz-box-shadow:0 4px 4px -4px rgba(0,0,0,0.5);

-webkit-box-shadow:0 4px 4px -4px rgba(0,0,0,0.5);

}

.navirow{

width:1000px;

margin:0 auto;

height:45px;

}

.navirow li a{

border-radius:2px;

-moz-border-radius:2px;

-webkit-border-radius:2px;

}

.navirow li.home a{

background-color:#1e3b66;

margin-right:5px;

}

.navirow li.home li a{

background-color:transparent;

}

.navirow li.active a{

font-weight:700;

color:#eaeaea;

background-color:#1e1e1e;

text-decoration:none;

text-shadow:none;

}

.navirow li.active li a{

font-weight:500;

text-decoration:none;

color:#fff;

background-color:transparent;

}

.navirow .searchbox{

float:right;

margin:6px 15px 0 0;

padding:0;

}

.navirow .searchbox input.search{

background:#fff url(http://2.bp.blogspot.com/-zfJ_tDUgohU/USSVWQvkJ4I/AAAAAAAAKCg/ijGAymZwfAI/s1600/sprite.png) no-repeat scroll -632px -10px;

border-radius:25px;

border:1px solid #004489;

color:#989898;

font-size:12px;

padding:5px 5px 5px 25px;

margin-left:10px;

margin-top:0;

width:150px;

}

Use relative rather than absolute units in CSS property values.

Line 161 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

.sf-menu,.sf-menu *{

margin:0;

padding:0;

list-style:none;

}

.sf-menu{

line-height:1.0;

}

.sf-menu ul{

position:absolute;

top:-999em;

border-top:1px solid #191919;

border-bottom:5px solid #191919;

width:10em;

}

.sf-menu ul li{

width:100%;

}

.sf-menu li:hover{

visibility:inherit;

}

Use relative rather than absolute units in CSS property values.

Line 182 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

.sf-menu li{

float:left;

position:relative;

}

.sf-menu a{

display:block;

position:relative;

}

.sf-menu li:hover ul,.sf-menu li.sfHover ul{

left:0;

top:3.0em;

z-index:99;

}

ul.sf-menu li:hover li ul,ul.sf-menu li.sfHover li ul{

top:-999em;

}

ul.sf-menu li li:hover ul,ul.sf-menu li li.sfHover ul{

left:10em;

top:0;

}

ul.sf-menu li li:hover li ul,ul.sf-menu li li.sfHover li ul{

top:-999em;

}

ul.sf-menu

Use relative rather than absolute units in CSS property values.

Line 206 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

li li li:hover ul,ul.sf-menu li li li.sfHover ul{

left:10em;

top:0;

}

.sf-menu{

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 210 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 210 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 210 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 210 Firefox Internet Explorer BlackBerry

float:left;

margin-bottom:0;

margin-top:1px;

}

.sf-menu a{

border-left:none;

border-top:none;

padding:.5em .65em;

margin:.5em

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 219 Firefox Internet Explorer BlackBerry

0;

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 219 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 219 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 219 Firefox Internet Explorer BlackBerry

text-decoration:none;

}

.sf-menu a,

Use relative rather than absolute units in CSS property values.

Line 222 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

.sf-menu a:visited{

color:#d1d4da;

}

.sf-menu li{

background:none;

font-family:"Droid Sans",Tahoma,Geneva,sans-serif;

font-size:1.00em;

font-weight:500;

text-shadow:-1px -1px #163159;

}

.sf-menu li li{

background:#2c2c2c;

border-top:1px solid #414141;

border-bottom:1px solid #191919;

font-size:.95em;

text-shadow:1px 1px #000;

}

.sf-menu li li li{

background:#9AAEDB;

}

.sf-menu li a:hover{

text-decoration:underline;

}

Use relative rather than absolute units in CSS property values.

Line 244 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

.sf-menu li li:hover{

background-color:#383838;

}

.sf-menu li:hover,.sf-menu li.sfHover,.sf-menu a:focus,.sf-menu a:hover,.sf-menu a:active{

background:none;

outline:0;

color:#fff;

}

.sf-menu a.sf-with-ul{

padding-right:1.25em;

min-width:1px;

}

.sf-sub-indicator{

position:absolute;

display:block;

right:.25em;

top:1.05em;

width:10px;

height:10px;

text-indent:-999em;

overflow:hidden;

background:url('http://2.bp.blogspot.com/-zfJ_tDUgohU/USSVWQvkJ4I/AAAAAAAAKCg/ijGAymZwfAI/s1600/sprite.png') no-repeat -8px -142px;

}

a>.sf-sub-indicator{

top:.5em;

background-position:-8px -140px;

}

a:focus>.sf-sub-indicator,a:hover>.sf-sub-indicator,a:active>.sf-sub-indicator,li:hover>a>.sf-sub-indicator,li.sfHover>a>.sf-sub-indicator{

background-position:-18px -140px;

}

.sf-menu ul .sf-sub-indicator{

background-position:-10px 0;

}

.sf-menu ul a>.sf-sub-indicator{

background-position:0 0;

}

.sf-menu ul a:focus>.sf-sub-indicator,.sf-menu ul a:hover>.sf-sub-indicator,.sf-menu ul a:active>.sf-sub-indicator,.sf-menu ul li:hover>a>.sf-

sub-indicator,.sf-menu ul li.sfHover>a>.sf-sub-indicator{

background-position:-10px 0;

}

.sf-shadow ul{

background:

Use relative rather than absolute units in CSS property values.

Line 286 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

url('../images/shadow.png') no-repeat bottom right;

padding:0 8px 9px 0;

-moz-border-radius-bottomleft:17px;

-moz-border-radius-topright:17px;

-webkit-border-top-right-radius:17px;

-webkit-border-bottom-left-radius:17px;

}

.sf-shadow ul.sf-shadow-off{

background:transparent;

}

.sf-navbar{

background:transparent;

height:2.5e

Use relative rather than absolute units in CSS property values.

Line 298 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

m;

padding-bottom:2.5em;

position:relative;

}

.sf-navbar li{

background:green;

position:static;

}

.sf-navbar a{

border-top:none;

}

.sf-navbar li ul{

width:44em;

}

.sf-navbar li li{

background:#BDD2FF;

position:relative;

}

.sf-navbar li li ul{

width:13em;

}

.sf-navbar li li li{

width:100%;

}

.sf-navbar ul li{

width:auto;

float:left;

}

.sf-navbar a,.sf-navbar a:visited{

border:none;

}

.sf-navbar li.current{

background:#BDD2FF;

}

.sf-navbar li:hover,.sf-navbar li.sfHover,.sf-navbar li li.current,.sf-navbar a:focus,.sf-navbar a:hover,.sf-navbar a:active{

background:#BDD2FF;

}

.sf-navbar ul li:hover,.sf-navbar ul li.sfHover,ul.sf-navbar ul li:hover li,ul.sf-navbar ul li.sfHover li,.sf-navbar ul a:focus,.sf-navbar ul a:hover,.sf-navbar ul a:active{

background:#D1DFFF;

}

ul.sf-navbar li li li:hover,ul.sf-navbar li li li.sfHover,.sf-navbar li li.current li.current,.sf-navbar ul li li a:focus,.sf-navbar ul li li a:hover,.sf-navbar ul li li a:active{

background:#E6EEFF;

}

ul.sf-navbar .current ul,ul.sf-navbar ul li:hover ul,ul.sf-navbar ul li.sfHover ul{

left:0;

top:2.5em;

}

ul.sf-navbar .current ul ul{

top:-999em;

}

.sf-navbar li li.current>a{

font-weight:bold;

}

.sf-navbar ul .sf-sub-indicator{

background-position:-10px -100px;

}

.sf-navbar ul a>.sf-sub-indicator{

background-position:0 -100px;

}

.sf-navbar ul a:focus>.sf-sub-indicator,.sf-navbar ul a:hover>.sf-sub-indicator,.sf-navbar ul a:active>.sf-sub-indicator,.sf-navbar ul

li:hover>a>.sf-sub-indicator,.sf-navbar ul li.sfHover>a>.sf-sub-indicator{

background-position:-10px -100px;

}

.sf-navbar>li>ul{

background:transparent;

padding:0;

-moz-border-radius-bottomleft:0;

-moz-border-radius-topright:0;

-webkit-bo

Use relative rather than absolute units in CSS property values.

Line 366 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

Use at least a 12-point font on all Web pages.

Line 366 Usability.gov 11:8

The following are all smaller than 12 point:

<p style="font-size: 11pt;" >
<p style="font-size: 11px;" >
<p style="font-size: small;" >
<font size="2" >
<font size="-1" >

For users over age 65, it may be better to use at least fourteen-point fonts. Never use less than nine-point font on a Web site.

rder-top-right-radius:0;

-webkit-border-bottom-left-radius:0;

}

/* Content

---

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

----

Multiple comments in comment declaration.

Line 370 HTML Validation

--

Invalid comment declaration: found name character outside comment but inside comment declaration.

Line 370 HTML Validation

-- */

#wrap1 {

margin: 0px auto 0;

width: 1000px;

}

#outer-wrapper {

Use relative rather than absolute units in CSS property values.

Line 375 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 375 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 375 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 375 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 375 Firefox Internet Explorer BlackBerry

background-color: #ffffff!important;

}

#content-wrapper {

background-color: #ffffff!important;

}

#main-wrapper {

float: left;

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 382 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 382 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 382 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 382 Firefox Internet Explorer BlackBerry

width: 670px;

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 383 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 383 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 383 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 383 Firefox Internet Explorer BlackBerry

margin: 0;

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 384 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 384 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 384 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 384 Firefox Internet Explorer BlackBerry

background-color: #fff!important;

}

.sidebar-wrapper {

float: right;

width: 300px;

margin: 0;

background-color: #ffffff!important;

Use relative rather than absolute units in CSS property values.

Line 391 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

}

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 392 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 392 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 392 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 392 Firefox Internet Explorer BlackBerry

/* Posts

----------------------------------------------- */

.date-header {

display:none;

margin:1.5em 0 .5em;

}

.post h1 {

The word-wrap CSS property is not supported by Firefox 3.0 and earlier.

Line 399 Firefox

text-shadow:0 1px 2px rgba(100,100,100,.35);

font-family: lora,sans-serif;

font-weight: 700;

font-size: 30px!important;

line-height: 36px!important;

margin: 0px

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 405 Firefox Internet Explorer BlackBerry

0

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 405 Firefox Internet Explorer BlackBerry

20px

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 405 Firefox Internet Explorer BlackBerry

0;

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 405 Firefox Internet Explorer BlackBerry

}

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 406 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 406 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 406 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 406 Firefox Internet Explorer BlackBerry

Use relative rather than absolute units in CSS property values.

Line 406 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

.post h1 a{

text-shadow:0 1px 2px rgba(100,100,100,.35);

color: #464646; text-decoration:none

}

.post h1 a:hover {

text-decoration: none;

color: #004489;

}

.post h3

{

background: #E3F0F2 url(http://2.bp.blogspot.com/-sj3Z6M7GRA4/UfthAoLZi_I/AAAAAAAAHDU/TDDBx1Uark4/s1600/note.png) center no-repeat;

border: 1px solid #6CC;

background-position: 7px 50%;

text-align: left;

padding: 10px 10px 10px 45px;

-moz-border-radius: 4px;

-webkit-border-radius: 4px;

}

.post h4

{

font-size: 20px;

color:#0080ff;

border-bottom:1px dotted #0080ff;

}

.post h5 {

font-size: 18px;

color:#0080ff;

border-top:1px dotted #0080ff;

border-bottom:1px dotted #0080ff;

padding:3px;

}

.post h2 {

text-shadow:0 1px 2px rgba(100,100,100,.35);

font-family: lora,sans-serif;

font-weight: 700;

font-size: 28px!important;

line-height: 36px!important;

margin: 0px 0 20px 0;

}

.post h2 a{

text-shadow:0 1px 2px rgba(100,100,100,.35);

color: #464646; text-decoration:none

}

.post h2 a:hover {

text-decoration: none;

color: #004489;

}

.post-body {

line-height: 2em;

margin-left:5px;

margin-top:12px;

font-family:Lora;

}

.post-body h2 {

font-family: 'Oswald', Helvetica, Arial!important;

font-style: normal!important;

font-weight: normal!important;

}

.post img {

border: 1px solid #d2d2d2;

}

.post blockquote {

margin:0px 0px 0px 0px;padding:10px;

background: #ffffa0;

border: 1px solid #e5e597;

}

.post{

border-bottom:1px solid #ddd;}

/* Comments

----------------------------------------------- */

#comments h4 {

font-weight:700;

line-height:1.4em;

text-transform:uppercase;

letter-spacing:.2em;

color:#333;

margin:1em 0;

}

#comments-block {

line-height:1.6em;

margin:1em 0 1.5em;

}

#comments-block .comment-body {

margin:.25em 0 0;

}

#comments-block .comment-footer {

line-height:1.4em;

text-transform:uppercase;

letter-spacing:.1em;

margin:-0.25em 0 2em;

}

#comments-block .comment-body p {

margin:0 0 .75em;

}

#comments{overflow:hidden}

#comments h4{display:inline;padding:10px;line-height:40px}

#comments h4,.comments .comment-header,.comments .comment-thread.inline-thread .comment{position:relative}

#comments h4,.comments .continue a{background:#004489}

#comments h4,.comments .user a,.comments .continue a{font-size:16px}

#comments h4,.comments .continue a{font-weight:normal;color:#fff}

#comments h4:after{content:"";position:absolute;bottom:-10px;left:10px;border-top:10px solid #004489;border-right:20px solid transparent;width:0;height:0;line-height:0}

#comments .avatar-image-container img{border:0}

.comment-thread{color:#111}

.comment-thread a{color:#777}

.comment-thread ol{margin:0 0 20px}

.comment-thread .comment-content a,.comments .user a,.comments .comment-thread.inline-thread .user a{color:#004489}

.comments .avatar-image-container,.comments .avatar-image-container img{width:48px;max-width:48px;height:48px;max-height:48px}

.comments .comment-block,.comments .comments-content .comment-replies,.comments .comment-replybox-single{margin-left:60px}

.comments .comment-block,.comments .comment-thread.inline-thread .comment{border:1px solid #ddd;background:#f9f9f9;padding:10px}

.comments .comments-content .comment{margin:15px 0 0;padding:0;width:100%;line-height:1em}

.comments .comments-content .icon.blog-author{position:absolute;top:-12px;right:-12px;margin:0;background-image: url(http://3.bp.blogspot.com/-U-Dv6Xse-VI/UA7g-c_PbhI/AAAAAAAAAxQ/al6quGVQhG4/s1600/rb+green+ribbon.gif);width:36px;height:36px}

.comments .comments-content .inline-thread{padding:0 0 0 20px}

.comments .comments-content .comment-replies{margin-top:0}

.comments .comment-content{padding:5px 0;line-height:1.4em}

.comments .comment-thread.inline-thread{border-left:1px solid #ddd;background:transparent}

.comments .comment-thread.inline-thread .comment{width:auto}

.comments .comment-thread.inline-thread .comment:after{content:"";position:absolute;top:10px;left:-20px;border-top:1px solid #ddd;width:10px;height:0px}

.comments .comment-thread.inline-thread .comment .comment-block{border:0;background:transparent;padding:0}

.comments .comment-thread.inline-thread .comment-block{margin-left:48px}

.comments .comment-thread.inline-thread .user a{font-size:13px}

.comments .comment-thread.inline-thread .avatar-image-container,.comments .comment-thread.inline-thread .avatar-image-container img{width:36px;max-width:36px;height:36px;max-height:36px}

.comments .continue{border-top:0;width:100%}

.comments .continue a{padding:10px 0;text-align:center}

.comment .continue{display:none}

#comment-editor{width:100%!important}

.comment-form{width:100%;max-width:100%}

#blog-pager-newer-link {

float:left;

}

#blog-pager-older-link {

float:right;

}

#blog-pager {

text-align:center;

}

.feed-links {

clear:both;

line-height:2.5em;

}

/* Sidebar Content

----------------------------------------------- */

.sidebar{

margin:0 0 10px 0;

font-size:13px;

color:#374142;

}

.sidebar a{

text-shadow:0 1px 2px rgba(100,100,100,.35);

text-decoration:none;

color:#374142;

}

.sidebar a:hover{

text-decoration:none;

color:#004489;

}

.sidebar h2{

text-shadow:0 1px 2px rgba(100,100,100,.35);

text-transform: uppercase;

font-family: 'Oswald', Arial, Helvetica, sans-serif;

font-size: 18px;

margin-bottom: 10px;

padding: 0 0 5px;

font-weight: normal;

line-height: 25px;

border-bottom: 5px solid #004489;

padding-bottom: 10px;

}

.sidebar ul{

list-style-type:none;

list-style:none;

margin:0px;

padding:0px;

}

.sidebar ul li{

padding:0 0 9px 0;

margin:0 0 8px 0;

}

.sidebar .widget{

margin:0 0 15px 0;

padding:0;

color:#374142;

font-size:13px;

padding-bottom: 10px;

border-bottom: 1px solid #d2d2d2;

}

.main .widget{

margin:0 0 5px;

padding:0 0 2px

}

.main .Blog{

border-bottom-width:0

}

#subscribe {

margin-top: 10px;

margin-bottom: 10px;

}

#subbutton:hover {

background-color: #292929;

border: 3px solid #292929;

}

#sidebar a img {

margin: 0;

padding: 0;

}

.sidebar .widget-content {

padding-top: 10px;

}

#subscribe {

margin-top: 10px;

margin-bottom: 10px;

}

#subbutton:hover {

background-color: #292929;

border: 3px solid #292929;

}

#subbutton {

background-color: #004489;

border: 3px solid #004489;

cursor: pointer;

color: white;

width: 48px;

height: 38px;

margin: 0px;

font-size: 14px;

font-family: 'Open Sans', sans-serif;

font-weight: 700;

margin: 0px;

float: right;

transition: all 0.3s ease-out;

}

#subbox {

height: 25px;

width: 203px;

margin: 0px;

border-bottom: 3px solid #F1F0F0;

font-size: 14px;

font-weight: 300;

font-family: 'Open Sans', sans-serif;

}

#subbox {

border: 1px solid #d2d2d2;

padding: 5px 30px 5px 10px;

width: 400px;

color: #838383;

font-style: italic;

height: 28px;

font-family: 'Lora', Arial, Helvetica, Verdana;

outline: none;

width: 198px;

margin: 0 5px 0 0;

}

/* Profile

----------------------------------------------- */

.profile-img {

float:left;

border:1px solid #ccc;

margin:0 5px 5px 0;

padding:4px;

}

.profile-data {

text-transform:uppercase;

letter-spacing:.1em;

font:normal normal 78% 'Trebuchet MS', Trebuchet, Arial, Verdana, Sans-serif;

color:#999;

font-weight:700;

line-height:1.6em;

margin:0;

}

.profile-textblock {

line-height:1.5em;

margin:0.5em 0;

}

.profile-link {

font:normal normal 78% 'Trebuchet MS', Trebuchet, Arial, Verdana, Sans-serif;

text-transform:uppercase;

letter-spacing:.1em;

}

/* Popular Posts

----------------------------------------------- */

#PopularPosts {

width:100%;

margin:0 auto;

padding:5px 0;

}

.PopularPosts .widget-content ul {

width:100%;

list-style:none;

margin:0;

padding:0;

}

.PopularPosts .widget-content li {

width:100%;

height:auto;

overflow:hidden;

list-style:none;

text-indent:0;

margin:0 5px;

}

.popularposts-img {

margin:2px;

padding:3px;

}

.item-snippet {

font-size:11px;

line-height:1.5em;

}

.bordertop {

border-top: 1px solid #d2d2d2;

margin-bottom: 30px;

}

#footer-top-wrapper { background:url(http://4.bp.blogspot.com/-zdraITTusyY/USSVVauHx_I/AAAAAAAAKCI/DKHZe_Ja2es/s1600/lower-top.png) repeat-x; height:55px; position:relative; z-index:999999;}

#footer-top { width:1000px; margin:0px auto; padding-top:20px; }

#footer-top a {font-size: 14px;font-weight: normal;line-height: 0.1px; text-decoration:none;color:#fff; text-shadow: 1px 1px 1px #000; }

#footer-top a:hover {text-decoration:underline;}

#footer-navigation li { display:block; float:left; margin-right:20px; }

#footer-navigation span { margin-right:10px; }

#backtotop { float:right; background:url(http://1.bp.blogspot.com/-ptkV4OoH2Ug/USSVU20u0AI/AAAAAAAAKCE/0gn1jiLHYo8/s1600/back-top.png) no-repeat right; padding-right:26px; }

#backtotop a, #backtotop a:hover {text-decoration:none; display:block; }

#footer-wrapper {background:url(http://1.bp.blogspot.com/-WZzEWRYEkIM/USSVVvgKCiI/AAAAAAAAKCQ/rWxNabgR0VY/s1600/lower.png) repeat; overflow:hidden; padding-bottom:20px; border-bottom:1px solid #000; position:relative; z-index:999999;}

#footer { width:1000px; margin:0 auto; padding-top:20px; color:#fff; text-shadow: 1px 1px 1px #000; }

#footer a { color:#888; text-shadow: 1px 1px 1px #000; }

#backtotop p { color:#fff; text-shadow: 1px 1px 1px #000; margin-top:0px; }

/* ----- LOWER SECTION ----- */

#lower {

margin:auto;

padding: 0px 0px 10px 0px;

width: 100%;

}

#lower a {font-family: Arial,Helvetica,Tahoma,sans-serif;font-size: 14px;font-weight: normal;

line-height: 22px;color:white; text-shadow: 1px 1px 1px #000;text-decoration:none;}

#lower a:hover {text-decoration:underline;}

#lowerbar-wrapper {

float: left;

margin: 0px 5px auto;

padding-bottom: 5px;

width: 320px;

word-wrap: break-word;

overflow: hidden;

}

.lowerbar {margin: 0; padding: 0;}

.lowerbar .widget {margin: 0;}

.lowerbar h2 {

text-shadow:0 1px 2px rgba(100,100,100,.35);

letter-spacing: 1px; color:#FFF; text-shadow: 1px 1px 1px #000; background:url(http://3.bp.blogspot.com/-vuWIMmkVbUc/USSVU-teHfI/AAAAAAAAKB8/psKGPRswq0M/s1600/footer-line.png) repeat-x bottom; padding-bottom:6px; margin-bottom:20px; font-size:15px; font-family: 'Yanone Kaffeesatz', sans-serif; text-transform: uppercase;border:0px !important; }

}

.lowerbar li {

margin-bottom:10px; background:url() no-repeat left; padding-left:16px; }

#copyightsbar a{

color: #8E8E8E;

}

#copyightsbar { clear: both; padding-top: 20px; padding-bottom: 20px; height: 60px; color: #8E8E8E; background-color: #111111; margin-bottom: -22px;} .copyrightwrap { width: 1000px; margin: 0px auto 0px; } .copyrightwrap p { float: left; width: 300px; margin: 0px; color: #d2d2d2; font-size: 12.5px; padding-top: 25px; font-family: lora,sans-serif; font-style: italic; }

}

.loader-page { margin-left: 300px; margin-top: 10px; margin-bottom: 20px; }

.ias_trigger { float: right; margin-right: 30px; font-size: 20px; font-style: italic; font-weight: bold; margin-bottom: 20px; }

ul.right li {

display: block;

float: left;

position: relative;

z-index: 5;

background-color: #292929;

padding-left: 15px;

padding-right: 15px;

padding-top: 7px;

padding-bottom: 7px;

margin-left: 10px;

}

ul.right {

margin: 0;

}

/* MBT Code For Author Box */

.about-author {

width : 98%;

overflow : hidden;

margin:10px 0px;

border:0px;

}

.about-author img {

width:70px;

padding:3px;

border:1px solid #ddd;

margin:0px 5px 0px 0px;

}

.about-author h6{

font-family: verdana !important;

font-size: 18px !important;

margin: 9px 0px !important;

color: #111 !important;

border-bottom: 2px solid #111 !important;

border-top: 0px !important;

}

.about-author p {

margin:0px;

text-align:justify;

color:#111;

}

/* Hreview Plugin */

.tth_box_right {

float: right;

margin: 0 0 10px 10px;

}

.tth_rating_container_default {

border: 1px solid #E0E0E0;

border-radius: 3px 3px 3px 3px;

font-size: 14px;

line-height: 20px;

width: 300px;

font-family: georgia;

}

#content_box #content .format_text {

color: #000000;

font-family: georgia;

}

#tth_rating {

background: none repeat scroll 0 0 #F6F6F6;

border: 2px solid white;

border-radius: 3px 3px 3px 3px;

clear: both;

overflow: hidden;

padding: 10px;

}

.tth_rating_container_default {

font-size: 14px;

line-height: 20px;

}

.tth_rating_container_default {

font-size: 14px;

line-height: 20px;

}

#tth_rating .review_screenshot {

display: block;

margin: 10px auto;

}

#tth_rating div.hr {

background: none repeat scroll 0 0 #E0E0E0;

height: 1px;

margin: 5px 0;

}

#tth_rating dd {

margin-bottom: 0 !important;

margin-left: 15px;

}

#tth_rating dt, #tth_rating dd {

float: left;

font-weight: normal;

}

.format_text dd {

margin-bottom: 1.5em;

}

.result {

text-indent: -9999px;

}

.tth_rating {

background: url("http://3.bp.blogspot.com/-wTDC4enXqzs/UIN5wgbreCI/AAAAAAAABFM/BNESOszfE-A/s320/stars.png") repeat-x scroll 0 -16px transparent;

height: 16px;

position: relative;

width: 80px;

}

.tth_rating .result {

background: url("http://3.bp.blogspot.com/-wTDC4enXqzs/UIN5wgbreCI/AAAAAAAABFM/BNESOszfE-A/s320/stars.png") repeat-x scroll 0 0 transparent;

height: 16px;

left: 0;

position: absolute;

text-indent: -9999px;

top: 0;

z-index: 102;

}

.ar_button {

background: url("http://2.bp.blogspot.com/-TqpXHM6VkoE/UIN6Ix2tGhI/AAAAAAAABFY/KaUnAb76hRM/s320/bg_button.png") repeat-x scroll center bottom #777777;

border: medium none;

border-radius: 3px 3px 3px 3px;

color: #FFFFFF !important;

cursor: pointer;

display: inline;

font-weight: bold;

padding: 5px 10px;

text-decoration: none !important;

text-shadow: 1px 1px #666666;

}

.ar_button:hover {

background-position: 0 center;

}

.ar_button:active {

background-position: 0 top;

padding: 6px 10px 4px;

position: relative;

top: 1px;

}

.ar_button.ar_red {

background-color: #E50000;

}

#tth_rating dl {

margin-top: 1px;

}

/* The three buttons sizes */

.button.big { font-size:30px;}

.button.medium { font-size:18px;}

.button.small { font-size:13px;}

/* BlueButton */

.blue.button{

color:#0f4b6d !important;

border:1px solid #84acc3 !important;

background-color: #48b5f2;

background-image: url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'),

-moz-radial-gradient( center bottom, circle,

rgba(89,208,244,1) 0,rgba(89,208,244,0) 100px),

-moz-linear-gradient(#4fbbf7, #3faeeb);

background-image: url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'),

-webkit-gradient( radial, 50% 100%, 0, 50% 100%, 100,

from(rgba(89,208,244,1)), to(rgba(89,208,244,0))),

-webkit-gradient(linear, 0% 0%, 0% 100%, from(#4fbbf7), to(#3faeeb));

}

.blue.button:hover{

background-color:#63c7fe;

background-image: url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'),

-moz-radial-gradient( center bottom, circle,

rgba(109,217,250,1) 0,rgba(109,217,250,0) 100px),

-moz-linear-gradient(#63c7fe, #58bef7);

background-image: url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'),

-webkit-gradient( radial, 50% 100%, 0, 50% 100%, 100,

from(rgba(109,217,250,1)), to(rgba(109,217,250,0))),

-webkit-gradient(linear, 0% 0%, 0% 100%, from(#63c7fe), to(#58bef7));

}

/* Green Button */

.green.button{

color:#345903 !important;

border:1px solid #96a37b !important;

background-color: #79be1e;

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -moz-radial-gradient(center bottom, circle, rgba(162,211,30,1) 0,rgba(162,211,30,0) 100px),-moz-linear-gradient(#82cc27, #74b317);

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -webkit-gradient(radial, 50% 100%, 0, 50% 100%, 100, from(rgba(162,211,30,1)), to(rgba(162,211,30,0))),-webkit-gradient(linear, 0% 0%, 0% 100%, from(#82cc27), to(#74b317));

}

.green.button:hover{

background-color:#89d228;

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -moz-radial-gradient(center bottom, circle, rgba(183,229,45,1) 0,rgba(183,229,45,0) 100px),-moz-linear-gradient(#90de31, #7fc01e);

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -webkit-gradient(radial, 50% 100%, 0, 50% 100%, 100, from(rgba(183,229,45,1)), to(rgba(183,229,45,0))),-webkit-gradient(linear, 0% 0%, 0% 100%, from(#90de31), to(#7fc01e));

}

/* Orange Button */

.orange.button{

color:#693e0a !important;

border:1px solid #bea280 !important;

background-color: #e38d27;

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -moz-radial-gradient(center bottom, circle, rgba(232,189,45,1) 0,rgba(232,189,45,0) 100px),-moz-linear-gradient(#f1982f, #d4821f);

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -webkit-gradient(radial, 50% 100%, 0, 50% 100%, 100, from(rgba(232,189,45,1)), to(rgba(232,189,45,0))),-webkit-gradient(linear, 0% 0%, 0% 100%, from(#f1982f), to(#d4821f));

}

.orange.button:hover{

background-color:#ec9732;

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -moz-radial-gradient(center bottom, circle, rgba(241,192,52,1) 0,rgba(241,192,52,0) 100px),-moz-linear-gradient(#f9a746, #e18f2b);

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -webkit-gradient(radial, 50% 100%, 0, 50% 100%, 100, from(rgba(241,192,52,1)), to(rgba(241,192,52,0))),-webkit-gradient(linear, 0% 0%, 0% 100%, from(#f9a746), to(#e18f2b));

}

/* Orange Button */

.gray.button{

color:#525252 !important;

border:1px solid #a5a5a5 !important;

background-color: #a9adb1;

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -moz-radial-gradient(center bottom, circle, rgba(197,199,202,1) 0,rgba(197,199,202,0) 100px),-moz-linear-gradient(#c5c7ca, #92989c);

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -webkit-gradient(radial, 50% 100%, 0, 50% 100%, 100, from(rgba(197,199,202,1)), to(rgba(197,199,202,0))),-webkit-gradient(linear, 0% 0%, 0% 100%, from(#c5c7ca), to(#92989c));

}

.gray.button:hover{

background-color:#b6bbc0;

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -moz-radial-gradient(center bottom, circle, rgba(202,205,208,1) 0,rgba(202,205,208,0) 100px),-moz-linear-gradient(#d1d3d6, #9fa5a9);

background-image:url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), url('https://lh6.googleusercontent.com/-4cWMlF-uqh4/TltCfL8C4DI/AAAAAAAABhE/qNaNueMVpCU/s144/button_bg.png'), -webkit-gradient(radial, 50% 100%, 0, 50% 100%, 100, from(rgba(202,205,208,1)), to(rgba(202,205,208,0))),-webkit-gradient(linear, 0% 0%, 0% 100%, from(#d1d3d6), to(#9fa5a9));

}

.mbt-textarea {

padding:0;

margin:0;

background: #fff;

width:500px;

height:50px;

color:#666;

font:12px arial;

border:1px dotted #289728; }

.mbt-textarea:hover {

color:#289728;

border:2px solid #666;

}

/*--------MBT TOC-----*/

.judul-label{

background-color:#E5ECF9;

font-weight:bold;

line-height:1.4em;

margin-bottom:5px;

overflow:hidden;

white-space:nowrap;

vertical-align: baseline;

margin: 0 2px;

outline: none;

cursor: pointer;

text-decoration: none;

font: 14px/100% Arial, Helvetica, sans-serif;

padding: .5em 2em .55em;

text-shadow: 0 1px 1px rgba(0,0,0,.3);

-webkit-border-radius: .5em;

-moz-border-radius: .5em;

border-radius: .5em;

-webkit-box-shadow: 0 1px 2px rgba(0,0,0,.2);

-moz-box-shadow: 1px 1px 4px #AAAAAA;

box-shadow: 0 1px 2px rgba(0,0,0,.2);

color: #e9e9e9;

border: 2px solid white !important;

background: #6e6e6e;

background: -webkit-gradient(linear, left top, left bottom, from(#888), to(#575757));

background: -moz-linear-gradient(top, #888, #575757);

filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#888888', endColorstr='#575757');

}

.data-list{

line-height:1.5em;

margin-left:5px;

margin-right:5px;

padding-left:15px;

padding-right:5px;

white-space:nowrap;

text-align:left;

font-family:"Arial",sans-serif;

font-size:12px;

}

.list-ganjil{

background-color:#F6F6F6;

}

.headactive{

color: #fef4e9;

border: 2px solid white !important;

background: #1C8DFF;

background: -webkit-gradient(linear, left top, left bottom, from(#9dc2e7), to(#438cd2));

background: -moz-linear-gradient(top, #9dc2e7, #438cd2);

filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#9dc2e7', endColorstr='#438cd2');

}

/*----------Guest Poster --------*/

.mbt-gp img {

margin:0;

border:0;

}

.mbt-gp-about {

font-size:15px;

margin:0 auto;

padding:3px;

width:100%;

background:#edf6ff;

border:#9ecfff dotted 1px;

min-height:130px;

}

.mbt-gp {

padding-top:10px;

margin:0;

font-size:15px;

float:left;

width:17%;

text-align:center;

border-right:#93C0F9 solid 1px;

}

.mbt-gp-text {

float:right;

width: 80%;

padding:5px;

text-align:left;

font:12px arial;

text-align:justify;

margin:0;

padding:0;

}

/* lower top wrapper

----------------------------------------------- */

#lower-top {

margin:auto;

width: 750px;

}

.post-timestamp {

margin-left: 0em;

}

.widget .post-body ul {

line-height: 2;

}

--></style>

{lang: 'en-US'} </script>

(function(){

var uid = 'ca_mrwhys_b9b30f45eb6948399a3c8ca45a664453';

if(!document.getElementById(uid))

{

var ca = document.createElement('script');

ca.id = uid;

ca.type = 'text/javascript';

ca.async = true;

ca.src = 'http' + '://' + 'cdn.crankyads.com/ca.js';

(document.getElementsByTagName('head')[0]||document.getElementsByTagName('body')[0]).appendChild(ca);

}

})();

</script>

var _gaq = _gaq || [];

_gaq.push(['_setAccount', 'UA-30565264-1']);

_gaq.push(['_trackPageview']);

(function() {

var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;

ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';

var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);

})();

</script>

var switchTo5x=true;</script>

stLight.options({publisher: "d335cc48-4c6d-477f-bcbf-e199a521a659"}); </script>

var thumbnail_mode = "no-float" ;

summary_noimg = 430;

summary_img = 500;

img_thumb_height = 150;

img_thumb_width = 180;

</script>

//<![CDATA[

function removeHtmlTag(strx,chop){

if(strx.indexOf("<")!=-1)

{

var s = strx.split("<");

for(var i=0;i<s.length;i++){

if(s[i].indexOf(">")!=-1){

s[i] = s[i].substring(s[i].indexOf(">")+1,s[i].length);

}

strx = s.join("");

}

chop = (chop < strx.length-1) ? chop : strx.length-2;

while(strx.charAt(chop-1)!=' ' && strx.indexOf(' ',chop)!=-1) chop++;

strx = strx.substring(0,chop-1);

return strx+'...';

}

function createSummaryAndThumb(pID){

var div = document.getElementById(pID);

var imgtag = "";

var img = div.getElementsByTagName("img");

var summ = summary_noimg;

if(img.length>=1) {

imgtag = '<span style="float:left; padding:0px 10px 5px 0px;"><img src="'+img[0].src+'" width="'+img_thumb_width+'px" height="'+img_thumb_height+'px"/></span>';

summ = summary_img;

}

var summary = imgtag + '<div>' + removeHtmlTag(div.innerHTML,summ) + '</div>';

div.innerHTML = summary;

}

//]]>

</script>

//<![CDATA[

$(document).ready(function() {

$('img').each(function(){

var $img = $(this);

var filename = $img.attr('src')

$img.attr('title', filename.substring((filename.lastIndexOf('/'))+1, filename.lastIndexOf('.')));

$img.attr('alt', filename.substring((filename.lastIndexOf('/'))+1, filename.lastIndexOf('.')));

});

//]]>

</script>

$(document).ready(function(){

$('a[name="more"]').before($('#MBT-google-ad').html());

$('#MBT-google-ad').html('');

});

</script>

<scrip

Required attribute "type" not specified.

Line 1173 HTML Validation

t>

(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){

(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),

m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)

})(window,document,'script','//www.google-analytics.com/analytics.js','ga');

ga('create', 'UA-42113707-1', 'alltechbuzz.net');

ga('send', 'pageview');

</script>

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1183 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1183 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&

Reference not terminated by REFC delimiter.

Line 1183 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1183 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

m=1",g="(^

Character "&" is the first character of a delimiter but occurred as data.

Line 1183 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

|&)m=",h="?",k="?m=1";function l(){var d=window.location.href,e=d.split(h);switch(e.length){case 1:return d+k;case 2:return

Character "<" is the first character of a delimiter but occurred as data.

Line 1183 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

0<=e[1].search(g)?null:d+f;default:return null}}if(-1!=a[b][c]("Mobile"

Character "&" is the first character of a delimiter but occurred as data.

Line 1183 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

)

Character "&" is the first character of a delimiter but occurred as data.

Line 1183 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&-1!=a[b][c]("WebKit"

Character "&" is the first character of a delimiter but occurred as data.

Line 1183 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

)

Character "&" is the first character of a delimiter but occurred as data.

Line 1183 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

&&-1==a[b][c]("iPad")||-1!=a[b][c]("Opera Mini")||-1!=a[b][c]("IEMobile")){var m=l();

Character "&" is the first character of a delimiter but occurred as data.

Line 1183 HTML Validation

This often occurs in text or JavaScript code when a bare angle bracket or ampersand is used instead of an entity reference.

m&

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1183 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1183 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&window.location.replac

Reference not terminated by REFC delimiter.

Line 1183 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1183 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e(m)};

</script><script type="text/javascript">

if (window.jstiming) window.jstiming.load.tick('headEnd');

</script></head>

<body>

</a>

</div>

</div></div>

</div>

<table align

There is no attribute "align".

Line 1200 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='left'>

<tr>

IMG tags must have an ALT attribute.

Line 1203 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

This link is broken. The SRC or HREF is an empty string.

Line 1203 Broken Link

HREF="" or SRC="" can cause unexpected effects such as traffic spikes or cookie corruption.

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 1203 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src=''

Required attribute "alt" not specified.

Line 1203 HTML Validation

/></a>

</td>

IMG tags must have an ALT attribute.

Line 1206 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

This link is broken. The SRC or HREF is an empty string.

Line 1206 Broken Link

HREF="" or SRC="" can cause unexpected effects such as traffic spikes or cookie corruption.

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 1206 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src=''

Required attribute "alt" not specified.

Line 1206 HTML Validation

/></a>

</td>

IMG tags must have an ALT attribute.

Line 1209 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

This link is broken. The SRC or HREF is an empty string.

Line 1209 Broken Link

HREF="" or SRC="" can cause unexpected effects such as traffic spikes or cookie corruption.

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 1209 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src=''

Required attribute "alt" not specified.

Line 1209 HTML Validation

/></a>

</td>

</tr>

</table>

</div>

</div>

Home

</a>

<ul>

<li>

About-Us

</a>

</li>

<li>

Contact-us

</a>

</li>

<li>

Advertise

</a>

</li>

<li>

Sitemap

</a>

</li>

</ul>

</li>

<li>

Make Money Online

</a>

</li>

<li>

Windows 8

</a>

</li>

<li>

Blogging

</a>

</li>

<li>

Facebook

</a>

</li>

<li>

SEO

</a>

</li>

<li>

Android

</a>

</li>

<li>

Templates

</a>

</li>

<li>

Giveaways

</a>

</li>

</ul>

</div>

<br/><cente

Element "center" undefined.

Line 1297 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

r>

<a href="http://bit.ly/15tU46s" target

There is no attribute "target".

Line 1299 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='_blank' rel='nofollow'>

IMG tags must have an ALT attribute.

Line 1299 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 1299 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src="http://4.bp.blogspot.com/-2__EH7Ykpbo/UjUZH0tEU3I/AAAAAAAAHQo/UfitDvvz6yc/s1600/Big+Idea+Mastermind.gif"

Required attribute "alt" not specified.

Line 1299 HTML Validation

/></a>

</center>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&widgetTyp

Reference not terminated by REFC delimiter.

Line 1307 HTML Validation

Reference to external entity in attribute value.

Line 1307 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&widgetI

Reference not terminated by REFC delimiter.

Line 1307 HTML Validation

Reference to external entity in attribute value.

Line 1307 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&actio

Reference not terminated by REFC delimiter.

Line 1307 HTML Validation

Reference to external entity in attribute value.

Line 1307 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&sectionI

Reference not terminated by REFC delimiter.

Line 1307 HTML Validation

Reference to external entity in attribute value.

Line 1307 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1307 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=main' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML3"));' target='configHTML3' title='Edit'>

</a>

</span>

</div><div class='widget Blog' id='Blog1'>

<div class='post hentry' itemprop

There is no attribute "itemprop".

Line 1323 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='blogPost' itemscope

There is no attribute "itemscope".

Line 1323 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='itemscope' itemtype

There is no attribute "itemtype".

Line 1323 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='http://schema.org/BlogPosting'>

There is no attribute "itemprop".

Line 1324 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='blogId'

Document type does not allow element "meta" here.

Line 1324 HTML Validation

/>

Document type does not allow element "meta" here.

Line 1325 HTML Validation

/>

Contact Us

</a>

</h2>

</span>

</div>

<div dir="ltr" style="text-align: left;" trbidi

There is no attribute "trbidi".

Line 1340 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="on">

<span style="background-color: white;">Thanks for your Interest in </span><b style="background-color: white;">All Tech Buzz</b><span style="background-color: white;">.If you have any suggestions , feedback,link exchange ,</span>

Avoid specifying a new window as the target of a link with target="_blank".

Line 1342 WCAG2 AAA F22

Displaying new windows without warning is very confusing to non-sighted users because some screen readers do not give any indication when new windows appear. If you cannot avoid displaying a new window, insert a warning into the link text like the following: "opens in a new window".

<a href="http://www.alltechbuzz.in/p/write-for-us.html" style="background-color: white;" target="_blank">Guest Post</a><span style="background-color: white;"> or

Avoid specifying a new window as the target of a link with target="_blank".

Line 1342 WCAG2 AAA F22

Displaying new windows without warning is very confusing to non-sighted users because some screen readers do not give any indication when new windows appear. If you cannot avoid displaying a new window, insert a warning into the link text like the following: "opens in a new window".

<a href="http://www.alltechbuzz.net/p/advertise-here.html" target="_blank">Advertisement offer</a>...Use the below contact form ,we will respond within 24 hours or you can mail me to </span><b style="background-color: white;">blogger.cbit@gmail.com</b><span style="background-color: white;"> .</span></div>

<h4>

<form action="http://www.emailmeform.com/builder/form/YJF3zCIfdp0HeeeaK" enctype="multipart/form-data" id="emf-form" method="post" name

There is no attribute "name".

Line 1345 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="emf-form" style="text-align: left;

Document type does not allow element "form" here; missing one of "object", "ins", "del", "map" start-tag.

Line 1345 HTML Validation

This page has markup errors, causing screen readers to miss content.

Line 1345 WCAG2 A F70

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

">

<b style="background-color: white; font-size: x-large;

Document type does not allow element "b" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag.

Line 1346 HTML Validation

This page has markup errors, causing screen readers to miss content.

Line 1346 WCAG2 A F70

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

">You can contact us using the below form</b></form>

</h4>

</div>

IFRAME tags must have alternative content.

Line 1351 Section 508 1194.22 (a)

To cater for screen readers that don't support frames, place some text in the IFRAME tag. For example: <iframe src='file.htm'>Alternative content</iframe>

No TITLE attributes found for the frames on these pages.

Line 1351 Section 508 1194.22 (i) WCAG2 A 2.4.1

Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Screen readers read out the TITLE letting the user decide which frame to visit.

<iframe frameborder

There is no attribute "frameborder".

Line 1351 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="0" height

There is no attribute "height".

Line 1351 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="524" src

There is no attribute "src".

Line 1351 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="http://www.foxyform.com/form.php?id=156439&sec_hash=2848a660b72" width

There is no attribute "width".

Line 1351 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="400

Element "iframe" undefined.

Line 1351 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

"></iframe></td></tr>

</tbody></table>

</div>

</div>

</div>

</span>

</div>

<div align

There is no attribute "align".

Line 1368 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='center' id='comment-header'>

<img class='comment-on' id='comments-norm' src='http://1.bp.blogspot.com/-9GUpWTGkgwE/Ua2qCpHNK6I/AAAAAAAAGkY/31G4-s9R-xI/s1600/comment+with+disqus.png' title='view Blogger comments'

Required attribute "alt" not specified.

Line 1369 HTML Validation

/>

IMG tags must have an ALT attribute.

Line 1369 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 1369 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src='http://lh4.googleusercontent.com/-TZUsaFaiAJM/UXVi6qJ1vjI/AAAAAAAAILk/GDdUhxz_51I/s50/bubbles.png'

Required attribute "alt" not specified.

Line 1369 HTML Validation

/><image id

There is no attribute "id".

Line 1369 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='comments-gplus' src

There is no attribute "src".

Line 1369 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='http://lh6.googleusercontent.com/-wnTb7SHAGEE/UXVi6xoHXAI/AAAAAAAAILY/6vx5Em5w8MI/s50/plus_off.png' title

There is no attribute "title".

Line 1369 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

='view Google+ comments

Element "image" undefined.

Line 1369 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

'></image>

</div><br/>

<h4>No comments:</h4>

</div>

</p>

</div>

Required attribute "type" not specified.

Line 1387 HTML Validation

'></script>

<scrip

Required attribute "type" not specified.

Line 1388 HTML Validation

t>

gapi.comments.render('gcomments', {

href: window.location,

width: '750',

first_party_property: 'BLOGGER',

view_type: 'FILTERED_POSTMOD'

});

$('#comments-norm').click(function(){

// switch to normal comments displaying

$('#gcontainer').css('display','none');

$('#comments').css('display','block');

$('#comments-norm').addClass('comment-on');

$('#comments-gplus').removeClass('comment-on');

$('#comments-norm').attr('src','http://1.bp.blogspot.com/-9GUpWTGkgwE/Ua2qCpHNK6I/AAAAAAAAGkY/31G4-s9R-xI/s1600/comment+with+disqus.png');

$('#comments-gplus').attr('src','http://lh6.googleusercontent.com/-wnTb7SHAGEE/UXVi6xoHXAI/AAAAAAAAILY/6vx5Em5w8MI/s50/plus_off.png');

});

$('#comments-gplus').click(function(){

// switch to google plus comments displaying

$('#comments').css('display','none');

$('#gcontainer').css('display','block');

$('#comments-norm').removeClass('comment-on');

$('#comments-gplus').addClass('comment-on');

$('#comments-norm').attr('src','http://4.bp.blogspot.com/-KLtnI588N5k/Ua2rhsdyCMI/AAAAAAAAGko/N7Lr1bx_SPY/s1600/comment+with+disqus.png');

$('#comments-gplus').attr('src','http://lh3.googleusercontent.com/-oNlD347wl3k/UXVi7AiBdHI/AAAAAAAAILc/NxAyb8fwEfI/s50/plus_on.png');

});

$('#comments-norm').hover(

// switch to normal comments displaying

function(){

if (!$('#comments-norm').hasClass('comment-on')){ $('#comments-norm').attr('src','http://1.bp.blogspot.com/-9GUpWTGkgwE/Ua2qCpHNK6I/AAAAAAAAGkY/31G4-s9R-xI/s1600/comment+with+disqus.png');}

}, function(){

if (!$('#comments-norm').hasClass('comment-on')){ $('#comments-norm').attr('src','http://4.bp.blogspot.com/-KLtnI588N5k/Ua2rhsdyCMI/AAAAAAAAGko/N7Lr1bx_SPY/s1600/comment+with+disqus.png');}

}

);

$('#comments-gplus').hover(

// switch to gplus comments displaying

function(){

if (!$('#comments-gplus').hasClass('comment-on')){ $('#comments-gplus').attr('src','http://lh3.googleusercontent.com/-oNlD347wl3k/UXVi7AiBdHI/AAAAAAAAILc/NxAyb8fwEfI/s50/plus_on.png');}

}, function(){

if (!$('#comments-gplus').hasClass('comment-on')){ $('#comments-gplus').attr('src','http://lh6.googleusercontent.com/-wnTb7SHAGEE/UXVi6xoHXAI/AAAAAAAAILY/6vx5Em5w8MI/s50/plus_off.png');}

}

);

</script>

<styl

Required attribute "type" not specified.

Line 1430 HTML Validation

Document type does not allow element "style" here.

Line 1430 HTML Validation

e>

#comment-zone {

position: relative;

}

#gcontainer {

display: none;

}

#comments-norm, #comments-gplus {

cursor: pointer;

padding: 0px 5px;

}

</style>

</div>

</div></div>

</div>

Home

</a>

</div>

Subscribe to:

Posts

(

Atom

)

</a>

</div>

</div><div class='widget HTML' id='HTML1'>

var disqus_shortname = 'atb2';

var disqus_blogger_current_url = "http://www.alltechbuzz.net/p/contact-us.html";

if (!disqus_blogger_current_url.length) {

disqus_blogger_current_url = "http://www.alltechbuzz.net/p/contact-us.html";

}

var disqus_blogger_homepage_url = "http://www.alltechbuzz.net/";

var disqus_blogger_canonical_homepage_url = "http://www.alltechbuzz.net/";

</script>

Document type does not allow element "style" here.

Line 1477 HTML Validation

'>

.post-comment-link { visibility: hidden; }

</style>

(function() {

var bloggerjs = document.createElement('script');

bloggerjs.type = 'text/javascript';

bloggerjs.async = true;

bloggerjs.src = 'http://'+disqus_shortname+'.disqus.com/blogger_index.js';

(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(bloggerjs);

})();

</script>

</div></div>

</div>

Search The Blog

</h2>

<cente

Element "center" undefined.

Line 1497 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

r>

<div>

This form control has no associated LABEL element.

Line 1503 WCAG2 A F68 Section 508 1194.22 (n)

Add a LABEL tag with the FOR attribute set to the ID of this control. This allows screen readers to tell the user what each control does. Do not wrap LABEL tags around input controls (implicit labels) since this is very unreliable in older screen readers.

</div>

</form>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1513 HTML Validation

Reference to external entity in attribute value.

Line 1513 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1513 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1513 HTML Validation

Reference to external entity in attribute value.

Line 1513 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1513 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML10&actio

Reference not terminated by REFC delimiter.

Line 1513 HTML Validation

Reference to external entity in attribute value.

Line 1513 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1513 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1513 HTML Validation

Reference to external entity in attribute value.

Line 1513 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1513 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML10"));' target='configHTML10' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML16'>

<script async

"async" is not a member of a group specified for any attribute.

Line 1521 HTML Validation

src="http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js

Required attribute "type" not specified.

Line 1521 HTML Validation

"></script>

<ins class="adsbygoogle"

style="display:inline-block;width:300px;height:250px"

data-ad-client

There is no attribute "data-ad-client".

Line 1525 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="ca-pub-8896493401481750"

data-ad-slot

There is no attribute "data-ad-slot".

Line 1526 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="0382480479"></ins>

<scrip

Required attribute "type" not specified.

Line 1527 HTML Validation

t>

(adsbygoogle = window.adsbygoogle || []).push({});

</script>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1534 HTML Validation

Reference to external entity in attribute value.

Line 1534 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1534 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1534 HTML Validation

Reference to external entity in attribute value.

Line 1534 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1534 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML16&actio

Reference not terminated by REFC delimiter.

Line 1534 HTML Validation

Reference to external entity in attribute value.

Line 1534 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1534 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1534 HTML Validation

Reference to external entity in attribute value.

Line 1534 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1534 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML16"));' target='configHTML16' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML2'>

There is no attribute "scrolling".

Line 1542 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="no" frameborder="0" style

There is no attribute "style".

Line 1542 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="border:none; overflow:hidden; width:292px; height:290px;" allowtransparency

There is no attribute "allowtransparency".

Line 1542 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="true

Element "iframe" undefined.

Line 1542 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

"></iframe>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1547 HTML Validation

Reference to external entity in attribute value.

Line 1547 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1547 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1547 HTML Validation

Reference to external entity in attribute value.

Line 1547 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1547 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML2&actio

Reference not terminated by REFC delimiter.

Line 1547 HTML Validation

Reference to external entity in attribute value.

Line 1547 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1547 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1547 HTML Validation

Reference to external entity in attribute value.

Line 1547 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1547 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML2"));' target='configHTML2' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML8'>

<h2 class='title'>Score our Site</h2>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1561 HTML Validation

Reference to external entity in attribute value.

Line 1561 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1561 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1561 HTML Validation

Reference to external entity in attribute value.

Line 1561 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1561 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML8&actio

Reference not terminated by REFC delimiter.

Line 1561 HTML Validation

Reference to external entity in attribute value.

Line 1561 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1561 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1561 HTML Validation

Reference to external entity in attribute value.

Line 1561 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1561 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML8"));' target='configHTML8' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML7'>

Document type does not allow element "style" here.

Line 1569 HTML Validation

">

/* PBT Style sheet for subscription box */

#pbt-subscribe-box .fb-like-box { border: 1px solid #EBEBEB; padding: 5px; background:#fff;}

Use relative rather than absolute units in CSS property values.

Line 1571 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

Use at least a 12-point font on all Web pages.

Line 1571 Usability.gov 11:8

The following are all smaller than 12 point:

<p style="font-size: 11pt;" >
<p style="font-size: 11px;" >
<p style="font-size: small;" >
<font size="2" >
<font size="-1" >

For users over age 65, it may be better to use at least fourteen-point fonts. Never use less than nine-point font on a Web site.

#pbt-subscribe-box .gplusone { background: #f7fcfc; border: 1px solid #EBEBEB; border-top: 1px solid #fff; color: #000; font-size: 10px; line-height: 1px; padding:5px;}

#pbt-subscribe-box .twitter-follow { background: #eef9f9; border: 1px solid #dff6f6; border-top: 1px solid #fff; padding:5px 11px;}

#pbt-subscribe-box .email-box {background:#e3edf4; padding:11px;}

Use relative rather than absolute units in CSS property values.

Line 1574 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

Use at least a 12-point font on all Web pages.

Line 1574 Usability.gov 11:8

The following are all smaller than 12 point:

<p style="font-size: 11pt;" >
<p style="font-size: 11px;" >
<p style="font-size: small;" >
<font size="2" >
<font size="-1" >

For users over age 65, it may be better to use at least fourteen-point fonts. Never use less than nine-point font on a Web site.

Ensure that foreground and background colors have enough contrast. The foreground/background contrast ratio is 1.94152. The ratio should be 4.5 or more, and for links this applies to both visited and unvisited styles.

Line 1575 WCAG2 AA 1.4.3

Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background.

#pbt-subscribe-box .email-box h4{color: #555;font-family: Arial;font-size: 11px; margin: 0 0 10px;}

CSS property border-radius is not supported by IE8 or earlier.

Line 1575 Internet Explorer

No rounded corners will be displayed on old versions of Internet Explorer.

Ensure that foreground and background colors have enough contrast. The foreground/background contrast ratio is 1.94152. The ratio should be 4.5 or more, and for links this applies to both visited and unvisited styles.

Line 1576 WCAG2 AA 1.4.3

Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background.

#pbt-subscribe-box .email-box .txt,#pbt-subscribe-box .email-box .txt:focus{background:#fff; float:left; color:#92c3c3; border:1px solid #E36B0A; bor

CSS property border-radius is not supported by IE8 or earlier.

Line 1576 Internet Explorer

No rounded corners will be displayed on old versions of Internet Explorer.

der-radius: 3px; padding: 7px

Use relative rather than absolute units in CSS property values.

Line 1576 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

10px 8px; width: 150px;}

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 1576 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 1576 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 1576 Firefox Internet Explorer BlackBerry

The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

Line 1576 Firefox Internet Explorer BlackBerry

#pbt-subscribe-box .email-box .btn,#pbt-subscribe-box .email-box .btn:focus{background:#E36B0A; border:1px solid #AD5513; color:#fff; border-radius: 3px; float: right; font-size: 12px; font-weight: bold; padding: 7px 8px; text-shadow: 1px 1px 0 #D08D00;}

#pbt-subscribe-box .email-box .btn:hover{background:#FF9b00;}

input, textarea {

font-family: Georgia, "Times New Roman", Times; font-size: 1em;}

#pbt-text {

background:#369;

border: 1px

The box-shadow CSS property is not supported in Internet Explorer 8 and Safari 5.0 or earlier.

Line 1584 Internet Explorer Safari

Boxes will display without a shadow in old versions of Internet Explorer and Safari.

so

The box-shadow CSS property is not supported in Internet Explorer 8 and Safari 5.0 or earlier.

Line 1584 Internet Explorer Safari

Boxes will display without a shadow in old versions of Internet Explorer and Safari.

li

The box-shadow CSS property is not supported in Internet Explorer 8 and Safari 5.0 or earlier.

Line 1584 Internet Explorer Safari

Boxes will display without a shadow in old versions of Internet Explorer and Safari.

d #CCC;

box-shadow: 0 0 5px

#EEE;

line-height: 10px;

margin: 10px 10px 15px 0;

padding: 10px;

width:280px;

}

#pbt-text h3 {

color:white;

border-bottom: 1px dotted

white;

line-height

Use relative rather than absolute units in CSS property values.

Line 1596 WCAG2 AA 1.4.4

Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual. This usually causes problems with pixel based layouts, which also perform badly on handheld and widescreen displays. Percentage values "stretch" according to screen size and work on a large range of display sizes.

:1.385em;

font-size: 18px;

padding: 0;

margin: 0 0 10px;

border-bottom: 1px dotted

#AAA;

Property font-wieght doesn't exist in the CSS 2.1 or CSS 3 recommendations.

Line 1601 CSS Validation

The property name may be mis-spelled, vendor specific, or a CSS 3 property which has not yet reached recommendation status.

font-wieght: bold;

text-transform: uppercase;

letter-spacing: 0;

}

</style>

<h4>Subscribe FREE updates on your

Avoid specifying a new window as the target of a link with target="_blank".

Line 1611 WCAG2 AAA F22

Displaying new windows without warning is very confusing to non-sighted users because some screen readers do not give any indication when new windows appear. If you cannot avoid displaying a new window, insert a warning into the link text like the following: "opens in a new window".

<a href="http://feedburner.google.com/fb/a/mailverify?uri=All-Tech-Buzz" rel="nofollow" target="_blank">Email</a> |

Avoid specifying a new window as the target of a link with target="_blank".

Line 1611 WCAG2 AAA F22

Displaying new windows without warning is very confusing to non-sighted users because some screen readers do not give any indication when new windows appear. If you cannot avoid displaying a new window, insert a warning into the link text like the following: "opens in a new window".

<form onsubmit="window.open('http://feedburner.google.com/fb/a/mailverify?uri=all-tech-buzz', 'popupwindow',

'scrollbars=yes,width=700px,height=700px');return true" target

There is no attribute "target".

Line 1613 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="popupwindow" method="post" action="http://feedburner.google.com/fb/a/mailverify">

<input name="email" onblur="if (this.value == '') {this.value = 'Enter your email address';}" onfocus="if (this.value == 'Enter your email address')

{this.value = '';}" value="Enter your email address" class="txt"

Document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag.

Line 1615 HTML Validation

This page has markup errors, causing screen readers to miss content.

Line 1615 WCAG2 A F70

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

/>

<input type="hidden" name="uri" value="All-Tech-Buzz"

Document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag.

Line 1616 HTML Validation

/>

<input type="hidden" value="en_US" name="loc"

Document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag.

Line 1617 HTML Validation

/>

<input type="submit" value="Subscribe" class="btn"

Document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag.

Line 1618 HTML Validation

/>

</form>

</div>

IFRAME tags must have alternative content.

Line 1627 Section 508 1194.22 (a)

To cater for screen readers that don't support frames, place some text in the IFRAME tag. For example: <iframe src='file.htm'>Alternative content</iframe>

No TITLE attributes found for the frames on these pages.

Line 1627 Section 508 1194.22 (i) WCAG2 A 2.4.1

Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Screen readers read out the TITLE letting the user decide which frame to visit.

Element "iframe" undefined.

Line 1627 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

/></ifram

End tag for element "iframe" which is not open.

Line 1627 HTML Validation

This page has markup errors, causing screen readers to miss content.

Line 1627 WCAG2 A F70

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

This page has malformed tags which IE8 and later treat differently from earlier versions of IE.

Line 1627 Internet Explorer

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags means IE8 and IE9 may display different content from IE6 and IE7.

Google recommends using well-formed HTML code in your webpages. This page has mismatched tags.

Line 1627 Google

Fix the critical errors listed on the Standards tab of this report. Markup errors like missing end tags or unclosed comments mean search engine web crawlers may skip important content.

e>

<a href="http://www.facebook.com/pages/ALL-TECH-BUZZ/174308785976839" target="_blank" rel="nofollow" style="color: #3B5998; font-family: arial; font-size: 15px; font-weight: bold; line-height: 20px;"> Like us on Facebook </a><div class="clear"></div>

</div>

<g:plusone href

There is no attribute "href".

Line 1633 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="http://www.alltechbuzz.in

Element "g:plusone" undefined.

Line 1633 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

"></g:plusone>

</div>

<a href="https://plus.google.com/103952868650172942518/posts" target="_blank" rel="nofollow" style="color: #d00; font-family: arial; font-size: 17px; font-weight: bold; line-height: 24px;">Circle us on Google+</a><div class="clear"></div>

</div>

</div></div></div>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1642 HTML Validation

Reference to external entity in attribute value.

Line 1642 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1642 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1642 HTML Validation

Reference to external entity in attribute value.

Line 1642 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1642 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML7&actio

Reference not terminated by REFC delimiter.

Line 1642 HTML Validation

Reference to external entity in attribute value.

Line 1642 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1642 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1642 HTML Validation

Reference to external entity in attribute value.

Line 1642 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1642 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML7"));' target='configHTML7' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML12'>

There is no attribute "marginheight".

Line 1650 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="0" marginwidth

There is no attribute "marginwidth".

Line 1650 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="0" topmargin

There is no attribute "topmargin".

Line 1650 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="0" leftmargin

There is no attribute "leftmargin".

Line 1650 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="0" width="300" height="250" src="http://this.content.served.by.adshuffle.com/p/kl/46/799/r/12/4/8/ast0k3n/cj_K_lW0d49sycr2pdnBTRylsVQXUAOw/view.html?[Place Your Cache Buster ID here]

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1650 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1650 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&ASTPC

Reference not terminated by REFC delimiter.

Line 1650 HTML Validation

Reference to external entity in attribute value.

Line 1650 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1650 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

T=[Place Your Click Tracking URL Here]

Element "iframe" undefined.

Line 1650 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

"></iframe>

Document type does not allow element "link" here.

Line 1651 HTML Validation

/>

<script language

There is no attribute "language".

Line 1652 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="javascript" src="http://cache.blogads.com/142575302/feed.js

Required attribute "type" not specified.

Line 1652 HTML Validation

"></script>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1657 HTML Validation

Reference to external entity in attribute value.

Line 1657 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1657 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1657 HTML Validation

Reference to external entity in attribute value.

Line 1657 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1657 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML12&actio

Reference not terminated by REFC delimiter.

Line 1657 HTML Validation

Reference to external entity in attribute value.

Line 1657 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1657 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1657 HTML Validation

Reference to external entity in attribute value.

Line 1657 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1657 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML12"));' target='configHTML12' title='Edit'>

</a>

</span>

</div>

IMG tags must have an ALT attribute.

Line 1666 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 1666 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src="http://3.bp.blogspot.com/-Wfn28wX2tUc/UidFaY5hSgI/AAAAAAAAHMs/s-HiPQnIZUQ/s1600/High+Traffic+Academy.gif"

Required attribute "alt" not specified.

Line 1666 HTML Validation

/></a>

Document type does not allow element "link" here.

Line 1668 HTML Validation

/>

Required attribute "type" not specified.

Line 1669 HTML Validation

"></script>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1674 HTML Validation

Reference to external entity in attribute value.

Line 1674 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1674 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1674 HTML Validation

Reference to external entity in attribute value.

Line 1674 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1674 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML15&actio

Reference not terminated by REFC delimiter.

Line 1674 HTML Validation

Reference to external entity in attribute value.

Line 1674 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1674 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1674 HTML Validation

Reference to external entity in attribute value.

Line 1674 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1674 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML15"));' target='configHTML15' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML6'>

<h2 class='title'>Premium Advertisers</h2>

<cente

Element "center" undefined.

Line 1683 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

r><link rel="stylesheet" type="text/css" href="http://cache.blogads.com/473941517/feed.css" />

Required attribute "type" not specified.

Line 1684 HTML Validation

"></script></center>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1689 HTML Validation

Reference to external entity in attribute value.

Line 1689 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1689 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1689 HTML Validation

Reference to external entity in attribute value.

Line 1689 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1689 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML6&actio

Reference not terminated by REFC delimiter.

Line 1689 HTML Validation

Reference to external entity in attribute value.

Line 1689 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1689 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1689 HTML Validation

Reference to external entity in attribute value.

Line 1689 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1689 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML6"));' target='configHTML6' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML9'>

<h2 class='title'>Quick Deals</h2>

<td> <cente

Element "center" undefined.

Line 1700 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

r>

Avoid specifying a new window as the target of a link with target="_blank".

Line 1700 WCAG2 AAA F22

Displaying new windows without warning is very confusing to non-sighted users because some screen readers do not give any indication when new windows appear. If you cannot avoid displaying a new window, insert a warning into the link text like the following: "opens in a new window".

Each A tag must contain text or an IMG with an ALT tag.

Line 1700 WCAG2 A F89

Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT tag is blank, screen readers have nothing to read, so read out the URL instead.

IMG tags must have an ALT attribute.

Line 1700 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 1700 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src="http://4.bp.blogspot.com/-55Ab5tsP2U4/Uh38UMAi8jI/AAAAAAAAHLQ/tRuUJQW3Mu0/s1600/Hostgator-Hosting-with-1-Penny.gif"

Required attribute "alt" not specified.

Line 1700 HTML Validation

/></a> </center> </td>

<td> <cente

Element "center" undefined.

Line 1702 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

r>

Avoid specifying a new window as the target of a link with target="_blank".

Line 1702 WCAG2 AAA F22

Displaying new windows without warning is very confusing to non-sighted users because some screen readers do not give any indication when new windows appear. If you cannot avoid displaying a new window, insert a warning into the link text like the following: "opens in a new window".

Each A tag must contain text or an IMG with an ALT tag.

Line 1702 WCAG2 A F89

Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT tag is blank, screen readers have nothing to read, so read out the URL instead.

IMG tags must have an ALT attribute.

Line 1702 Section 508 1194.22 (a) WCAG2 A F65

Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.

Line 1702 Usability.gov 14:3

This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src="http://3.bp.blogspot.com/-Gvs_yMieo9g/UiCpikYbjFI/AAAAAAAAHL0/i0CVEoFvAyc/s1600/Powerful+web+hosting.gif"

Required attribute "alt" not specified.

Line 1702 HTML Validation

/></a>

</center>

</td> </tr>

<cente

Element "center" undefined.

Line 1706 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

r>

<td> <cente

Element "center" undefined.

Line 1709 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

r> </center> </td> </center></td></tr> </tbody> </table>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1714 HTML Validation

Reference to external entity in attribute value.

Line 1714 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1714 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1714 HTML Validation

Reference to external entity in attribute value.

Line 1714 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1714 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML9&actio

Reference not terminated by REFC delimiter.

Line 1714 HTML Validation

Reference to external entity in attribute value.

Line 1714 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1714 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1714 HTML Validation

Reference to external entity in attribute value.

Line 1714 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1714 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML9"));' target='configHTML9' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML5'>

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&appI

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=252086268166345

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&border_colo

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

r=%23ececec

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&fon

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

t=tahoma

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&heade

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

r=true

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&heigh

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

t=600

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&linktarge

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

t=_blank

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&local

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=en_US

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&sit

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=http%3A%2F%2Fwww.alltechbuzz.net

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

&widt

Reference not terminated by REFC delimiter.

Line 1722 HTML Validation

Reference to external entity in attribute value.

Line 1722 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1722 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

h=300

Element "iframe" undefined.

Line 1722 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

"></iframe>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1727 HTML Validation

Reference to external entity in attribute value.

Line 1727 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1727 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1727 HTML Validation

Reference to external entity in attribute value.

Line 1727 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1727 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML5&actio

Reference not terminated by REFC delimiter.

Line 1727 HTML Validation

Reference to external entity in attribute value.

Line 1727 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1727 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1727 HTML Validation

Reference to external entity in attribute value.

Line 1727 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1727 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML5"));' target='configHTML5' title='Edit'>

</a>

</span>

</div><div class='widget HTML' id='HTML11'>

<h2 class='title'>Connect with me on Youtube</h2>

IFRAME tags must have alternative content.

Line 1736 Section 508 1194.22 (a)

To cater for screen readers that don't support frames, place some text in the IFRAME tag. For example: <iframe src='file.htm'>Alternative content</iframe>

No TITLE attributes found for the frames on these pages.

Line 1736 Section 508 1194.22 (i) WCAG2 A 2.4.1

Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Screen readers read out the TITLE letting the user decide which frame to visit.

There is no attribute "id".

Line 1736 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="fr" scrolling="no" src="http://www.youtube.com/subscribe_widget?p=imran1276" style="border: 0px; height: 104px; background:#FFF; overflow-x: hidden; overflow-y: hidden; width: 300px;

Element "iframe" undefined.

Line 1736 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

"></iframe>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1741 HTML Validation

Reference to external entity in attribute value.

Line 1741 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1741 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1741 HTML Validation

Reference to external entity in attribute value.

Line 1741 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1741 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML11&actio

Reference not terminated by REFC delimiter.

Line 1741 HTML Validation

Reference to external entity in attribute value.

Line 1741 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1741 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1741 HTML Validation

Reference to external entity in attribute value.

Line 1741 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1741 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML11"));' target='configHTML11' title='Edit'>

</a>

</span>

</div><div class='widget Label' id='Label1'>

<h2>Choose Your Category</h2>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/Adsense'>Adsense</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/AFFILIATE-MARKETING'>AFFILIATE-MARKETING</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/ALEXA'>ALEXA</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/ANDROID'>ANDROID</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/ANTIVIRUS-SOFTWARES'>ANTIVIRUS-SOFTWARES</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/APPLE'>APPLE</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/BLOGGING'>BLOGGING</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/CLOUD-COMPUTING'>CLOUD-COMPUTING</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/COMPUTER-TRICKS'>COMPUTER-TRICKS</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/DESIGN'>DESIGN</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/EDUCATION'>EDUCATION</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/FACEBOOK'>FACEBOOK</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/GADGETS'>GADGETS</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/GAMES'>GAMES</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/GIVEAWAY'>GIVEAWAY</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/Gmail'>Gmail</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/GOOGLE-CHROME'>GOOGLE-CHROME</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/GOOGLE-SEO'>GOOGLE-SEO</a>

</span>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/Income-Report'>Income-Report</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/Inspiration'>Inspiration</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/IPHONE'>IPHONE</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/LAPTOPS'>LAPTOPS</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/MAKE-MONEY-ONLINE'>MAKE-MONEY-ONLINE</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/MICROSOFT'>MICROSOFT</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/MOBILE-TRICKS'>MOBILE-TRICKS</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/MUSIC'>MUSIC</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/PHOTO-VIDEO-EDITING'>PHOTO-VIDEO-EDITING</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/Pinterest'>Pinterest</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/SOFTWARES'>SOFTWARES</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/SYSTEM-SECURITY'>SYSTEM-SECURITY</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/TECH-UPDATES'>TECH-UPDATES</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/TEMPLATES'>TEMPLATES</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/TOOLS'>TOOLS</a>

</span>

</span>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/TORRENT-TRICKS'>TORRENT-TRICKS</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/WEBHOSTING'>WEBHOSTING</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/WIDGETS'>WIDGETS</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/WINDOWS'>WINDOWS</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/WINDOWS-8'>WINDOWS-8</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/WORDPRESS'>WORDPRESS</a>

</span>

<a dir='ltr' href='http://www.alltechbuzz.net/search/label/YOUTUBE'>YOUTUBE</a>

</span>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1882 HTML Validation

Reference to external entity in attribute value.

Line 1882 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1882 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=Label&widgetI

Reference not terminated by REFC delimiter.

Line 1882 HTML Validation

Reference to external entity in attribute value.

Line 1882 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1882 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=Label1&actio

Reference not terminated by REFC delimiter.

Line 1882 HTML Validation

Reference to external entity in attribute value.

Line 1882 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1882 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1882 HTML Validation

Reference to external entity in attribute value.

Line 1882 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1882 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=sidebar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("Label1"));' target='configLabel1' title='Edit'>

</a>

</span>

</div>

</div></div>

</div>

</div>

</div>

Document type does not allow element "link" here.

Line 1906 HTML Validation

/>

Required attribute "type" not specified.

Line 1907 HTML Validation

"></script>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1912 HTML Validation

Reference to external entity in attribute value.

Line 1912 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1912 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1912 HTML Validation

Reference to external entity in attribute value.

Line 1912 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1912 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML14&actio

Reference not terminated by REFC delimiter.

Line 1912 HTML Validation

Reference to external entity in attribute value.

Line 1912 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1912 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1912 HTML Validation

Reference to external entity in attribute value.

Line 1912 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1912 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=lower-topbar1' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML14"));' target='configHTML14' title='Edit'>

</a>

</span>

</div></div>

</div>

<l

Document type does not allow element "li" here; missing one of "ul", "ol" start-tag.

Line 1924 HTML Validation

This page has markup errors, causing screen readers to miss content.

Line 1924 WCAG2 A F70

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

i>

Home

</a>

</li>

<l

Document type does not allow element "li" here; missing one of "ul", "ol" start-tag.

Line 1929 HTML Validation

i>

About-us

</a>

</li>

<l

Document type does not allow element "li" here; missing one of "ul", "ol" start-tag.

Line 1934 HTML Validation

i>

Privacy Policy

</a>

</li>

<l

Document type does not allow element "li" here; missing one of "ul", "ol" start-tag.

Line 1939 HTML Validation

i>

Contact-us

</a>

</li>

<l

Document type does not allow element "li" here; missing one of "ul", "ol" start-tag.

Line 1944 HTML Validation

i>

Services

</a>

</li>

<l

Document type does not allow element "li" here; missing one of "ul", "ol" start-tag.

Line 1949 HTML Validation

i>

Advertise on this Blog

</a>

</li>

</div>

Back to top

</a>

</p>

</div>

</div>

About All Tech Buzz

</h2>

<p>Alltechbuzz.NET is a Tech Blog dedicated for <font color

There is no attribute "color".

Line 1975 HTML Validation

This happens when the version of HTML used on this page doesn't support an attribute with this name. This can happen if the attribute is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 attributes and Strict DOCTYPEs don't allow stylistic attributes which were present in earlier versions of HTML.

="sky blue

Element "font" undefined.

Line 1975 HTML Validation

This happens when the version of HTML used on this page doesn't support an element with this name. This can happen if the element is misspelled, is uppercase or mixed case in XHTML, or isn't supported by some HTML versions. For example, HTML 4 DOCTYPEs don't allow HTML 5 element and Strict DOCTYPEs don't allow stylistic elements and frames which were present in earlier versions of HTML.

">Tech Geeks and Bloggers</font>.

<

Document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag.

Line 1976 HTML Validation

This page has markup errors, causing screen readers to miss content.

Line 1976 WCAG2 A F70

Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

p>We constantly publish Tips Tricks and Tutorials related to Blogging , Design,Software,Social Media,New Services and Much More related to Latest Technologies...</p>

<

Document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag.

Line 1977 HTML Validation

p>Visit Our <a href='http://www.alltechbuzz.net/p/about-us.html'>About Us Page</a></p></p>

</div>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 1982 HTML Validation

Reference to external entity in attribute value.

Line 1982 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1982 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=HTML&widgetI

Reference not terminated by REFC delimiter.

Line 1982 HTML Validation

Reference to external entity in attribute value.

Line 1982 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1982 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=HTML4&actio

Reference not terminated by REFC delimiter.

Line 1982 HTML Validation

Reference to external entity in attribute value.

Line 1982 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1982 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 1982 HTML Validation

Reference to external entity in attribute value.

Line 1982 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 1982 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=lowerbar1' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML4"));' target='configHTML4' title='Edit'>

</a>

</span>

</div></div>

</div>

<div id=

ID "lowerbar-wrapper" already defined.

Line 1990 HTML Validation

This page has duplicate IDs which cause problems in screen readers.

Line 1990 WCAG2 A F77

Two or more tags on this page share the same ID. Change the ID so it is unique for each tag.

'lowerbar-wrapper'>

<h2>Quick Navigation</h2>

<ul>

<li><a href='http://www.alltechbuzz.net/p/write-for-us_16.html'>Submit A Guest Post</a></li>

<li><a href='http://www.alltechbuzz.net/p/contact-us.html'>Contact Us</a></li>

<li><a href='http://www.alltechbuzz.net/p/about-us.html'>Read About Us</a></li>

</ul>

<a class='quickedit' href='//www.blogger.com/rearrange?blogID=5302457754201593493&widgetTyp

Reference not terminated by REFC delimiter.

Line 2002 HTML Validation

Reference to external entity in attribute value.

Line 2002 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 2002 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

e=LinkList&widgetI

Reference not terminated by REFC delimiter.

Line 2002 HTML Validation

Reference to external entity in attribute value.

Line 2002 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 2002 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=LinkList3&actio

Reference not terminated by REFC delimiter.

Line 2002 HTML Validation

Reference to external entity in attribute value.

Line 2002 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 2002 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

n=editWidget&sectionI

Reference not terminated by REFC delimiter.

Line 2002 HTML Validation

Reference to external entity in attribute value.

Line 2002 HTML Validation

An unknown entity has been used. This often happens when &param=value is used instead of &param=value in URL query strings.

Line 2002 HTML Validation Ampersand Problem

In HTML the ampersand character (&) is reserved for marking character entities so you should never use raw ampersands in HTML - including ampersands inside URLs. For example, any URL that needs an ampersand should look like: http://www.example.com/file.html?var1=val1&var2=val2&var3=val3

d=lowerbar2' onclick='return _WidgetManager._PopupConfig(document.getElementById("LinkList3"));' target='configLinkList3' title='Edit'>

</a>

</span>

</div>

</div><div class='widget LinkList' id='LinkList2'>

<h2>

URL:	http://www.alltechbuzz.net/p/contact-us.html
HTTP Status:	200 OK
MIME Type:	text/html
Last Modified:	Wed, 18 Sep 2013 12:43:10 GMT
Download Time:	Less than a second
Cookies:	None
Size:	90 KB
Page Weight:	106 KB (total size of HTML, CSS, JavaScript and images)
Depth:	1 clicks from home page
Charset:	UTF-8
Forms:	4 forms containing 13 controls
HTTP Headers:	8 headers Alternate-Protocol: 80:quic,80:quic Cache-Control: private, max-age=0 Date: Wed, 18 Sep 2013 15:15:20 GMT Server: GSE Transfer-Encoding: chunked X-Content-Type-Options: nosniff X-Robots-Tag: nofollow,noindex,noodp X-XSS-Protection: 1; mode=block
Links In:	1 pages http://www.alltechbuzz.net/
Links Out:	85 links http://www.alltechbuzz.net/p/about-us.html http://www.alltechbuzz.net/p/advertise-on-technology-blog.html http://www.alltechbuzz.net/p/blog-archive.html http://www.alltechbuzz.net/search/label/MAKE%20MONEY%20ONLINE http://www.alltechbuzz.net/search/label/WINDOWS%208 http://www.alltechbuzz.net/search/label/BLOGGING http://www.alltechbuzz.net/search/label/FACEBOOK http://www.alltechbuzz.net/search/label/GOOGLE%2FSEO http://www.alltechbuzz.net/search/label/ANDROID http://www.alltechbuzz.net/search/label/TEMPLATES http://www.alltechbuzz.net/search/label/GIVEAWAY http://bit.ly/15tU46s http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main http://www.alltechbuzz.in/p/write-for-us.html http://www.alltechbuzz.net/p/advertise-here.html http://www.alltechbuzz.net/feeds/posts/default http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML10&action=editWidget&sectionId=sidebar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML16&action=editWidget&sectionId=sidebar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=sidebar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sidebar2 http://feedburner.google.com/fb/a/mailverify?uri=All-Tech-Buzz http://feeds.feedburner.com/All-Tech-Buzz http://www.facebook.com/pages/ALL-TECH-BUZZ/174308785976839 https://plus.google.com/103952868650172942518/posts http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sidebar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=sidebar2 http://tracker.hightrafficacademy.com/track.php?id=23171 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML15&action=editWidget&sectionId=sidebar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=sidebar2 http://bit.ly/11iz9n1 http://bit.ly/17Hivz6 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML9&action=editWidget&sectionId=sidebar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=sidebar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=sidebar2 http://www.alltechbuzz.net/search/label/Adsense http://www.alltechbuzz.net/search/label/AFFILIATE-MARKETING http://www.alltechbuzz.net/search/label/ALEXA http://www.alltechbuzz.net/search/label/ANTIVIRUS-SOFTWARES http://www.alltechbuzz.net/search/label/APPLE http://www.alltechbuzz.net/search/label/CLOUD-COMPUTING http://www.alltechbuzz.net/search/label/COMPUTER-TRICKS http://www.alltechbuzz.net/search/label/DESIGN http://www.alltechbuzz.net/search/label/EDUCATION http://www.alltechbuzz.net/search/label/GADGETS http://www.alltechbuzz.net/search/label/GAMES http://www.alltechbuzz.net/search/label/Gmail http://www.alltechbuzz.net/search/label/GOOGLE-CHROME http://www.alltechbuzz.net/search/label/GOOGLE-SEO http://www.alltechbuzz.net/search/label/HOW-TO http://www.alltechbuzz.net/search/label/Income-Report http://www.alltechbuzz.net/search/label/Inspiration http://www.alltechbuzz.net/search/label/IPHONE http://www.alltechbuzz.net/search/label/LAPTOPS http://www.alltechbuzz.net/search/label/MAKE-MONEY-ONLINE http://www.alltechbuzz.net/search/label/MICROSOFT http://www.alltechbuzz.net/search/label/MOBILE-TRICKS http://www.alltechbuzz.net/search/label/MUSIC http://www.alltechbuzz.net/search/label/PHOTO-VIDEO-EDITING http://www.alltechbuzz.net/search/label/Pinterest http://www.alltechbuzz.net/search/label/SOFTWARES http://www.alltechbuzz.net/search/label/SYSTEM-SECURITY http://www.alltechbuzz.net/search/label/TECH-UPDATES http://www.alltechbuzz.net/search/label/TOOLS http://www.alltechbuzz.net/search/label/Top%2010 http://www.alltechbuzz.net/search/label/TOP%205 http://www.alltechbuzz.net/search/label/TORRENT-TRICKS http://www.alltechbuzz.net/search/label/WEBHOSTING http://www.alltechbuzz.net/search/label/WIDGETS http://www.alltechbuzz.net/search/label/WINDOWS http://www.alltechbuzz.net/search/label/WINDOWS-8 http://www.alltechbuzz.net/search/label/WORDPRESS http://www.alltechbuzz.net/search/label/YOUTUBE http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML14&action=editWidget&sectionId=lower-topbar1 http://www.alltechbuzz.net/p/privacy-policy.html http://www.alltechbuzz.net/p/services.html http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=lowerbar1 http://www.alltechbuzz.net/p/write-for-us_16.html http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=LinkList&widgetId=LinkList3&action=editWidget&sectionId=lowerbar2 http://www.alltechbuzz.net/2012/06/how-to-increase-alexa-rank.html http://www.alltechbuzz.net/2012/01/10-best-ways-to-make-money-online.html http://www.alltechbuzz.net/2013/05/best-facebook-tips-tricks.html http://www.alltechbuzz.net/2013/05/download-whatsapp-for-pc.html http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=LinkList&widgetId=LinkList2&action=editWidget&sectionId=lowerbar2 http://www.blogger.com/rearrange?blogID=5302457754201593493&widgetType=ContactForm&widgetId=ContactForm1&action=editWidget&sectionId=lowerbar3
Images:	16 images http://www.alltechbuzz.net/p/'+img[0].src+' NaN KB http://2.bp.blogspot.com/-soelk1Usu5c/UcN3_TMbc7I/AAAAAAAAGzc/nliVApJP7SA/s1600/All-Tech-Buzz.png 16 KB http://www.alltechbuzz.net/p/contact-us.html 106 KB http://4.bp.blogspot.com/-2__EH7Ykpbo/UjUZH0tEU3I/AAAAAAAAHQo/UfitDvvz6yc/s1600/Big+Idea+Mastermind.gif NaN KB http://img1.blogblog.com/img/icon18_wrench_allbkg.png NaN KB http://1.bp.blogspot.com/-9GUpWTGkgwE/Ua2qCpHNK6I/AAAAAAAAGkY/31G4-s9R-xI/s1600/comment+with+disqus.png NaN KB http://lh4.googleusercontent.com/-TZUsaFaiAJM/UXVi6qJ1vjI/AAAAAAAAILk/GDdUhxz_51I/s50/bubbles.png NaN KB http://3.bp.blogspot.com/-Wfn28wX2tUc/UidFaY5hSgI/AAAAAAAAHMs/s-HiPQnIZUQ/s1600/High+Traffic+Academy.gif NaN KB http://4.bp.blogspot.com/-55Ab5tsP2U4/Uh38UMAi8jI/AAAAAAAAHLQ/tRuUJQW3Mu0/s1600/Hostgator-Hosting-with-1-Penny.gif NaN KB http://3.bp.blogspot.com/-Gvs_yMieo9g/UiCpikYbjFI/AAAAAAAAHL0/i0CVEoFvAyc/s1600/Powerful+web+hosting.gif NaN KB http://2.bp.blogspot.com/-sj3Z6M7GRA4/UfthAoLZi_I/AAAAAAAAHDU/TDDBx1Uark4/s1600/note.png NaN KB http://3.bp.blogspot.com/-U-Dv6Xse-VI/UA7g-c_PbhI/AAAAAAAAAxQ/al6quGVQhG4/s1600/rb+green+ribbon.gif NaN KB http://4.bp.blogspot.com/-zdraITTusyY/USSVVauHx_I/AAAAAAAAKCI/DKHZe_Ja2es/s1600/lower-top.png NaN KB http://1.bp.blogspot.com/-ptkV4OoH2Ug/USSVU20u0AI/AAAAAAAAKCE/0gn1jiLHYo8/s1600/back-top.png NaN KB http://1.bp.blogspot.com/-WZzEWRYEkIM/USSVVvgKCiI/AAAAAAAAKCQ/rWxNabgR0VY/s1600/lower.png NaN KB http://3.bp.blogspot.com/-vuWIMmkVbUc/USSVU-teHfI/AAAAAAAAKB8/psKGPRswq0M/s1600/footer-line.png NaN KB
CSS:	0 files
JavaScript:	0 files

Issues:	93 issues found on 697 lines

HTML Document