Source View: http://hungryhouse.co.uk/join

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<head>

Document title must not be blank.

Line 5 WCAG2 A F25

For HTML pages change the TITLE tag. For Office documents and PDF documents produced from Office, fill in the Title in Document Properties before saving as PDF.

Google, Bing and Yahoo recommend that all pages have a non-blank TITLE tag.

Line 5 Google Yahoo Bing

var $_hh = {media: "http://static.hungryhouse.co.uk/", base: "http://hungryhouse.co.uk/", self: "http://hungryhouse.co.uk/include/", mobile_version: 'http://hungryhouse.co.uk/~m', host: '.hungryhouse.co.uk', media_path: 'http://static.hungryhouse.co.uk/', iswl : false};

</script>

Required attribute "type" not specified.

Line 20 HTML Validation

"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.tools.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.cookie.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.history.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.fancybox.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.uniform.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/checkout.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.growl.min.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/jquery.easing.js?30"></script><script language="javascript" type="text/javascript" src="http://static.hungryhouse.co.uk/include/device.detect.js?30"></script>

var _vwo_code=(function(){

var account_id=6352,

settings_tolerance=2000,

library_tolerance=1500,

use_existing_jquery=false,

// DO NOT EDIT BELOW THIS LINE

f=false,d=document;return{use_existing_jquery:function(){return use_existing_jquery;},library_tolerance:function(){return library_tolerance;},finish:function(){if(!f){f=true;var a=d.getElementById('_vis_opt_path_hides');if(a)a.parentNode.removeChild(a);}},finished:function(){return f;},load:function(a){var b=d.createElement('script');b.src=a;b.type='text/javascript';b.innerText;b.onerror=function(){_vwo_code.finish();};d.getElementsByTagName('head')[0].appendChild(b);},init:function(){settings_timer=setTimeout('_vwo_code.finish()',settings_tolerance);this.load('//dev.visualwebsiteoptimizer.com/j.php?a='+account_id+'

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

Line 29 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 29 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 29 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 29 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

u='+encodeURIComponent(d.URL)+'

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

Line 29 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 29 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 29 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 29 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='+Math.random());var a=d.createElement('style'),b='body{opacity:0 !important;filter:alpha(opacity=0) !important;background:none !important;}',h=d.getElementsByTagName('head')[0];a.setAttribute('id','_vis_opt_path_hides');a.setAttribute('type','text/css');if(a.styleSheet)a.styleSheet.cssText=b;else a.appendChild(d.createTextNode(b));h.appendChild(a);return settings_timer;}};}());_vwo_settings_timer=_vwo_code.init();

</script>

</head>

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

Line 43 Broken Link

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

<a class="logo" href="" title="order takeaway online"><span>Hungryhouse.co.uk</span></a>

<a id="mainmenu-item-join" href="/join" id

Duplicate specification of attribute "id".

Line 46 HTML Validation

="guest-join-button" class="toolTipPopup guestJoinButton"><span>Join</span></a>

<span class="tooltipPopup"><

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

Line 47 HTML Validation

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

Line 47 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>Members benefit from a better Checkout experience, but it's also possible to order as a guest without creating an account.</p></span>

The A NAME attribute is deprecated in XHTML 1.0, and is illegal in XHTML 1.1 Strict.

Line 49 W3C Deprecated

Use the ID attribute instead.

</div>

</li>

<li>

<a title="My Order" href="/search_loading"><span>My Order</span></a>

</li>

<li>

<a title="Help" href="/contact"><span>Contact/Help</span></a>

</li>

<li>

<a title="Order Tracking" href="/ordertracking" class="homeNavOrderTracking"><span>Order Tracking</span></a>

</li>

</ul>

<span>Order Takeaway Online!</span>

</div>

<scrip

Required attribute "type" not specified.

Line 69 HTML Validation

t>try{$(".guestJoinButton").tooltip({ position: ['bottom', 'center'], offset: [14, 0]})} catch(e){}</script>

<ul id="sub-menu"><li class="menuActive" id="enter_details"><span>1) Enter my Details</span></li><li><span>2) Create Membership</span></li><li><a href="main.php?menu=Join&submenu=activate_membership_direct"><span>3) Activate Membership</span></a></li></ul></div></div>

</div>

</div><div id="main-container">

<div id=

ID "maincontent" already defined.

Line 80 HTML Validation

This page has duplicate IDs which cause problems in screen readers.

Line 80 WCAG2 A F77

Two or more tags on this page share the same ID. Change the ID so it is unique for each tag.

"maincontent">

<form action="main.php?menu=Join

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

Line 86 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 86 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

&submen

Reference not terminated by REFC delimiter.

Line 86 HTML Validation

Reference to external entity in attribute value.

Line 86 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 86 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

u=enter_details" method="post">

<div class="tips-text padding-4 joinWelcomeTips">Please note that we are SafeBuy accredited. We keep your personal information safe and do not pass it on to third parties. We do not use spam marketing techniques.</div>

<div class="memberAtfacebook">You can also sign into hungryhouse with your <a href="faq/Using%20Facebook%20to%20Sign%20in">Facebook</a> details</div></div>

<tr class="join_form_bg_0"><td><span class="form-label label">Title:</span></td><td>

This form control has no associated LABEL element.

Line 94 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.

This form has fields without LABEL elements or TITLE attributes.

Line 94 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 94 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

Radio buttons are easier to use than drop-downs when there are 6 choices or less.

Line 94 Usability.gov 13:9

One usability study showed radio buttons give reliably better performance than drop-down lists for mutually exclusive selections. If screen space allows use radio buttons instead of lists/dropdowns with fewer than 7 items.

<select name="cust_title" class="form-text-select"><option>choose a title...</option><option>Mr</option><option>Miss</option><option>Mrs</option><option>Ms</option></select> </td>

</tr>

<span class="form-label label">First name:</span>

</td>

<td>

This form control has no associated LABEL element.

Line 99 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.

This form has fields without LABEL elements or TITLE attributes.

Line 99 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 99 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input type="text"

class="form-text-input-join"

value=""

name="cust_first_name" id="cust_first_name" /></td>

</tr>

</td>

<td>

This form control has no associated LABEL element.

Line 107 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.

This form has fields without LABEL elements or TITLE attributes.

Line 107 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 107 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input type="text"

class="form-text-input-join"

value=""

name="cust_last_name" id="cust_last_name" /></td>

</tr>

<span class="form-label label">Postcode:</span></td>

<td>

This form control has no associated LABEL element.

Line 114 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.

This form has fields without LABEL elements or TITLE attributes.

Line 114 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 114 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input placeholder

There is no attribute "placeholder".

Line 114 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.

="eg. SW6 6LG" type="text"

class="form-text-input-join"

value=""

name="locality_postcode" id="locality_postcode" /></td>

</tr>

<span class="form-label label">Street address:</span></td>

<td>

This form control has no associated LABEL element.

Line 121 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.

This form has fields without LABEL elements or TITLE attributes.

Line 121 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 121 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input placeholder="eg. 23 Example Street" type="text"

class="form-text-input-join"

value=""

name="custloc_address" id="custloc_address" /></td>

</tr>

<td colspan="2" class="tipsHolder"><span class="tips">Allows us to find take-away restaurants in your area. You can add additional addresses after joining.</span></td>

</tr>

<span class="form-label label">Name for this address:</span></td>

<td>

This form control has no associated LABEL element.

Line 131 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.

This form has fields without LABEL elements or TITLE attributes.

Line 131 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 131 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input placeholder="eg. Home" maxlength="20" type="text"

class="form-text-input-join"

name="custloc_name" id="custloc_name" /></td>

</tr>

<td colspan="2" class="tipsHolder"><span class="tips">Allows you to easily switch between multiple addresses (example: work, home, a friend's house)</span></td>

</tr>

<span class="form-label label">Phone number:</span></td>

<td>

This form control has no associated LABEL element.

Line 141 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.

This form has fields without LABEL elements or TITLE attributes.

Line 141 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 141 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input type="text"

class="form-text-input-join"

value=""

name="custloc_phone" id="custloc_phone" /></td>

</tr>

<td colspan="2" class="tipsHolder"><span class="tips">Allows a restaurant to contact you about your order.</span></td>

</tr>

<span class="form-label label">Mobile number:</span></td>

<td>

This form control has no associated LABEL element.

Line 151 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.

This form has fields without LABEL elements or TITLE attributes.

Line 151 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 151 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input type="text"

class="form-text-input-join"

value=""

name="cust_mobile" id="cust_mobile" /></td>

</tr>

<td colspan="2" class="tipsHolder" class

Duplicate specification of attribute "class".

Line 157 HTML Validation

="tipsHolder"><span class="tips">Provide an alternate contact number that can be used if you cannot be reached on your normal phone number.</span></td>

</tr>

<span class="form-label label">Email Address:</span></td>

<td>

This form control has no associated LABEL element.

Line 161 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.

This form has fields without LABEL elements or TITLE attributes.

Line 161 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 161 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input type="text"

class="form-text-input-join"

value=""

name="custloc_email" id="custloc_email" /></td>

</tr>

<span class="form-label label">Re-enter email address:</span></td>

<td>

This form control has no associated LABEL element.

Line 168 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.

This form has fields without LABEL elements or TITLE attributes.

Line 168 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 168 Usability.gov 13:5

Make sure each INPUT field has an associated LABEL tag describing the field.

<input type="text"

class="form-text-input-join"

name="temp_cust_email" id="temp_cust_email" /></td>

</tr>

<td colspan="2" class="tipsHolder"><span class="tips">An email will be sent to this address to activate your membership. Choose an address you can access immediately.</span></td>

</tr>

<span class="form-label label">I prefer email:</span>

<i></i>

<span>to be plain text</span>

LABEL elements should be associated with other controls using FOR attributes.

Line 186 WCAG2 A 4.1.2

Add a FOR attribute set to the ID of the associated control. Some screen readers ignore labels without FOR attributes.

LABEL elements should be not be blank.

Line 186 WCAG2 A 4.1.2

Add text to the LABEL describing the associated control.

LABEL must not contain other LABEL elements.

Line 186 HTML Validation

<label>

</spa

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

Line 187 HTML Validation

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

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

Line 187 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 187 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 187 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 187 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.

n>

<input type="radio" class="middle" id="format_html" checked

The name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified.

Line 190 HTML Validation

value="html" name="custloc_email_format" />

<i></i>

<span>with colour and images (HTML)</span>

</label>

</span>

</div>

</td>

</tr>

IMG tags must have an ALT attribute.

Line 202 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 202 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 class="form-image" src="http://static.hungryhouse.co.uk/images/buttons/activate_membership.gif?30"

Required attribute "alt" not specified.

Line 202 HTML Validation

/>

<span>continue</span>

</butto

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

Line 204 HTML Validation

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

Line 204 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 204 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 204 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.

n>

</td>

</tr>

</table>

</for

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

Line 208 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 208 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 208 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 208 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.

m>

</td></tr></table></div>

</div><div class="panelb"><div></div></div>

</div></div>

<div class="panel" style="width:380px" id="panel-what-are-the-benefits-of-being-a-member"><div class="paneli"><div class="panelt"><div class="panelTitle">Why become a member?</div></div>

<ul>

<li>Save your details for faster, easier ordering</li>

<li>One-click re-ordering of previous meals from your order history</li>

<li>'Like' restaurants, to make it easier to find them next time you visit hungryhouse</li>

<li>Leave personalized notes about any restaurant - eg "their pork balls are amazing!!"</li>

<li>Opt-in for email updates of special offers and new menus in your area</li>

</ul>

<p>Own a restaurant? <a href="restaurateurs2">Contact us</a></p>

</td></tr></table></div>

</div><div class="panelb"><div></div></div>

</div></div>

<div class="panel" style="width:380px" id="panel-need-activation-code"><div class="paneli"><div class="panelt"><div class="panelTitle">Need new activation code?</div></div>

Already created your membership but can't find the email containing

your activation code?<br />

<br />

If you enter your email address, we can send a new activation code to you.<br />

<br />

Check your Junk Mail folder before requesting a new code.<br />

<div class="form-label label">Email address:</div>

IMG tags must have an ALT attribute.

Line 254 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 254 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 class="form-image" src="http://static.hungryhouse.co.uk/images/new_buttons/continue2.gif?30"

Required attribute "alt" not specified.

Line 254 HTML Validation

/>

<span>submit</span>

</butto

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

Line 256 HTML Validation

n>

</form>

</div>

</td></tr></table></div>

</div><div class="panelb"><div></div></div>

</div></div>

AREA tags must have an ALT attribute.

Line 272 Section 508 1194.22 (a) WCAG2 A F65

Non-sighted users can't see pictures, so each AREA should have an ALT attribute describing the function of the link, which is read aloud by screen readers.

AREA tags must have an ALT attribute.

Line 273 Section 508 1194.22 (a) WCAG2 A F65

Non-sighted users can't see pictures, so each AREA should have an ALT attribute describing the function of the link, which is read aloud by screen readers.

</map>

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

Line 275 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.

</div>

</div> </div>

</div>

</div>

</div>

</div>

<span class="signinInfo">Sign in with your Member ID and your password...</span>

<label for="sign-in-form-login"><span>Member ID</span></label>

<a href="member_reminder">Forgotten your ID?</a>

</p>

<label for="sign-in-form-password"><span>Password</span></label>

Search engines cannot index areas of sites that require a log in.

Line 316 Google Blogs

<a href="password_reset">Forgotten your Password?</a>

</p>

<p>

Sign in using secure mode</a>

</p>

</div>

<span class="signinInfo">Sign in with your Facebook account</span><div class=" "><a href="/openid/redirect/facebook/" class="facebookSignIn"><span>Facebook</span></a></div></div></form>

<div class="signinJoin">Not a member? <a href="join" title="Join to Hungryhouse">Join now</a></div>

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

$(document).ready(function() {

$("#guest-login-button").attr("href", $("#guest-login-button").attr("rel")).fancybox({

autoScale : false,

fitToView : false,

height : 575,

width : 440,

fitToView : false,

autoSize : false,

closeClick : false,

wrapCSS : "fancybox-signin",

closeBtn : true,

openEffect : "fade",

closeEffect : "fade",

padding : 0

});

</script>

</div>

<h3>Get our mobile app</h3>

<a href="https://play.google.com/store/apps/details?id=com.hungryhouse" class="app-andr"><i class="iconAndroid"></i><span style="display: none !important;">Android App</span></a>

Provide a way to skip repetitive navigation links.

Line 358 Section 508 1194.22 (o)

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="http://itunes.apple.com/gb/app/hungryhouse-order-takeaway/id400227047?mt=8" class="app-apple"><i class="iconApple"></i><span style="display: none !important;">iPhone App</span></a>

</div>

<h3>Company</h3>

<ul>

<li><a href="about"><span>About Us</span></a></li>

<li><a href="recommendations" rel="nofollow"><span>Recommend Restaurant</span></a></li>

<li><a href="restaurateurs" rel="nofollow"><span>Restaurateurs</span></a></li>

<li><a href="partner" rel="nofollow"><span>Partner Portal</span></a></li>

<li><a href="contact" rel="nofollow"><span>Contact Us</span></a></li>

<li><a href="sitemap"><span>Sitemap</span></a></li>

<li><a href="faq" title="FAQ" rel="nofollow"><span>Frequently Asked Questions</span></a></li>

<li><a href="faq/Gift%20Vouchers" title="Gift Vouchers"><span>Gift Vouchers</span></a></li>

</ul>

</div>

<h3>Now serving</h3>

<ul>

<li><a href="birmingham_takeaway"><span>Birmingham</span></a></li>

<li><a href="brighton_takeaway"><span>Brighton</span></a></li>

<li><a href="glasgow_takeaway"><span>Glasgow</span></a></li>

<li><a href="leeds_takeaway"><span>Leeds</span></a></li>

<li><a href="leicester_takeaway"><span>Leicester</span></a></li>

<li><a href="liverpool_takeaway"><span>Liverpool</span></a></li>

<li><a href="london_takeaway"><span>London</span></a></li>

<li><a href="manchester_takeaway"><span>Manchester</span></a></li>

<li><a href="newcastle_takeaway"><span>Newcastle</span></a></li>

<li><a href="sheffield_takeaway"><span>Sheffield</span></a></li>

<li><a href="takeaway"><span>All locations</span></a></li>

</ul>

</div>

<h3>Best Takeaways</h3>

<ul>

<li><a href="indian_takeaway"><span>Indian Takeaway</span></a></li>

<li><a href="chinese_takeaway"><span>Chinese Takeaway</span></a></li>

<li><a href="thai_takeaway"><span>Thai Takeaway</span></a></li>

<li><a href="pizza"><span>Pizza Delivery</span></a></li>

<li><a href="sushi"><span>Sushi Delivery</span></a></li>

<li><a href="halal_takeaway"><span>Halal Takeaway</span></a></li>

<li><a href="takeaway"><span>All takeaway cuisines</span></a></li>

</ul>

</div>

<a class="footLinkNectar" href="/news/Awards/hungryhouse-takes-top-business-award_875" title="hungryhouse takes top business award" rel="nofollow"><span>hungryhouse takes top business award</span></a>

Provide a way to skip repetitive navigation links.

Line 410 Section 508 1194.22 (o)

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 class="footLinkSmartest" title="Hungryhouse recognised as one of the UK's smartest small businesses" href="/news/Press%20releases/hungryhouse-recognised-as-one-of-the-uk-s-smartest-small-businesses_701" rel="nofollow"><span>Hungryhouse recognised as one of the UKâ€™s smartest small businesses</span></a>

<a class="footLinkReward" title="Hungryhouse rewarded for its innovation" href="/news/What%20We%20Are%20Excited%20About/hungryhouse-rewarded-for-its-innovation_688" rel="nofollow"><span>Hungryhouse rewarded for its innovation</span></a>

<a class="footLinkDragon" href="/news/Videos/hungryhouse-co-uk-tempts-dragons-to-a-takeaway_156" title="Dragons Den" rel="nofollow"><span>Dragons Den</span></a>

</div>

<a href="/privacy" title="Privacy Policy" rel="nofollow">Privacy Policy</a>

|

Provide a way to skip repetitive navigation links.

Line 418 Section 508 1194.22 (o)

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="/terms" title="Terms of Use" rel="nofollow">Terms of Use</a>

| <a href="/cookies" title="About cookies" rel="nofollow">About Cookies</a>

| <a href="http://hungryhouse.co.uk/~m/">Mobile site</a>

<br />

</div>

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

Line 426 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.

</a>

</div>

<li>Save your details for faster, easier ordering</li>

<li>One-click re-ordering of previous meals from your order history</li>

<li>'Like' restaurants, to make it easier to find them next time you visit hungryhouse</li>

<li>Leave personalized notes about any restaurant - eg "their pork balls are amazing!!"</li>

<li>Opt-in for email updates of special offers and new menus in your area</li>

</ul>

<p>Own a restaurant? <a href="restaurateurs2">Contact us</a></p></div></div>

$(document).ready(function() {

if($("#guest-join-button").length){

var tmp = $("#membership-benefits").clone();

$("#membership-benefits-wrapper").remove();

$("#guest-join-button").after(tmp);

$("#guest-join-button").tooltip({

position: ["bottom", "right"],

offset: [14, 0],

opacity: 0.8

});

}

});

</script>

(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><script type="text/javascript">var _gaq = _gaq || [];

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

_gaq.push(['_setDomainName', '.hungryhouse.co.uk']);

_gaq.push(['_addIgnoredRef', 'hungryhouse.co.uk']);

_gaq.push(['_setAllowAnchor', true]);

_gaq.push(['_setCampaignCookieTimeout', '2592000000']);_gaq.push('_setVar', 'rebrand');_gaq.push('_setCustomVar', 1, 'design', 'rebrand');_gaq.push(['_trackPageview', location.pathname + '+enterdetails/' + location.search]);

$_hh.tracking.base.register("ga", ['event', 'trans', 'ga', 'gajax', 'error'], function (type, category, action, opt_label, opt_value) {

opt_value = parseInt(opt_value);

if (isNaN(opt_value)) {

opt_value = null;

}

if (type != "trans") {

_gaq.push(["_trackEvent", category, action, opt_label, opt_value]);

}

});

</script>

/* <![CDATA[ */

var google_conversion_id = 996602259;

var google_conversion_label = "ZaqACN2U1QQQk-Ob2wM";

var google_custom_params = window.google_tag_params;

var google_remarketing_only = true;

/* ]]> */

</script>

</script>

</div>

</noscript>

$('body').append('<s

An attribute specification must start with a name or name token.

Line 499 HTML Validation

Element "sc" undefined.

Line 499 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.

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

Line 499 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 499 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 499 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.

c'+'rip'+'t async="" src="http://www.dwin1.com/3898.js"></

Delimiter "'" invalid: only S separators and TAGC allowed here.

Line 499 HTML Validation

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

Line 499 HTML Validation

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

Line 499 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 499 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 499 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.

s'+'cri'+'pt>');

});

</scrip

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

Line 501 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 501 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 501 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 501 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.

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

$(window).load(function() {

(function() {

var d=document,

h=d.getElementsByTagName('head')[0],

s=d.createElement('script');

s.type='text/javascript';

s.async=true;

s.src='http://static.hungryhouse.co.uk/include/tracking.maxemail.js?30';

h.appendChild(s);

}());

}); </script><script type="text/javascript"><!--

document.write(unescape("%3Cscript id='pap_x2s6df8d' src='http://pap.hungryhouse.co.uk/scripts/trackjs.js' type='text/javascript'%3E%3C/script%3E"));//-->

</script>

try {

PostAffTracker.setAccountId('default1');

PostAffTracker.disableTrackingMethod('F');

PostAffTracker.track();

} catch (err) { }

//-->

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

$(window).load(function() {

var d=document,

h=d.getElementsByTagName('body')[0],

s=d.createElement('img');

s.src='/os.gif?os=http://hungryhouse.co.uk/join&(none)';

s.width=1; s.height=1;

s.className='os';

s.alt='';

h.appendChild(s);

});

</script>

var GoSquared = {};

GoSquared.acct = 'GSN-178163-Q';

(function (w) {

function gs() {

w._gstc_lt = +new Date;

var d = document, g = d.createElement('script');

g.type = 'text/javascript';

g.src = '//d1l6p2sc9645hc.cloudfront.net/tracker.js';

var s = d.getElementsByTagName('script')[0];

s.parentNode.insertBefore(g, s);

}

w.addEventListener ? w.addEventListener('load', gs, false) : w.attachEvent('onload', gs);

})(window);

</script>

<scrip

Required attribute "type" not specified.

Line 549 HTML Validation

t>$(document).ready(function(){$('input[type="checkbox"], input[type="radio"]').uniform();})</script><scrip

Required attribute "type" not specified.

Line 549 HTML Validation

t>

if($_hh.deviceInfo.type.ipad){

$(".tooltip , .tooltipPopup, .toolTipPopup").each(function(){

$(this).unbind();

});

}

</script><script type="text/javascript">$(document).ready(function(){

if($_hh){

if($_hh.deviceInfo){

if($_hh.deviceInfo.type){

for(var i in $_hh.deviceInfo.type){

if($_hh.deviceInfo.type[i]){

$("body").addClass("deviceMobile");

break;

}

});</script><script type="text/javascript">if(!NREUMQ.f){NREUMQ.f=function(){NREUMQ.push(["load",new Date().getTime()]);var e=document.createElement("script");e.type="text/javascript";e.src=(("http:"===document.location.protocol)?"http:":"https:")+"//"+"js-agent.newrelic.com/nr-100.js";document.body.appendChild(e);if(NREUMQ.a)NREUMQ.a();};NREUMQ.a=window.onload;window.onload=NREUMQ.f;};NREUMQ.push(["nrfj","beacon-4.newrelic.com","377a1d8613","2325961","YlEHbUZZXRVWU0wIW1sbJkxHTFwLGHpXCFoaUQtNUUpsAlJEWQhYRg==",0,36,new Date().getTime(),"","","","",""]);</script></body></html>

URL:	http://hungryhouse.co.uk/join
HTTP Status:	200 OK
MIME Type:	text/html
Last Modified:	Mon, 01 Jan 1601 00:00:00 GMT
Download Time:	Less than a second
Cookies:	PHPSESSID=ucjmldv9c9rnu3r0lev w=rebrand hh_os=dktvxpy4i
Size:	30 KB
Page Weight:	30 KB (total size of HTML, CSS, JavaScript and images)
Depth:	1 clicks from home page
Charset:	UTF-8
Forms:	3 forms containing 16 controls
HTTP Headers:	11 headers Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Connection: keep-alive Date: Fri, 28 Mar 2014 08:45:28 GMT Pragma: no-cache Server: nginx Set-Cookie: hh_os=dktvxpy4i; expires=Thu, 26-Jun-2014 08:45:28 GMT; path=/; domain=.hungryhouse.co.uk Transfer-Encoding: chunked X-Do-Mobile-Redirect: 0 X-Is-Mobile: 0 X-Os_Ua: noos X-Server-Id: 10
Links In:	1 pages http://hungryhouse.co.uk/takeaways/southwark-waterloo-bermondsey-borough-se1
Links Out:	52 links http://hungryhouse.co.uk/ http://hungryhouse.co.uk/join http://hungryhouse.co.uk/?signin=yes http://hungryhouse.co.uk/search_loading http://hungryhouse.co.uk/contact http://hungryhouse.co.uk/ordertracking http://hungryhouse.co.uk/main.php?menu=Join&submenu=activate_membership_direct http://hungryhouse.co.uk/faq/Using%20Facebook%20to%20Sign%20in http://hungryhouse.co.uk/restaurateurs2 http://www.safebuy.org.uk/certificate/dc3a56b5-33a6-4f1e-bab8-1f2677a046b7.html http://www.instantssl.com/ http://hungryhouse.co.uk/member_reminder http://hungryhouse.co.uk/password_reset https://hungryhouse.co.uk/?signin=yes http://hungryhouse.co.uk/openid/redirect/facebook/ https://play.google.com/store/apps/details?id=com.hungryhouse http://itunes.apple.com/gb/app/hungryhouse-order-takeaway/id400227047?mt=8 http://hungryhouse.co.uk/blog/dragons-den/ http://hungryhouse.co.uk/about http://hungryhouse.co.uk/recommendations http://hungryhouse.co.uk/restaurateurs http://hungryhouse.co.uk/partner http://hungryhouse.co.uk/blog/ http://hungryhouse.co.uk/sitemap http://hungryhouse.co.uk/faq http://hungryhouse.co.uk/faq/Gift%20Vouchers http://hungryhouse.co.uk/birmingham_takeaway http://hungryhouse.co.uk/brighton_takeaway http://hungryhouse.co.uk/glasgow_takeaway http://hungryhouse.co.uk/leeds_takeaway http://hungryhouse.co.uk/leicester_takeaway http://hungryhouse.co.uk/liverpool_takeaway http://hungryhouse.co.uk/london_takeaway http://hungryhouse.co.uk/manchester_takeaway http://hungryhouse.co.uk/newcastle_takeaway http://hungryhouse.co.uk/sheffield_takeaway http://hungryhouse.co.uk/takeaway http://hungryhouse.co.uk/indian_takeaway http://hungryhouse.co.uk/chinese_takeaway http://hungryhouse.co.uk/thai_takeaway http://hungryhouse.co.uk/pizza http://hungryhouse.co.uk/sushi http://hungryhouse.co.uk/halal_takeaway http://hungryhouse.co.uk/news/Awards/hungryhouse-takes-top-business-award_875 http://hungryhouse.co.uk/news/Press%20releases/hungryhouse-recognised-as-one-of-the-uk-s-smartest-small-businesses_701 http://hungryhouse.co.uk/news/What%20We%20Are%20Excited%20About/hungryhouse-rewarded-for-its-innovation_688 http://hungryhouse.co.uk/news/Videos/hungryhouse-co-uk-tempts-dragons-to-a-takeaway_156 http://hungryhouse.co.uk/privacy http://hungryhouse.co.uk/terms http://hungryhouse.co.uk/cookies http://hungryhouse.co.uk/~m http://www.deliveryhero.com/
Images:	7 images http://static.hungryhouse.co.uk/images/buttons/activate_membership.gif?30 NaN KB http://static.hungryhouse.co.uk/images/new_buttons/continue2.gif?30 NaN KB http://static.hungryhouse.co.uk/images/misc/logobarbig-secure-takeaway.gif?30 NaN KB http://static.hungryhouse.co.uk/images/checkout/verified_securecode.gif?30 NaN KB http://static.hungryhouse.co.uk/images/ads/dh_black.png?30 NaN KB http://googleads.g.doubleclick.net/pagead/viewthroughconversion/996602259/?value=0&label=ZaqACN2U1QQQk-Ob2wM&guid=ON&script=0 NaN KB http://hungryhouse.co.uk/os.gif?os=http://hungryhouse.co.uk/join&(none) NaN KB
CSS:	0 files
JavaScript:	0 files

Issues:	42 issues found on 113 lines

HTML Document