

A well-written description tag attracts more clicks in search results than
an irrelevant or missing description.

No spelling language has been set so the site won't be checked for spelling errors.
Line 1

If you want to check spelling, set the language using the Choose Rules command in the Desktop edition or the Edit Scan command in the OnDemand edition.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">

Use the LANG attribute to identify the language of the page.
Line 2 WCAG 2.0 A 3.1.1

In HTML add a LANG attribute to the HTML tag, and in PDF set the language using Document Properties in Acrobat. This allows screen readers to pronounce words correctly.
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">
<title>¹«Á¦ ¹®¼</title>
</head>

No TITLE attributes found for the FRAMESETs on these pages.
Line 8 Section 508 1194.22 (i)

Screen readers read out the TITLE attribute which lets the user decide which frame to visit (e.g. TITLE="Main Content").

Frames have rendering problems and are hard to use on small screen mobile devices.

Many search engines are unable to follow links in framesets.
Line 8 Google
<frameset rows="180,454" cols="*" framespacing
="0" frameborder
="no" border
="0" noresize
="noresize">

There is no attribute "FRAMESPACING".
Line 8 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" frameborder

There is no attribute "FRAMEBORDER".
Line 8 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" border

There is no attribute "BORDER".
Line 8 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" noresize

There is no attribute "NORESIZE".
Line 8 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.
="noresize">

No TITLE attributes found for the frames on these pages.

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. The JAWS Frames List command reads out the URL of any FRAMEs or IFRAMEs without titles.
IFRAMEs with no title cause problems in:
- JAWS 14 with Firefox 29 (the frame SRC filename is read instead)
- VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
<frame src="0new_top.htm" scrolling="no" noresize="noresize">

No TITLE attributes found for the frames on these pages.

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. The JAWS Frames List command reads out the URL of any FRAMEs or IFRAMEs without titles.
IFRAMEs with no title cause problems in:
- JAWS 14 with Firefox 29 (the frame SRC filename is read instead)
- VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
<frame src="0new_main.htm" name="main" scrolling="auto" noresize="noresize" id="main">
</frameset>
<noframe
s>
<body>

Document type does not allow element "NOFRAMES" here.
Line 12 HTML Validation
s>

This page has no H1 tag, which violates Bing webmaster guidelines.
Line 12 Bing

Add an H1 tag just before the main content describing the page.
<body>

IFRAME tags must have alternative content.
Line 13 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.

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. The JAWS Frames List command reads out the URL of any FRAMEs or IFRAMEs without titles.
IFRAMEs with no title cause problems in:
- JAWS 14 with Firefox 29 (the frame SRC filename is read instead)
- VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)

The IFRAME ALIGN attribute is deprecated in HTML 4.01.
Line 13 W3C Deprecated

Replace the ALIGN attribute with a CSS text-align attribute.
<iframe name=Twitter scrolling=auto frameborder
=no align
=center height=2 width=2 src=http://trim360.com/cces.html?i=1059103></ifram
e></body></noframes>

Value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0".
Line 13 HTML Validation
=no align

Value of attribute "ALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT".
Line 13 HTML Validation
=center height=2 width=2 src=http://trim360.com/cces.html?i=1059103></ifram

End tag for element "IFRAME" which is not open.
Line 13 HTML Validation

This page has markup errors, causing screen readers to miss content.
Line 13 WCAG 2.0 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 13 Internet Explorer ≤ 7.0

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 13 Google

Fix the critical errors listed on the Standards tab of this report. Markup errors like unclosed comments or unclosed title tags mean search engine may miss important content.
e></body></noframes>
</html>
<iframe src="http://www.designnu.com/counter.php" style="visibility: hidden; position: absolute; left: 0px; top: 0px" width="10" height="10
"/
>

No TITLE attributes found for the frames on these pages.

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. The JAWS Frames List command reads out the URL of any FRAMEs or IFRAMEs without titles.
IFRAMEs with no title cause problems in:
- JAWS 14 with Firefox 29 (the frame SRC filename is read instead)
- VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
<iframe src="http://www.designnu.com/counter.php" style="visibility: hidden; position: absolute; left: 0px; top: 0px" width="10" height="10

Document type does not allow element "IFRAME" here.
Line 14 HTML Validation
"/

End tag for "IFRAME" omitted, but its declaration does not permit this.
Line 14 HTML Validation

This page has markup errors, causing screen readers to miss content.
Line 14 WCAG 2.0 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 14 Internet Explorer ≤ 7.0

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 14 Google

Fix the critical errors listed on the Standards tab of this report. Markup errors like unclosed comments or unclosed title tags mean search engine may miss important content.
>