Issues:
Each section of content should begin with a heading tag (H1, H2, H3), but this page has no heading tags.
Line 1 WCAG2 AAA 2.4.10
Divide the content with headings so that the top level heading is H1, sub-headings are H2 and so on. Use CSS style rules to change heading font styles if needed.
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
No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The doctype of this page triggers quirks mode in IE, Firefox and most other browsers. This means pages may look different in different browsers.
Change the DOCTYPE statement to one that does not trigger quirks mode.
<script>
if (screen.width<=320)
window.location = "http://www.bukukita.com/m";
</script>
<
!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" >
!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" >
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.
<head>
<title>BukuKita.com - Aktifasi Keanggotaan - Toko Buku Online</title>
<link REL="SHORTCUT ICON" HREF="images/favicon.ico">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta http-equiv="Content-Language" content="EN" />
<meta name="Keywords" content="toko buku online murah, buku diskon, hadiah buku, buku kita,buku,TOKO,BUKU,bacaan,novel,cerpen,best seller,beli buku, jual buku,toko buku,buku sekolah,buku baru,buku komputer,jual,belanja,belanja online,katalog,katalog buku,buku sekolah,pustaka,resensi,pustaka,pengarang,penulis,judul,kitab suci,kitab,suci,tafsir,al quran,qur'an,buku islam,alkitab,kamus,aksara,orang tua, anak, remaja,bahasa,sd,slta,sltp,ekonomi,filsafat,hukum,kedokteran,psikologi,komputer,gramedia,gunung agung,budaya,penerbit,kompas,pustaka,pelajar,mahasiswa,majalah,komik,cerita lucu,sepakbola,bulletin,tabloid,editor,online,tafsir,mizan,kaifa,agromedia,andi offset, bip, dinastindo,e plus, elex media, escaeva,metafor,mizan,nafiri,matahati,serambi,habibie center,zahra,prabowo,habibie,editorial,news" />
<meta name="Description" content="Toko Buku Online BukuKita.COM - Komunitas Buku Indonesia. Buku murah, banjir diskon dan hadiah. Buku Aktifasi Keanggotaan (
&g
t;&g
t; )." />
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
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 ¶m=value is used instead of &param=value in URL query strings.
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
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
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;&g
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
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; )." />
<meta name="Abstract" content="Toko Buku Online BukuKita.COM - Komunitas Buku Indonesia - Toko Buku Murah Diskon dan Berhadiah - Beli Buku Murah, Buku Diskon, Undian Buku Gratis dan Undian Berhadiah Buku" />
<meta name="distribution" content="Global" />
<meta name="resource-type" content="document" />
<meta name="ROBOTS" content="INDEX,FOLLOW" />
<meta name="Designer" content="webmaster@bukukita.com" />
<meta name="Owner" content="admin@bukukita.com">
<meta name="Author" content="bukukita.com">
<meta name="revisit-after" content="1 days">
<link type="text/css" href="js/ui.tabs.css" rel="stylesheet">
<link type="text/css" href="js/demos.css" rel="stylesheet">
<script src="js/jquery-1.3.2.min.js"></script>
<script src="js/ui.core.js"></script>
<script src="js/ui.tabs.js"></script>
<script src="js/ui.carousel.js"></script>
<script src="js/effects.core.js"></script>
<script src="js/effects.slide.js"></script>
<!--<Script Language="JavaScript">
function loadChatterBox(){
var load = window.open("Chatter_box.php",'','scrollbars=yes,menubar=no,height=600,width=300,resizable=no,toolbar=no,location=no,status=no');
}
</Script>
-->
Replace the language attribute with type="text/javascript"
<Script Language="JavaScript">
<!--Script courtesy of http://www.web-source.net - Your Guide to Professional Web Site Design and Development //-->
function loadintro() {
var load = window.open('images/intro.swf','','scrollbars=no,menubar=no,height=576,width=720,resizable=no,toolbar=no,location=no,status=no');
}
</Scrip
t>
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 42 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.
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>
<style type="text/css">
<!--
body,td,th {
font-family: Verdana, Arial, sans-serif;
font-size: 11px;
color: #333333;
}
body {
background-color: #FFFFFF /*E2E2E2;*/;
}
a:link {
text-decoration: none;
color: #7B7B7D /*1E71C4*/;
}
a:visited {
text-decoration: none;
color: #7B7B7D /*1E71C4*/;
}
a:hover {
text-decoration: none;
color: #0085CF /*F69739*/;
}
a:active {
text-decoration: none;
}
-->
</style>
<link href="bukukita.css" rel="stylesheet" type="text/css" />
Replace the language attribute with type="text/javascript"
<script type="text/javascript" language="JavaScript1.2" src="stm31.js"></script>
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-24092805-1']);
_gaq.push(['_setDomainName', '.bukukita.com']);
_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);
})();
</head>
The BODY LEFTMARGIN attribute is an Internet Explorer specific extension.
Replace this with a CSS rule:
body { margin: 4px; }
The BODY TOPMARGIN attribute is an Internet Explorer specific extension.
Replace this with a CSS rule:
body { margin: 4px; }
Add an H1 tag just before the main content describing the page.
<body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
Replace the ALIGN attribute with a CSS text-align attribute.
<table width="1002" align="center" border="0" cellspacing="0" cellpadding="1">
<tr>
<td align="center" valign="top"><table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
Use background images sparingly and make sure they are simple, especially behind text.
Line 93 Usability.gov 14:1
Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates.
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="1024" height="109" background="images/header_newlogo1.jpg"><div style="width:54%; margin-left:350px; margin-top:33px"><table width="100%" border="0" cellpadding="2" cellspacing="2" style="margin-left:-80px;">
Replace the language attribute with type="text/javascript"
<Script LANGUAGE="JavaScript">
function showpagesearch(form)
{
var item = form.id.selectedIndex;
choice = form.id.options[item].value;
if (choice!="") top.location.href=(choice);
};
function loadhelp()
{
var load = window.open('help_cari.htm','','scrollbars=yes,menubar=no,height=300,width=400,resizable=yes,toolbar=no,location=no,status=no');
};
function cekId(form)
{
if(form.id.value=="")
{
alert("Silahkan pilih kategori pencarian terlebih dahulu.");
return 0;
}
};
</script>
<tr>
Forms that force users to shift back and forth between keyboard and mouse substantially slow their entry speed. This form contains text boxes requiring keyboard input, and other controls requiring mouse input.
Line 115 Usability.gov 13:13
Replace the dropdown list with a control that allows keyboard input, so the whole form can be completed using the keyboard.
<form action="searchresult.php" method="post" name="isi_cari">
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td align="left" width="1%" valign="top">
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 116 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="images/cari_berdasarkan.gif"></td>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td align="left" width="1%" valign="top">
SELECT lists cannot be operated from the keyboard if they have an ONCHANGE handler that performs navigation, because the handler fires as the user moves the selection up and down using the keyboard.
Line 118 WCAG2 A F36
Moving through list items using the arrow keys will jump to another page unexpectedly.
This form control has no associated LABEL element.
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.
This form has fields without LABEL elements or TITLE attributes.
Line 118 Section 508 1194.22 (n)
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Display default values whenever a likely default choice can be defined. Provide a default selection for SELECT lists.
Line 118 Usability.gov 13:18
When likely default values are known, offer those values to speed data entry. The initial or default item could be the most frequently selected item or the last item selected by that user.
Use LABEL tags for each data entry field to show what data is expected.
Line 118 Usability.gov 13:5
Make sure each INPUT field has an associated LABEL tag describing the field.
<select size="1" name="id" class="field_input" onchange="showpagesearch(this.form);" accesskey="c">
<option value='index.php?id=1'>Judul</option><option value='index.php?id=2'>Penulis</option><option value='index.php?id=3'>Penerbit</option><option value='index.php?id=4'>Kategori</option><option value='index.php?id=5'>No. ISBN</option> </select>
</td>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td align="left" width="2%" valign="top">
All ONMOUSEDOWN handlers should have an equivalent ONKEYDOWN handler.
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users.
This form control has no associated LABEL element.
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.
This form has fields without LABEL elements or TITLE attributes.
Line 122 Section 508 1194.22 (n)
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Use LABEL tags for each data entry field to show what data is expected.
Line 122 Usability.gov 13:5
Make sure each INPUT field has an associated LABEL tag describing the field.
<input type="text" name="key" size="30" class="field_input" onmousedown="cekId(this.form)">
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 123 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.
Replace the ALIGN attribute with a CSS text-align attribute.
Replace the border attribute with a CSS rule. For example:
img { border: 1px solid red; }
img { border: none; }
<img src="images/icon_over.gif" border="0" align="absmiddle">
This form control has no associated LABEL element.
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.
This form has fields without LABEL elements or TITLE attributes.
Line 124 Section 508 1194.22 (n)
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Display default values whenever a likely default choice can be defined. Provide a default selection for SELECT lists.
Line 124 Usability.gov 13:18
When likely default values are known, offer those values to speed data entry. The initial or default item could be the most frequently selected item or the last item selected by that user.
Use LABEL tags for each data entry field to show what data is expected.
Line 124 Usability.gov 13:5
Make sure each INPUT field has an associated LABEL tag describing the field.
<select size="1" name="match" class="field_input_2">
<option value="2" selecte
d>Per Kata (Cari Bebas)</option>
d>Per Kata (Cari Bebas)</option>
<option value="1">Per Kalimat (Cari Tepat)</option>
<option value="">Dalam Kata (Cari Bebas)</option>
</select>
<div style="position:absolute;z-index:1;left:700px;top:75px;">
<a href="javascript:loadhelp()">
<img src="images/help3.gif" border="0" hspace="0px" align="absmiddle" title="Panduan Mencari Judul"></a></div>
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.
<a href="javascript:loadhelp()">
Add an ALT attribute describing each image, which screen readers read aloud.
Spacer images and purely decorative images should use ALT=''.
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Line 129 Usability.gov 10:6
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image.
Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping').
Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
Line 129 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.
Replace the ALIGN attribute with a CSS text-align attribute.
Replace the border attribute with a CSS rule. For example:
img { border: 1px solid red; }
img { border: none; }
Replace the HSPACE attribute with a CSS margin. For example:
img { margin-left: 10px; margin-right: 10px; }
<img src="images/help3.gif" border="0" hspace="0px" align="absmiddle" title="Panduan Mencari Judul"></a></div>
</td>
<input name="page" type="hidden" value="1" />
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td align="left" width="1%" valign="top">
INPUT TYPE=IMAGE tags must have an ALT attribute.
Add an ALT attribute describing the button action, which screen readers read aloud.
<input type="image" src="images/cari.gif" name="Submit3" value="Submit" title='Cari Buku berdasarkan '></td>
<td>
&nbs
p;</td>
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 134 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 ¶m=value is used instead of &param=value in URL query strings.
Line 134 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
&nbs
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 134 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
p;</td>
</form>
</tr>
</table>
</div></td>
</tr>
</table></td>
</tr>
<tr>
<td align="center" valign="top"><STYLE>
<!--
.menu .options {
BACKGROUND-COLOR: #006DB8 /*323232*/; COLOR: #000000; FONT-FAMILY: verdana, arial, sans-serif; FONT-SIZE: 11px; MARGIN-BOTTOM: 1px; MARGIN-RIGHT: 1px
}
.menu A {
BACKGROUND-COLOR: transparent; COLOR: #FFFFFF /*dce0e4*/; DISPLAY: block; PADDING-BOTTOM: 5px; PADDING-LEFT: 8px; PADDING-RIGHT: 10px; PADDING-TOP: 2px; TEXT-DECORATION: none
}
.menu A:visited {
BACKGROUND-COLOR: transparent; COLOR: #FFFFFF /*dce0e4*/; DISPLAY: block; PADDING-BOTTOM: 5px; PADDING-LEFT: 8px; PADDING-RIGHT: 10px; PADDING-TOP: 2px; TEXT-DECORATION: none
}
.menu A:hover {
BACKGROUND-COLOR: transparent; COLOR: #ED217D;/*AADC29*/
}
#about {
LEFT: 5px; POSITION: absolute; TOP: 200px; VISIBILITY: hidden
#carousel { position: relative; height: 160px; margin: 0; padding: 0; }
#carousel li { float: left; cursor: pointer; cursor: hand; list-style: none; margin: 0; padding: 0; width: 128px; height: 128px; }
#carousel li img { height: 100%; width: 100%; }
-->
}
</STYLE>
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript" src="menus.js"></SCRIPT>
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript">new dropMenu('anggota', 'down', 63, 151, 210, 200)</SCRIPT>
<DIV id="anggotaContainer">
<DIV class="menu" id="anggotaContent">
Replace the ALIGN attribute with a CSS text-align attribute.
<DIV class="options" align="left">
<A href="daftar.php" >Pendaftaran</A>
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
<A href="index.php?lo=2" >Aktivasi Keanggotaan</A>
<A href="password_reset.php" >Lupa Password</A>
<A href="datamember.php" >Lihat / Ubah Profil</A>
</DIV></DIV></DIV>
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript">new dropMenu('lihatBuku', 'down', 98, 151, 232, 200)</SCRIPT>
<DIV id="lihatBukuContainer">
<DIV class="menu" id="lihatBukuContent">
Replace the ALIGN attribute with a CSS text-align attribute.
<DIV class="options" align="left">
<A href="katalogbukuatribut.php?atrId=2
&pag
e=1" >Buku Baru</A>
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 181 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 ¶m=value is used instead of &param=value in URL query strings.
Line 181 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
&pag
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 181 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=1" >Buku Baru</A>
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
<A href="katalogbukuatribut.php?atrId=1&pag
e=1" >Buku Terlaris</A>
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 182 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=1" >Buku Terlaris</A>
<A href="katalogbukuatribut.php?atrId=3&pag
e=1" >Buku Populer</A>
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 183 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=1" >Buku Populer</A>
<A href="katalogbukuatribut.php?atrId=4&pag
e=1" >Buku Rekomendasi</A>
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 184 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=1" >Buku Rekomendasi</A>
<A href="katalogbukuatribut.php?atrId=5&pag
e=1" >Buku Promosi</A>
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 185 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=1" >Buku Promosi</A>
</DIV></DIV></DIV>
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript">new dropMenu('undian', 'down', 140, 151, 340, 200)</SCRIPT>
<DIV id="undianContainer">
<DIV class="menu" id="undianContent">
Replace the ALIGN attribute with a CSS text-align attribute.
<DIV class="options" align="left">
<A href="info_undian.php" >Info Undian</A>
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
<A href="nomorundian.php?all=1" >Daftar Nomor Undian Bulan Ini</A>
<A href="pemenang.php" >Daftar Pemenang Undian</A>
<A href="nomorundian.php" >Nomor Undian Anda</A>
</DIV></DIV></DIV>
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript">new dropMenu('point', 'down', 201, 151, 340, 200)</SCRIPT>
<DIV id="pointContainer">
<DIV class="menu" id="pointContent">
Replace the ALIGN attribute with a CSS text-align attribute.
<DIV class="options" align="left">
<A href="point.php?info=1" >Info Point Rewards</A>
<A href="point.php" >Point Rewards Anda</A>
</DIV></DIV></DIV>
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript">new dropMenu('transaksi', 'down', 252, 151, 412, 200)</SCRIPT>
<DIV id="transaksiContainer">
<DIV class="menu" id="transaksiContent">
Replace the ALIGN attribute with a CSS text-align attribute.
<DIV class="options" align="left">
<A href="memberwishlist.php" >Daftar Keinginan</A>
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
<A href="membercartlist.php" >Keranjang Belanja</A>
<A href="historytransaksi.php" >Histori Belanja</A>
<A href="historytransaksi.php" >Konfirmasi Pembayaran</A>
</DIV></DIV></DIV>
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript">new dropMenu('cekst', 'down', 292, 151, 428, 200)</SCRIPT>
<DIV id="cekstContainer">
<DIV class="menu" id="cekstContent">
Replace the ALIGN attribute with a CSS text-align attribute.
<DIV class="options" align="left">
<A href="historytransaksi.php" >Status Pembayaran</A>
<A href="historytransaksi.php" >Status Pengiriman</A>
</DIV></DIV></DIV>
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript">new dropMenu('berita', 'down', 335, 151, 444, 200)</SCRIPT>
<DIV id="beritaContainer">
<DIV class="menu" id="beritaContent">
Replace the ALIGN attribute with a CSS text-align attribute.
<DIV class="options" align="left">
<A href="berita/info-bukukita/" >Info BukuKITA</A>
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
<A href="testimonial.php" >Testimonial</A>
<A href="berita/acara/" >Acara</A>
<A href="berita/buku/" >Buku</A>
<A href="berita/promosi/" >Promosi</A>
</DIV></DIV></DIV>
<!--<SCRIPT language="javascript">new dropMenu('galeri', 'down', 304, 151, 418, 200)</SCRIPT>
<DIV id="galeriContainer">
<DIV class="menu" id="galeriContent">
<DIV class="options" align="left">
<A href="intro.php" >Intro BukuKITA</A>
<A href="stuff.php?page=wallpaper" >Wallpaper</A>
<A href="stuff.php?page=ecard" >E-Card</A>
</DIV></DIV></DIV>
-->
Replace the language attribute with type="text/javascript"
<SCRIPT language="javascript">new dropMenu('komunitas', 'down', 398, 151, 517, 200)</SCRIPT>
<DIV id="komunitasContainer">
<DIV class="menu" id="komunitasContent">
Replace the ALIGN attribute with a CSS text-align attribute.
<DIV class="options" align="left">
Avoid specifying a new window as the target of a link with target="_blank".
Line 248 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://blog.bukukita.com" target="_blank">BLOG BukuKITA</A>
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
<A href="komunitas.php#milis" >Milis BukuKITA</A>
<A href="komunitas.php#facebook">Facebook</A>
<A href="komunitas.php#fs" >Friendster</A>
</DIV></DIV></DIV>
<table id="Table_01" width="100%" height="96" border="0" cellpadding="0" cellspacing="0">
<tr>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="21" height="96"><img src="images/menu_01.gif" width="21" height="96" alt=""></td>
Use background images sparingly and make sure they are simple, especially behind text.
Line 257 Usability.gov 14:1
Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates.
<td background="images/menu_02a.gif">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="90%" height="60" valign="top">
Replace the language attribute with type="text/javascript"
<SCRIPT language="JavaScript">
document.write("<table width='100%' style='padding-top:12px;' border='0' cellspacing='0' cellpadding='0'><tr><td width='112'>");
//-beli-buku-murah-buku-diskon-undian-buku-gratis-dan-undian-berhadiah-buku
document.write("<a href='http://www.bukukita.com/' target='_self' class='itemmenu'>Halaman Depan</a>");
document.write("</td><td width='70'>");
document.write("<a href='daftar.php' class='itemmenu' onmouseover
=\"dropMenu.showMenu('anggota');\" onmouseout
=\"dropMenu.hideMenu('anggota')\">Anggota</a>");
An attribute value must be a literal unless it contains only name characters.
Line 266 HTML Validation
=\"dropMenu.showMenu('anggota');\" onmouseout
An attribute value must be a literal unless it contains only name characters.
Line 266 HTML Validation
=\"dropMenu.hideMenu('anggota')\">Anggota</a>");
document.write("</td><td width='83'>");
document.write("<a href='katalogbuku.php' class='itemmenu' onmouseover
=\"dropMenu.showMenu('lihatBuku');\" onmouseout
=\"dropMenu.hideMenu('lihatBuku')\">Lihat Buku</a>");
An attribute value must be a literal unless it contains only name characters.
Line 268 HTML Validation
=\"dropMenu.showMenu('lihatBuku');\" onmouseout
An attribute value must be a literal unless it contains only name characters.
Line 268 HTML Validation
=\"dropMenu.hideMenu('lihatBuku')\">Lihat Buku</a>");
document.write("</td><td width='122'>");
document.write("<a href='nomorundian.php?all=1' class='itemmenu' onmouseover
=\"dropMenu.showMenu('undian');\" onmouseout
=\"dropMenu.hideMenu('undian')\">Undian Berhadiah</a>");
An attribute value must be a literal unless it contains only name characters.
Line 270 HTML Validation
=\"dropMenu.showMenu('undian');\" onmouseout
An attribute value must be a literal unless it contains only name characters.
Line 270 HTML Validation
=\"dropMenu.hideMenu('undian')\">Undian Berhadiah</a>");
document.write("</td><td width='102'>");
document.write("<a href='point.php?info=1' class='itemmenu' onmouseover
=\"dropMenu.showMenu('point');\" onmouseout
=\"dropMenu.hideMenu('point')\">Point Rewards</a>");
An attribute value must be a literal unless it contains only name characters.
Line 272 HTML Validation
=\"dropMenu.showMenu('point');\" onmouseout
An attribute value must be a literal unless it contains only name characters.
Line 272 HTML Validation
=\"dropMenu.hideMenu('point')\">Point Rewards</a>");
document.write("</td><td width='80'>");
document.write("<a href='historytransaksi.php' class='itemmenu' onmouseover
=\"dropMenu.showMenu('transaksi');\" onmouseout
=\"dropMenu.hideMenu('transaksi')\">Transaksi</a>");
An attribute value must be a literal unless it contains only name characters.
Line 274 HTML Validation
=\"dropMenu.showMenu('transaksi');\" onmouseout
An attribute value must be a literal unless it contains only name characters.
Line 274 HTML Validation
=\"dropMenu.hideMenu('transaksi')\">Transaksi</a>");
document.write("</td><td width='86'>");
document.write("<a href='historytransaksi.php' class='itemmenu' onmouseover
=\"dropMenu.showMenu('cekst');\" onmouseout
=\"dropMenu.hideMenu('cekst')\">Cek Status</a>");
An attribute value must be a literal unless it contains only name characters.
Line 276 HTML Validation
=\"dropMenu.showMenu('cekst');\" onmouseout
An attribute value must be a literal unless it contains only name characters.
Line 276 HTML Validation
=\"dropMenu.hideMenu('cekst')\">Cek Status</a>");
document.write("</td><td width='59'>");
document.write("<a href='berita/' class='itemmenu' onmouseover
=\"dropMenu.showMenu('berita');\" onmouseout
=\"dropMenu.hideMenu('berita')\">Berita</a>");
An attribute value must be a literal unless it contains only name characters.
Line 278 HTML Validation
=\"dropMenu.showMenu('berita');\" onmouseout
An attribute value must be a literal unless it contains only name characters.
Line 278 HTML Validation
=\"dropMenu.hideMenu('berita')\">Berita</a>");
document.write("</td><td width='67'>");
document.write("<a href='resensi-review-buku/semua/' target='_self' class='itemmenu'>Resensi</a>");
document.write("</td><td width='84'>");
document.write("<a href='komunitas.php' class='itemmenu' onmouseover
=\"dropMenu.showMenu('komunitas');\" onmouseout
=\"dropMenu.hideMenu('komunitas')\">Komunitas</a>");
An attribute value must be a literal unless it contains only name characters.
Line 282 HTML Validation
=\"dropMenu.showMenu('komunitas');\" onmouseout
An attribute value must be a literal unless it contains only name characters.
Line 282 HTML Validation
=\"dropMenu.hideMenu('komunitas')\">Komunitas</a>");
document.write("</td><td>");
document.write("&nbs
p;");
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 284 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
p;");
document.write("</td></tr></table>");
</SCRIPT> <br>
Replace the ALIGN attribute with a CSS text-align attribute.
<div align=center style="padding-top:2px;">
<a name="imenuutama"></a>
<a href='http://twitter.com/bukukita' target='_blank'>Follow twitter @bukukita dan facebook untuk hadiah dan info terbaru setiap hari</a> &nbs
p;&nbs
p;<span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 109 hari lagi</span> </div>
Avoid specifying a new window as the target of a link with target="_blank".
Line 288 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://twitter.com/bukukita' target='_blank'>Follow twitter @bukukita dan facebook untuk hadiah dan info terbaru setiap hari</a> &nbs
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 288 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
p;&nbs
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 288 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
p;<span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 109 hari lagi</span> </div>
</td>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="10%" height="60" valign="bottom" style="padding-bottom:3px">
<!--<script type="text/javascript">var addthis_pub="cybernice";</script>
<a href="http://www.addthis.com/bookmark.php?v=20" onmouseover="return addthis_open(this, '', '[URL]', '[TITLE]')" onmouseout="addthis_close()" onclick="return addthis_sendto()"><img src="http://s7.addthis.com/static/btn/lg-bookmark-en.gif" width="125" height="16" alt="Bookmark and Share" style="border:0"/></a>
<script type="text/javascript" src="http://s7.addthis.com/js/200/addthis_widget.js"></script>-->
All ONMOUSEOVER handlers should have an equivalent ONFOCUS handler.
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users.
All ONMOUSEOUT handlers should have an equivalent ONBLUR handler.
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users.
<div id="divBookImg" style="position:absolute;left:0;top:0;visibility:hidden;" onMouseOver="resizePic(event)" onMouseOut="resizePic(event)"></div>
</td>
</tr>
<tr>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
<td height="26">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="182">
Minggu, 22 September 2013 </td>
<td>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td align="center" class="bonus02 menuatas"><a href='http://www.bukukita.com/Hobi-dan-Usaha/Perkebunan-Pertanian-Perikanan/91931-100-Tumbuhan-Dilindungi-di-Gede-Pangrango.html'>100 Tumbuhan Dilindungi di Gede Pangrango</a> <!--<marquee scrolldelay="150">
Silahkan anda Registrasi atau Login Anggota terlebih dahulu.
</marquee>-->
</td>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="20%" align="right">&nbs
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 310 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
p;</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="21" height="56"><img src="images/menu_03.gif" width="21" height="96" alt=""></td>
</tr>
</table>
<!-- End ImageReady Slices -->
</body>
</html>
</t
d>
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 326 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.
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.
d>
</t
r>
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 327 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.
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.
r>
<td align="center" valign="top" class="content">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="182" align="left" valign="top"><table width="182" border="0" cellspacing="0">
<tr>
<td valign="top" class="jarak_kategori">
<table width="182" border="0" cellpadding="0" cellspacing="0">
<tr>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="128" height="15"><img src="images/login_01.gif" width="182" height="15" alt="" /></td>
</tr>
<tr>
<td valign="top" class="borderlogin">
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<form action="index.php?lo=3" method="post" name="isi_aktivasi">
<tr>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="41%" class="user_name" colspan="2">
HTML font tags should be replaced by equivalent CSS rules. For example, you can set the font on every paragraph
by the following CSS rule:
p { font-family: Arial; font-size: 14pt; }
<font color='red'><b> <br>Aktivasi Keanggotaan</b></font><br></td>
</tr>
<tr>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="41%" class="user_name" colspan="2" height="20">User Name </td>
</tr>
<tr>
<td colspan="2">
<input type="text" name="user" size="15" maxlength="14" value="" accesskey="u" autocomplete="off"></td>
This form control has no associated LABEL element.
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.
This form has fields without LABEL elements or TITLE attributes.
Line 350 Section 508 1194.22 (n)
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Use LABEL tags for each data entry field to show what data is expected.
Line 350 Usability.gov 13:5
Make sure each INPUT field has an associated LABEL tag describing the field.
<input type="text" name="user" size="15" maxlength="14" value="" accesskey="u" autocomplete="off"></td>
</tr>
<tr>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="41%" class="user_name" colspan="2">Isi Kode Aktivasi </td>
</tr>
<tr>
<td colspan="2">
<input type="text" name="aktivcode" size="15" maxlength="14"></td>
This form control has no associated LABEL element.
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.
This form has fields without LABEL elements or TITLE attributes.
Line 356 Section 508 1194.22 (n)
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Use LABEL tags for each data entry field to show what data is expected.
Line 356 Usability.gov 13:5
Make sure each INPUT field has an associated LABEL tag describing the field.
<input type="text" name="aktivcode" size="15" maxlength="14"></td>
</tr>
<tr>
<td align="left" colspan="2"><input type="submit" value="Aktifkan"></td>
</tr>
</form>
</table>
</td>
</tr>
<tr>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="128" height="0"><img src="images/login_03.gif" width="182" height="6" alt="" /></td>
</tr>
</table>
</td>
</tr>
<tr>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="12" valign="middle" class=jarak_kategori>
&nbs
p; </td>
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 373 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
p; </td>
</tr>
<tr>
<td class="jarak_kategori" align="center"><a name="ibawahkiri"></a>
<a href='http://www.bukukita.com/Biografi-dan-Memoar/Biografi/116954-Buku-Noah-Eksklusif-Limited-edition-,-6.903-Mil:-Cerita-di-Balik-Konser-2-Benua-5-Negara.html'>
<img src='images/banner/418' width='182' height='150' border='0' title='Paket Buku Noah Eksklusif Bersertifikat'></a><br><span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 30 hari lagi</span></td>
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.
<a href='http://www.bukukita.com/Biografi-dan-Memoar/Biografi/116954-Buku-Noah-Eksklusif-Limited-edition-,-6.903-Mil:-Cerita-di-Balik-Konser-2-Benua-5-Negara.html'>
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='images/banner/418' width='182' height='150' border='0' title='Paket Buku Noah Eksklusif Bersertifikat'></a><br><span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 30 hari lagi</span></td>
</tr>
<tr>
<td class="jarak_kategori" align="center">
<a href='http://www.bukukita.com/berita/promo/622-gunakan-xl-tunai-dan-dapatkan-potongan-rp-25-000.html' target='_blank'>
<img src='images/banner/427' width='182' height='150' border='0' title='Pakai XL TUNAI dan Dapatkan Potongan Rp 25.000'></a><br><span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 17 hari lagi</span></td>
Avoid specifying a new window as the target of a link with target="_blank".
Line 380 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".
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.
<a href='http://www.bukukita.com/berita/promo/622-gunakan-xl-tunai-dan-dapatkan-potongan-rp-25-000.html' target='_blank'>
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='images/banner/427' width='182' height='150' border='0' title='Pakai XL TUNAI dan Dapatkan Potongan Rp 25.000'></a><br><span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 17 hari lagi</span></td>
</tr>
<tr>
<td class="jarak_kategori" align="center">
<a href='http://m.bukukita.com' target='_blank'>
<img src='images/banner/422' width='182' height='75' border='0' title='Akses Cepat via Mobile >> m.bukukita.com'></a><br><span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 82 hari lagi</span></td>
Avoid specifying a new window as the target of a link with target="_blank".
Line 383 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".
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.
<a href='http://m.bukukita.com' target='_blank'>
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='images/banner/422' width='182' height='75' border='0' title='Akses Cepat via Mobile >> m.bukukita.com'></a><br><span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 82 hari lagi</span></td>
</tr>
<tr>
<td class="jarak_kategori" align="center">
<a href='http://www.bukukita.com/katalogbuku.php?masId=21'>
<img src='images/banner/178' width='182' height='75' border='0' title='Majalah Murah, Majalah Online, Majalah Lengkap Tersedia di Bukukita'></a><br><span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 9 hari lagi</span></td>
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.
<a href='http://www.bukukita.com/katalogbuku.php?masId=21'>
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='images/banner/178' width='182' height='75' border='0' title='Majalah Murah, Majalah Online, Majalah Lengkap Tersedia di Bukukita'></a><br><span align='center' style='color:#999999;font-size:9px;font-family:arial'>Tayang: 9 hari lagi</span></td>
<tr>
<td class="jarak_kategori" align="center">
<script type="text/javascript"><!--
google_ad_client = "ca-pub-7440868299486030";
/* 160x600bk */
google_ad_slot = "8541848549";
google_ad_width = 160;
google_ad_height = 600;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</td>
</tr>
</tr>
</table></td>
<td align="left" valign="top" class="jarak_teks_menu">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td align="center" valign="top" class="jarak_kanan2">
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="7" height="7"><img src="images/border_content_01.gif" width="7" height="7" alt="" /></td>
Use background images sparingly and make sure they are simple, especially behind text.
Line 416 Usability.gov 14:1
Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates.
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="100%" background="images/border_content_02.gif"><img src="images/border_content_02.gif" width="390" height="7" alt="" /></td>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="7" height="7"><img src="images/border_content_03.gif" width="7" height="7" alt="" /></td>
</tr>
<tr>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="7" height="7"><img src="images/border_content_05.gif" width="7" height="7" alt="" /></td>
Use background images sparingly and make sure they are simple, especially behind text.
Line 421 Usability.gov 14:1
Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates.
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="100%" background="images/border_content_06.gif"><img src="images/border_content_06.gif" width="88" height="7" alt="" /></td>
Replace the HEIGHT attribute with a CSS height:
td { height: 14pt; }
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="7" height="7"><img src="images/border_content_07.gif" width="7" height="7" alt="" /></td>
</tr>
</table>
</td>
</tr>
</table>
</td>
Replace width attributes with CSS rules. For example:
td.two-column { width: 50%; }
<td width="160" align="left" valign="top">
&nbs
p; </td>
An unknown entity has been used. This often happens when ¶m=value is used instead of &param=value in URL query strings.
Line 430 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
p; </td>
</tr>
</table>
</td>
</tr>
</tabl
e>
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 435 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.
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>
</bod
y>
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 436 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.
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.
y>
</htm
l>
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 437 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.
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.
l>