HTML Document

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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.

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.

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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.

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

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

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

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

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.

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

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.

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

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.

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

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.

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

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.

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.

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.

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

Either tags are not nested properly, or the element must contain other elements. For example, the HEAD element must contain a TITLE element and the TR element must contain a TD element.

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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.

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

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

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

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

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

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

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

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

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

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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.

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

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

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

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

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

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

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

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

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

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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.

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

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

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

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

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

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

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

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

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

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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.

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

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

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

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

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

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

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

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

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

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.

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

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

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

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

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

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

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

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

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

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

Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

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

Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler.