All Directories and Files

The following tables contain the count and list of all directories and files.

HTM and HTML Files

HTML files should contain the most significant content and have meaningful names. The following tables contain the count and list of files.

JSP Files

JSP files are regarded as equivalent to HTML files. The following tables contain the count and list of files.

GIF Files

These image files can be indexed by image search websites. They should have meaningful names. The following tables contain the count and list of files.

JPG and JPEG Files

These image files can be indexed by image search websites. They should have meaningful names. The following tables contain the count and list of files.

JS Files

These Javascript files are usually ignored by search websites. The following tables contain the count and list of files.

CSS Files

These files are usually ignored by search websites. The following tables contain the count and list of files.

Errors

Serious errors encountered during the retrieval.

Messages

Messages encountered during the retrieval.

Statistics

File sizes, MIME types and download speeds.

Search Engine Visibility

The following elements are important in search website visibility.

The TITLE element:

 WhyWaitForever Accessibility Statement 

The META element DESCRIPTION attribute:

This page describes the accessibility support implemented in the WhyWaitForever 
website.

The META element KEYWORDS attribute:

accessibility

The H1 elements:

<h1 class="chaptert">
<a name="icaccess"></a> WhyWaitForever Accessibility Statement </h1>

The H2 elements:

<h2 class="access">
<a name="icaccess-s1"></a> Access keys </h2>
<h2 class="access">
<a name="icaccess-s2"></a> Standards compliance </h2>
<h2 class="access">
<a name="icaccess-s3"></a> Navigation aids </h2>
<h2 class="access">
<a name="icaccess-s4"></a> Images </h2>
<h2 class="access">
<a name="icaccess-s5"></a> Visual design </h2>
<h2 class="access">
<a name="icaccess-s6"></a> Accessibility references </h2>
<h2 class="access">
<a name="icaccess-s7"></a> Accessibility software </h2>

The H3 elements:

The information in the paragraph elements:

This is the accessibility statement for the
WhyWaitForever Consultancy
(www.whywaitforever.com/consultancy) website.
Visitors with questions or comments can email WhyWaitForever at
webmaster@whywaitforever.com .
When a page is viewed in a browser it is possible to
move directly to a specific link by typing key combinations.
On Windows, the
ALT
+ an access key can be used.
On Macs, the
Control
+ an access key can be used.
All pages on this web site have the following access keys defined:
Access key
0
- Accessibility Statement
Access key
1
- Home
Access key
2
- Consultancy
Access key
3
- Technology
Access key
4
- Contact
Access key
5
- Site map
Access key
6
- Privacy Statement
Access key
7
- Terms and Conditions of use of website
Access key
p
- Printer friendly version
Access key
x
- XHTML version
WhyWaitForever believe all pages on this site comply with all the
Bobby Guidelines .
Accessibility features that can be measured have been tested for compliance.
WhyWaitForever believe all pages on this site follow
W3C Web Content
Accessibility Guidelines  and in particular
comply with all the priority 1, 2 and 3
W3C Web Content
Accessibility Checklist .
Accessibility features that can be measured have been tested for compliance.
WhyWaitForever believe the consultancy pages on this site validate as
HTML 4.01 strict
and can be independently validated using
W3C Markup Validation Service .
Where possible, text rich pages on this site use structured semantic markup.
H1
tags are used for page titles.
H2
tags are used for main titles.
H3
tags are used for sub titles.
In these text rich pages JAWS users can skip to the next section by pressing
the key combination
ALT+INSERT+3
.
WhyWaitForever has created a style sheet in addition to
using the standard "Steely" which is available from
W3C Core Styles .
The website contains a
sitemap .
Each page contains menu links.
Each page contains "breadcrumb" navigation.
All content images used in this site include descriptive ALT attributes.
Complex images include
LONGDESC
attributes or
inline descriptions to explain the significance of each image to non-visual 
readers.
This website uses cascading style sheets for visual layout.
This website uses relative font sizes, compatible with the
user-specified "text size" option in visual browsers.
This website is still readable if the browser or
browsing device used does not support stylesheets.
The website has been designed to allow for printing
without truncation of information.
It is best to check using print preview and adjust using the print
page setup margins if necessary.
W3C Web
Accessibility Initiative  which aims for access by everyone.
W3C Web Content
Accessibility Guidelines  which explains the reasons behind each guideline.
W3C Web Content
Accessibility Techniques  which explains implementation details.
W3C Web Content
Accessibility Checklist  which provides summary information.
JAWS
for Windows  a screen reader for Windows.
Lynx  a text browser.
Opera  a general browser
with accessibility related features.

The anchor (links) elements:

<a name="icaccess"></a>
<a href="index.html" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> WhyWaitForever Consultancy
(www.whywaitforever.com/consultancy)</a> website.
<a href="mailto:webmaster@whywaitforever.com" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> webmaster@whywaitforever.com </a>
<a name="icaccess-s1"></a>
<a name="icaccess-s2"></a>
<a href="http://bobby.watchfire.com/bobby/html/en/browsereport.jsp" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Bobby Guidelines </a>
<a href="http://www.w3.org/TR/WCAG10/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;"> W3C Web Content
Accessibility Guidelines </a> and in particular
<a href="http://www.w3.org/TR/WCAG10/full-checklist.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
Accessibility Checklist </a>.
<a href="http://www.w3.org/TR/html4/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;"> HTML 4.01 strict </a>
<a href="http://validator.w3.org/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> W3C Markup Validation Service </a>
<a href="http://www.w3.org/StyleSheets/Core/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Core Styles </a>
<a name="icaccess-s3"></a>
<a href="sitemap.html" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> sitemap </a>
<a name="icaccess-s4"></a>
<a name="icaccess-s5"></a>
<a name="icaccess-s6"></a>
<a href="http://www.w3c.org/WAI/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> W3C Web
Accessibility Initiative </a> which aims for access by everyone.
<a href="http://www.w3.org/TR/WCAG10/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;"> W3C Web Content
Accessibility Guidelines </a> which explains the reasons behind each guideline.
<a href="http://www.w3.org/TR/WCAG10-TECHS/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
Accessibility Techniques </a> which explains implementation details.
<a href="http://www.w3.org/TR/WCAG10/full-checklist.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
Accessibility Checklist </a> which provides summary information.
<a name="icaccess-s7"></a>
<a href="http://www.freedomscientific.com/fs_downloads/jaws.asp" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> JAWS
for Windows </a> a screen reader for Windows.
<a href="http://lynx.browser.org/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> Lynx </a>
<a href="http://www.opera.com/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> Opera </a>

The image elements:

The META element COPYRIGHT attribute:

Copyright © 2005-2007 WhyWaitforever

Validation

Spelling check and Tidy can return warning or error messages. Search websites looks for correctly spelled words. A website can be down ranked for poor spelling and grammar. It is important all errors and warnings are addressed.

The spelling check messages:

The Tidy messages:

Tidy (vers 4th August 2000) 
Doctype given is "-//W3C//DTD HTML 4.01//EN"
Document content looks like HTML 4.01 Transitional
no warnings or errors were found

The HTML or equivalent page with line counts (for use with messages):

     1	<!DOCTYPE html
     2	PUBLIC "-//W3C//DTD HTML 4.01//EN" 
"http://www.w3.org/TR/html4/strict.dtd">
     3	<html><head>
     4	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
     5	<title> WhyWaitForever Accessibility Statement </title><link 
rel="stylesheet" href="css/main-portlet.css" type="text/css"><link 
rel="stylesheet" href="css/main-layout.css" type="text/css"><link rev="made" 
title="WhyWaitForever" href="mailto:sales@whywaitforever.co.uk"><meta 
name="description" content="This page describes the accessibility support 
implemented in the WhyWaitForever website."><meta name="keywords" 
content="accessibility"><meta name="copyright" content="Copyright &copy; 
2005-2007 WhyWaitforever"><meta name="generator" content="WhyWaitForever 
extending DocBook XSL Stylesheets V1.65.1"></head><body><div class="body"><div 
class="header"><span class="header"> WhyWaitForever </span><span 
class="headerLeft"> IT Consultancy </span></div><div class="layout-01"><div 
class="portlet-01"><div class="chapter"><h1 class="chaptert"><a 
name="icaccess"></a> WhyWaitForever Accessibility Statement </h1><p 
class="chapterp"> This is the accessibility statement for the
     6	<a href="index.html" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> WhyWaitForever Consultancy
     7	(www.whywaitforever.com/consultancy)</a> website.
     8	Visitors with questions or comments can email WhyWaitForever at
     9	<a href="mailto:webmaster@whywaitforever.com" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> webmaster@whywaitforever.com </a>.</p><div class="section"><h2 
class="access"><a name="icaccess-s1"></a> Access keys </h2><p class="access"> 
When a page is viewed in a browser it is possible to
    10	move directly to a specific link by typing key combinations.
    11	On Windows, the <span class="emphasis"><em>ALT</em></span> + an access 
key can be used.
    12	On Macs, the <span class="emphasis"><em>Control</em></span> + an access 
key can be used. </p><p>All pages on this web site have the following access 
keys defined:</p><div class="itemizedlist"><ul><li><p> Access key <span 
class="emphasis"><em>0</em></span> - Accessibility Statement </p></li><li><p> 
Access key <span class="emphasis"><em>1</em></span> - Home </p></li><li><p> 
Access key <span class="emphasis"><em>2</em></span> - Consultancy 
</p></li><li><p> Access key <span class="emphasis"><em>3</em></span> - 
Technology </p></li><li><p> Access key <span class="emphasis"><em>4</em></span> 
- Contact </p></li><li><p> Access key <span class="emphasis"><em>5</em></span> 
- Site map </p></li><li><p> Access key <span class="emphasis"><em>6</em></span> 
- Privacy Statement </p></li><li><p> Access key <span 
class="emphasis"><em>7</em></span> - Terms and Conditions of use of website 
</p></li><li><p> Access key <span class="emphasis"><em>p</em></span> - Printer 
friendly version </p></li><li><p> Access key <span 
class="emphasis"><em>x</em></span> - XHTML version 
</p></li></ul></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s2"></a> Standards compliance </h2><div class="orderedlist"><ol 
type="1"><li><p> WhyWaitForever believe all pages on this site comply with all 
the
    13	<a href="http://bobby.watchfire.com/bobby/html/en/browsereport.jsp" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Bobby Guidelines </a>.
    14	Accessibility features that can be measured have been tested for 
compliance.
    15	</p></li><li><p> WhyWaitForever believe all pages on this site follow
    16	<a href="http://www.w3.org/TR/WCAG10/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    17	Accessibility Guidelines </a> and in particular
    18	comply with all the priority 1, 2 and 3
    19	<a href="http://www.w3.org/TR/WCAG10/full-checklist.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    20	Accessibility Checklist </a>.
    21	Accessibility features that can be measured have been tested for 
compliance.
    22	</p></li><li><p> WhyWaitForever believe the consultancy pages on this 
site validate as
    23	<a href="http://www.w3.org/TR/html4/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> HTML 4.01 strict </a>
    24	and can be independently validated using
    25	<a href="http://validator.w3.org/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;"> W3C Markup Validation 
Service </a>.
    26	</p></li><li><p> Where possible, text rich pages on this site use 
structured semantic markup.
    27	<span class="emphasis"><em>H1</em></span> tags are used for page titles.
    28	<span class="emphasis"><em>H2</em></span> tags are used for main titles.
    29	<span class="emphasis"><em>H3</em></span> tags are used for sub titles.
    30	In these text rich pages JAWS users can skip to the next section by 
pressing
    31	the key combination <span class="emphasis"><em>ALT+INSERT+3</em></span>.
    32	</p></li><li><p> WhyWaitForever has created a style sheet in addition to
    33	using the standard "Steely" which is available from
    34	<a href="http://www.w3.org/StyleSheets/Core/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Core Styles </a>.
    35	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s3"></a> Navigation aids </h2><div class="orderedlist"><ol 
type="1"><li><p> The website contains a <a href="sitemap.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> sitemap </a>. </p></li><li><p> Each page contains menu links. 
</p></li><li><p> Each page contains "breadcrumb" navigation. 
</p></li></ol></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s4"></a> Images </h2><div class="orderedlist"><ol 
type="1"><li><p> All content images used in this site include descriptive ALT 
attributes.
    36	</p></li><li><p> Complex images include <span 
class="emphasis"><em>LONGDESC</em></span> attributes or
    37	inline descriptions to explain the significance of each image to 
non-visual readers.
    38	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s5"></a> Visual design </h2><div class="orderedlist"><ol 
type="1"><li><p> This website uses cascading style sheets for visual layout.
    39	</p></li><li><p> This website uses relative font sizes, compatible with 
the
    40	user-specified "text size" option in visual browsers. </p></li><li><p> 
This website is still readable if the browser or
    41	browsing device used does not support stylesheets. </p></li><li><p> The 
website has been designed to allow for printing
    42	without truncation of information.
    43	It is best to check using print preview and adjust using the print
    44	page setup margins if necessary. </p></li></ol></div></div><div 
class="section"><h2 class="access"><a name="icaccess-s6"></a> Accessibility 
references </h2><div class="orderedlist"><ol type="1"><li><p> <a 
href="http://www.w3c.org/WAI/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> W3C Web
    45	Accessibility Initiative </a> which aims for access by everyone.
    46	</p></li><li><p> <a href="http://www.w3.org/TR/WCAG10/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    47	Accessibility Guidelines </a> which explains the reasons behind each 
guideline.
    48	</p></li><li><p> <a href="http://www.w3.org/TR/WCAG10-TECHS/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    49	Accessibility Techniques </a> which explains implementation details.
    50	</p></li><li><p> <a 
href="http://www.w3.org/TR/WCAG10/full-checklist.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    51	Accessibility Checklist </a> which provides summary information.
    52	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s7"></a> Accessibility software </h2><div 
class="orderedlist"><ol type="1"><li><p> <a 
href="http://www.freedomscientific.com/fs_downloads/jaws.asp" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> JAWS
    53	for Windows </a> a screen reader for Windows.
    54	</p></li><li><p> <a href="http://lynx.browser.org/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Lynx </a> a text browser.
    55	</p></li><li><p> <a href="http://www.opera.com/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Opera </a> a general browser
    56	with accessibility related features.
    57	</p></li></ol></div></div></div></div></div><div class="footer"><span 
class="footer"> WhyWaitForever </span><span class="headerLeft"> 
(www.whywaitforever.com/consultancy)</span></div></div></body></html>

The script elements:

The style (CSS) inline elements:

The link (CSS) external elements:

<link rel="stylesheet" href="css/main-portlet.css" type="text/css">
<link rel="stylesheet" href="css/main-layout.css" type="text/css">
<link rev="made" title="WhyWaitForever" 
href="mailto:sales@whywaitforever.co.uk">

The comments elements:

Search Engine Visibility

The following elements are important in search website visibility.

The TITLE element:

 WhyWaitForever Accessibility Statement 

The META element DESCRIPTION attribute:

This page describes the accessibility support implemented in the WhyWaitForever 
website.

The META element KEYWORDS attribute:

accessibility

The H1 elements:

<h1 class="chaptert">
<a name="icaccess"/> WhyWaitForever Accessibility Statement </h1>

The H2 elements:

<h2 class="access">
<a id="icaccess-s1"/> Access keys </h2>
<h2 class="access">
<a id="icaccess-s2"/> Standards compliance </h2>
<h2 class="access">
<a id="icaccess-s3"/> Navigation aids </h2>
<h2 class="access">
<a id="icaccess-s4"/> Images </h2>
<h2 class="access">
<a id="icaccess-s5"/> Visual design </h2>
<h2 class="access">
<a id="icaccess-s6"/> Accessibility references </h2>
<h2 class="access">
<a id="icaccess-s7"/> Accessibility software </h2>

The H3 elements:

The information in the paragraph elements:

Computer Keyboard lying on a desk.
This is the accessibility statement for the
WhyWaitForever Consultancy
(www.whywaitforever.com/consultancy) website.
Visitors with questions or comments can email WhyWaitForever at
webmaster@whywaitforever.com .
When a page is viewed in a browser it is possible to
move directly to a specific link by typing key combinations.
On Windows, the
ALT
+ an access key can be used.
On Macs, the
Control
+ an access key can be used.
All pages on this web site have the following access keys defined:
Access key
0
- Accessibility Statement
Access key
1
- Home
Access key
2
- Consultancy
Access key
3
- Technology
Access key
4
- Contact
Access key
5
- Site map
Access key
6
- Privacy Statement
Access key
7
- Terms and Conditions of use of website
Access key
p
- Printer friendly version
Access key
x
- XHTML version
WhyWaitForever believe all pages on this site comply with all the
Bobby Guidelines .
Accessibility features that can be measured have been tested for compliance.
WhyWaitForever believe all pages on this site follow
W3C Web Content
Accessibility Guidelines  and in particular
comply with all the priority 1, 2 and 3
W3C Web Content
Accessibility Checklist .
Accessibility features that can be measured have been tested for compliance.
WhyWaitForever believe the consultancy pages on this site validate as
HTML 4.01 strict
and can be independently validated using
W3C Markup Validation Service .
Where possible, text rich pages on this site use structured semantic markup.
H1
tags are used for page titles.
H2
tags are used for main titles.
H3
tags are used for sub titles.
In these text rich pages JAWS users can skip to the next section by pressing
the key combination
ALT+INSERT+3
.
WhyWaitForever has created a style sheet in addition to
using the standard "Steely" which is available from
W3C Core Styles .
The website contains a
sitemap .
Each page contains menu links.
Each page contains "breadcrumb" navigation.
All content images used in this site include descriptive ALT attributes.
Complex images include
LONGDESC
attributes or
inline descriptions to explain the significance of each image to non-visual 
readers.
This website uses cascading style sheets for visual layout.
This website uses relative font sizes, compatible with the
user-specified "text size" option in visual browsers.
This website is still readable if the browser or
browsing device used does not support stylesheets.
The website has been designed to allow for printing
without truncation of information.
It is best to check using print preview and adjust using the print
page setup margins if necessary.
W3C Web
Accessibility Initiative  which aims for access by everyone.
W3C Web Content
Accessibility Guidelines  which explains the reasons behind each guideline.
W3C Web Content
Accessibility Techniques  which explains implementation details.
W3C Web Content
Accessibility Checklist  which provides summary information.
JAWS
for Windows  a screen reader for Windows.
Lynx  a text browser.
Opera  a general browser
with accessibility related features.

The anchor (links) elements:

<a href="http://www.whywaitforever.com/consultancy/ld-d0e24.html" 
target="longdesc">D</a>
<a accesskey="1" href="index-xhtml.html" class="menuheader" title="To Home"> 
Home </a>
<a accesskey="2" href="consultancy-xhtml.html" class="menuheader" title="To 
Consultancy"> Consultancy </a>
<a accesskey="3" href="technology-xhtml.html" class="menuheader" title="To 
Technologies"> Technology </a>
<a accesskey="4" href="contact-xhtml.html" class="menuheader" title="To 
Contact"> Contact </a>
<a accesskey="5" href="sitemap-xhtml.html" class="menuheader" title="To 
Sitemap"> Sitemap </a>
<a accesskey="1" href="index-xhtml.html" class="navigation" title="To Home"> 
Home </a>
<a accesskey="0" href="accessibility-xhtml.html" class="navigation" title="To 
Accessibility Statement"> Accessibility </a>
<a name="icaccess"/> WhyWaitForever Accessibility Statement </h1>
<p class="chapterp"> This is the accessibility statement for the
<a href="index.html"> WhyWaitForever Consultancy
(www.whywaitforever.com/consultancy)</a> website.
<a href="mailto:webmaster@whywaitforever.com"> webmaster@whywaitforever.com </a>
<a id="icaccess-s1"/> Access keys </h2>
<p class="access"> When a page is viewed in a browser it is possible to
move directly to a specific link by typing key combinations.
On Windows, the
<span class="emphasis">
<em>ALT</em>
</span> + an access key can be used.
On Macs, the
<span class="emphasis">
<em>Control</em>
</span> + an access key can be used. </p>
<p>All pages on this web site have the following access keys defined:</p>
<div class="itemizedlist">
<ul>
<li>
<p> Access key
<span class="emphasis">
<em>0</em>
</span> - Accessibility Statement </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>1</em>
</span> - Home </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>2</em>
</span> - Consultancy </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>3</em>
</span> - Technology </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>4</em>
</span> - Contact </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>5</em>
</span> - Site map </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>6</em>
</span> - Privacy Statement </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>7</em>
</span> - Terms and Conditions of use of website </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>p</em>
</span> - Printer friendly version </p></li>
<li>
<p> Access key
<span class="emphasis">
<em>x</em>
</span> - XHTML version </p></li></ul>
</div>
</div>
<div class="section">
<h2 class="access">
<a id="icaccess-s2"/> Standards compliance </h2>
<div class="orderedlist">
<ol type="1">
<li>
<p> WhyWaitForever believe all pages on this site comply with all the
<a href="http://bobby.watchfire.com/bobby/html/en/browsereport.jsp"> Bobby 
Guidelines </a>
<a href="http://www.w3.org/TR/WCAG10/"> W3C Web Content
Accessibility Guidelines </a> and in particular
<a href="http://www.w3.org/TR/WCAG10/full-checklist.html"> W3C Web Content
Accessibility Checklist </a>.
<a href="http://www.w3.org/TR/html4/"> HTML 4.01 strict </a>
<a href="http://validator.w3.org/"> W3C Markup Validation Service </a>
<a href="http://www.w3.org/StyleSheets/Core/"> W3C Core Styles </a>
<a id="icaccess-s3"/> Navigation aids </h2>
<div class="orderedlist">
<ol type="1">
<li>
<p> The website contains a
<a href="sitemap.html"> sitemap </a>
<a id="icaccess-s4"/> Images </h2>
<div class="orderedlist">
<ol type="1">
<li>
<p> All content images used in this site include descriptive ALT attributes.
</p></li>
<li>
<p> Complex images include
<span class="emphasis">
<em>LONGDESC</em>
</span> attributes or
inline descriptions to explain the significance of each image to non-visual 
readers.
</p></li></ol>
</div>
</div>
<div class="section">
<h2 class="access">
<a id="icaccess-s5"/> Visual design </h2>
<div class="orderedlist">
<ol type="1">
<li>
<p> This website uses cascading style sheets for visual layout.
</p></li>
<li>
<p> This website uses relative font sizes, compatible with the
user-specified "text size" option in visual browsers. </p></li>
<li>
<p> This website is still readable if the browser or
browsing device used does not support stylesheets. </p></li>
<li>
<p> The website has been designed to allow for printing
without truncation of information.
It is best to check using print preview and adjust using the print
page setup margins if necessary. </p></li></ol>
</div>
</div>
<div class="section">
<h2 class="access">
<a id="icaccess-s6"/> Accessibility references </h2>
<div class="orderedlist">
<ol type="1">
<li>
<p>
<a href="http://www.w3c.org/WAI/"> W3C Web
Accessibility Initiative </a> which aims for access by everyone.
<a href="http://www.w3.org/TR/WCAG10/"> W3C Web Content
Accessibility Guidelines </a> which explains the reasons behind each guideline.
<a href="http://www.w3.org/TR/WCAG10-TECHS/"> W3C Web Content
Accessibility Techniques </a> which explains implementation details.
<a href="http://www.w3.org/TR/WCAG10/full-checklist.html"> W3C Web Content
Accessibility Checklist </a> which provides summary information.
<a id="icaccess-s7"/> Accessibility software </h2>
<div class="orderedlist">
<ol type="1">
<li>
<p>
<a href="http://www.freedomscientific.com/fs_downloads/jaws.asp"> JAWS
for Windows </a> a screen reader for Windows.
<a href="http://lynx.browser.org/"> Lynx </a>
<a href="http://www.opera.com/"> Opera </a>
<a accesskey="0" href="accessibility-xhtml.html" class="menuheader" title="To 
Accessibility Statement"> Accessibility </a>
<a accesskey="6" href="privacy-xhtml.html" class="menuheader" title="To 
Privacy"> Privacy </a>
<a accesskey="7" href="terms-xhtml.html" class="menuheader" title="To Website 
Terms and Conditions"> Terms </a>
<a accesskey="p" href="accessibility-print.html" class="menuheader" title="To 
Printer friendly version"> Printable </a>
<a accesskey="h" href="accessibility.html" class="menuheader" title="To HTML 
version"> HTML </a>
<a accesskey="x" href="accessibility-xhtml.html" class="menuheader" title="To 
XHTML version"> XHTML </a>

The image elements:

<img src="images/keyboard.jpg" height="138" alt="Computer Keyboard" 
longdesc="ld-d0e24.html"/>

The META element COPYRIGHT attribute:

Copyright © 2005-2007 WhyWaitforever

Validation

Spelling check and Tidy can return warning or error messages. Search websites looks for correctly spelled words. A website can be down ranked for poor spelling and grammar. It is important all errors and warnings are addressed.

The spelling check messages:

The Tidy messages:

Tidy (vers 4th August 2000) 
Doctype given is "-//W3C//DTD XHTML 1.0 Transitional//EN"
Document content looks like XHTML 1.0 Transitional
no warnings or errors were found

The HTML or equivalent page with line counts (for use with messages):

     1	<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
     2	<!DOCTYPE html
     3	PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
     4	<html xmlns="http://www.w3.org/1999/xhtml"><head><title> WhyWaitForever 
Accessibility Statement </title><link rel="stylesheet" 
href="css/main-portlet.css" type="text/css"/><link rel="stylesheet" 
href="css/main-layout.css" type="text/css"/><link rev="made" 
title="WhyWaitForever" href="mailto:sales@whywaitforever.co.uk"/><meta 
name="description" content="This page describes the accessibility support 
implemented in the WhyWaitForever website."/><meta name="keywords" 
content="accessibility"/><meta name="copyright" content="Copyright © 2005-2007 
WhyWaitforever"/><meta name="generator" content="WhyWaitForever extending 
DocBook XSL Stylesheets V1.65.1"/></head><body><div class="body"><div 
class="header"><span class="header"> WhyWaitForever </span><span 
class="headerLeft"> IT Consultancy </span></div><div class="banner"><div 
class="mediaobject"><img src="images/keyboard.jpg" height="138" alt="Computer 
Keyboard" longdesc="ld-d0e24.html"/><div class="longdesc-link" 
align="right"><br clear="all"/><span class="longdesc-link">[<a 
href="http://www.whywaitforever.com/consultancy/ld-d0e24.html" 
target="longdesc">D</a>]</span></div><div class="caption"><p 
class="imagecaption">Computer Keyboard lying on a 
desk.</p></div></div></div><div class="menuheader"><span class="menup"><a 
accesskey="1" href="index-xhtml.html" class="menuheader" title="To Home"> Home 
</a></span><span class="menup"><a accesskey="2" href="consultancy-xhtml.html" 
class="menuheader" title="To Consultancy"> Consultancy </a></span><span 
class="menup"><a accesskey="3" href="technology-xhtml.html" class="menuheader" 
title="To Technologies"> Technology </a></span><span class="menup"><a 
accesskey="4" href="contact-xhtml.html" class="menuheader" title="To Contact"> 
Contact </a></span><span class="menup"><a accesskey="5" 
href="sitemap-xhtml.html" class="menuheader" title="To Sitemap"> Sitemap 
</a></span></div><div class="navigation"><span class="navigation"><a 
accesskey="1" href="index-xhtml.html" class="navigation" title="To Home"> Home 
</a></span><span class="navigation-text">  &gt;  </span><span 
class="navigation"><a accesskey="0" href="accessibility-xhtml.html" 
class="navigation" title="To Accessibility Statement"> Accessibility 
</a></span><span class="navigation-text"> </span></div><div 
class="layout-01"><div class="portlet-01"><div class="chapter"><h1 
class="chaptert"><a name="icaccess"/> WhyWaitForever Accessibility Statement 
</h1><p class="chapterp"> This is the accessibility statement for the
     5	<a href="index.html"> WhyWaitForever Consultancy
     6	(www.whywaitforever.com/consultancy)</a> website.
     7	Visitors with questions or comments can email WhyWaitForever at
     8	<a href="mailto:webmaster@whywaitforever.com"> 
webmaster@whywaitforever.com </a>.</p><div class="section"><h2 
class="access"><a id="icaccess-s1"/> Access keys </h2><p class="access"> When a 
page is viewed in a browser it is possible to
     9	move directly to a specific link by typing key combinations.
    10	On Windows, the <span class="emphasis"><em>ALT</em></span> + an access 
key can be used.
    11	On Macs, the <span class="emphasis"><em>Control</em></span> + an access 
key can be used. </p><p>All pages on this web site have the following access 
keys defined:</p><div class="itemizedlist"><ul><li><p> Access key <span 
class="emphasis"><em>0</em></span> - Accessibility Statement </p></li><li><p> 
Access key <span class="emphasis"><em>1</em></span> - Home </p></li><li><p> 
Access key <span class="emphasis"><em>2</em></span> - Consultancy 
</p></li><li><p> Access key <span class="emphasis"><em>3</em></span> - 
Technology </p></li><li><p> Access key <span class="emphasis"><em>4</em></span> 
- Contact </p></li><li><p> Access key <span class="emphasis"><em>5</em></span> 
- Site map </p></li><li><p> Access key <span class="emphasis"><em>6</em></span> 
- Privacy Statement </p></li><li><p> Access key <span 
class="emphasis"><em>7</em></span> - Terms and Conditions of use of website 
</p></li><li><p> Access key <span class="emphasis"><em>p</em></span> - Printer 
friendly version </p></li><li><p> Access key <span 
class="emphasis"><em>x</em></span> - XHTML version 
</p></li></ul></div></div><div class="section"><h2 class="access"><a 
id="icaccess-s2"/> Standards compliance </h2><div class="orderedlist"><ol 
type="1"><li><p> WhyWaitForever believe all pages on this site comply with all 
the
    12	<a href="http://bobby.watchfire.com/bobby/html/en/browsereport.jsp"> 
Bobby Guidelines </a>.
    13	Accessibility features that can be measured have been tested for 
compliance.
    14	</p></li><li><p> WhyWaitForever believe all pages on this site follow
    15	<a href="http://www.w3.org/TR/WCAG10/"> W3C Web Content
    16	Accessibility Guidelines </a> and in particular
    17	comply with all the priority 1, 2 and 3
    18	<a href="http://www.w3.org/TR/WCAG10/full-checklist.html"> W3C Web 
Content
    19	Accessibility Checklist </a>.
    20	Accessibility features that can be measured have been tested for 
compliance.
    21	</p></li><li><p> WhyWaitForever believe the consultancy pages on this 
site validate as
    22	<a href="http://www.w3.org/TR/html4/"> HTML 4.01 strict </a>
    23	and can be independently validated using
    24	<a href="http://validator.w3.org/"> W3C Markup Validation Service </a>.
    25	</p></li><li><p> Where possible, text rich pages on this site use 
structured semantic markup.
    26	<span class="emphasis"><em>H1</em></span> tags are used for page titles.
    27	<span class="emphasis"><em>H2</em></span> tags are used for main titles.
    28	<span class="emphasis"><em>H3</em></span> tags are used for sub titles.
    29	In these text rich pages JAWS users can skip to the next section by 
pressing
    30	the key combination <span class="emphasis"><em>ALT+INSERT+3</em></span>.
    31	</p></li><li><p> WhyWaitForever has created a style sheet in addition to
    32	using the standard "Steely" which is available from
    33	<a href="http://www.w3.org/StyleSheets/Core/"> W3C Core Styles </a>.
    34	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
id="icaccess-s3"/> Navigation aids </h2><div class="orderedlist"><ol 
type="1"><li><p> The website contains a <a href="sitemap.html"> sitemap </a>. 
</p></li><li><p> Each page contains menu links. </p></li><li><p> Each page 
contains "breadcrumb" navigation. </p></li></ol></div></div><div 
class="section"><h2 class="access"><a id="icaccess-s4"/> Images </h2><div 
class="orderedlist"><ol type="1"><li><p> All content images used in this site 
include descriptive ALT attributes.
    35	</p></li><li><p> Complex images include <span 
class="emphasis"><em>LONGDESC</em></span> attributes or
    36	inline descriptions to explain the significance of each image to 
non-visual readers.
    37	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
id="icaccess-s5"/> Visual design </h2><div class="orderedlist"><ol 
type="1"><li><p> This website uses cascading style sheets for visual layout.
    38	</p></li><li><p> This website uses relative font sizes, compatible with 
the
    39	user-specified "text size" option in visual browsers. </p></li><li><p> 
This website is still readable if the browser or
    40	browsing device used does not support stylesheets. </p></li><li><p> The 
website has been designed to allow for printing
    41	without truncation of information.
    42	It is best to check using print preview and adjust using the print
    43	page setup margins if necessary. </p></li></ol></div></div><div 
class="section"><h2 class="access"><a id="icaccess-s6"/> Accessibility 
references </h2><div class="orderedlist"><ol type="1"><li><p> <a 
href="http://www.w3c.org/WAI/"> W3C Web
    44	Accessibility Initiative </a> which aims for access by everyone.
    45	</p></li><li><p> <a href="http://www.w3.org/TR/WCAG10/"> W3C Web Content
    46	Accessibility Guidelines </a> which explains the reasons behind each 
guideline.
    47	</p></li><li><p> <a href="http://www.w3.org/TR/WCAG10-TECHS/"> W3C Web 
Content
    48	Accessibility Techniques </a> which explains implementation details.
    49	</p></li><li><p> <a 
href="http://www.w3.org/TR/WCAG10/full-checklist.html"> W3C Web Content
    50	Accessibility Checklist </a> which provides summary information.
    51	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
id="icaccess-s7"/> Accessibility software </h2><div class="orderedlist"><ol 
type="1"><li><p> <a 
href="http://www.freedomscientific.com/fs_downloads/jaws.asp"> JAWS
    52	for Windows </a> a screen reader for Windows.
    53	</p></li><li><p> <a href="http://lynx.browser.org/"> Lynx </a> a text 
browser.
    54	</p></li><li><p> <a href="http://www.opera.com/"> Opera </a> a general 
browser
    55	with accessibility related features.
    56	</p></li></ol></div></div></div></div></div><div 
class="menufooter"><span class="menup"><a accesskey="0" 
href="accessibility-xhtml.html" class="menuheader" title="To Accessibility 
Statement"> Accessibility </a></span><span class="menup"><a accesskey="6" 
href="privacy-xhtml.html" class="menuheader" title="To Privacy"> Privacy 
</a></span><span class="menup"><a accesskey="7" href="terms-xhtml.html" 
class="menuheader" title="To Website Terms and Conditions"> Terms 
</a></span><span class="menup"><a accesskey="p" href="accessibility-print.html" 
class="menuheader" title="To Printer friendly version"> Printable 
</a></span><span class="menup"><a accesskey="h" href="accessibility.html" 
class="menuheader" title="To HTML version"> HTML </a></span><span 
class="menup"><a accesskey="x" href="accessibility-xhtml.html" 
class="menuheader" title="To XHTML version"> XHTML </a></span></div><div 
class="footer"><span class="footer"> Websites For The Future </span><span 
class="headerLeft"> Accessibility. </span><span class="headerMiddle"> 
Usability. </span><span class="headerRight"> Visibility. 
</span></div></div></body></html>

The script elements:

The style (CSS) inline elements:

The link (CSS) external elements:

<link rel="stylesheet" href="css/main-portlet.css" type="text/css"/>
<link rel="stylesheet" href="css/main-layout.css" type="text/css"/>
<link rev="made" title="WhyWaitForever" 
href="mailto:sales@whywaitforever.co.uk"/>

The comments elements:

Search Engine Visibility

The following elements are important in search website visibility.

The TITLE element:

 WhyWaitForever Accessibility Statement 

The META element DESCRIPTION attribute:

This page describes the accessibility support implemented in the WhyWaitForever 
website.

The META element KEYWORDS attribute:

accessibility

The H1 elements:

<h1 class="chaptert">
<a name="icaccess"></a> WhyWaitForever Accessibility Statement </h1>

The H2 elements:

<h2 class="access">
<a name="icaccess-s1"></a> Access keys </h2>
<h2 class="access">
<a name="icaccess-s2"></a> Standards compliance </h2>
<h2 class="access">
<a name="icaccess-s3"></a> Navigation aids </h2>
<h2 class="access">
<a name="icaccess-s4"></a> Images </h2>
<h2 class="access">
<a name="icaccess-s5"></a> Visual design </h2>
<h2 class="access">
<a name="icaccess-s6"></a> Accessibility references </h2>
<h2 class="access">
<a name="icaccess-s7"></a> Accessibility software </h2>

The H3 elements:

The information in the paragraph elements:

Computer Keyboard lying on a desk.
This is the accessibility statement for the
WhyWaitForever Consultancy
(www.whywaitforever.com/consultancy) website.
Visitors with questions or comments can email WhyWaitForever at
webmaster@whywaitforever.com .
When a page is viewed in a browser it is possible to
move directly to a specific link by typing key combinations.
On Windows, the
ALT
+ an access key can be used.
On Macs, the
Control
+ an access key can be used.
All pages on this web site have the following access keys defined:
Access key
0
- Accessibility Statement
Access key
1
- Home
Access key
2
- Consultancy
Access key
3
- Technology
Access key
4
- Contact
Access key
5
- Site map
Access key
6
- Privacy Statement
Access key
7
- Terms and Conditions of use of website
Access key
p
- Printer friendly version
Access key
x
- XHTML version
WhyWaitForever believe all pages on this site comply with all the
Bobby Guidelines .
Accessibility features that can be measured have been tested for compliance.
WhyWaitForever believe all pages on this site follow
W3C Web Content
Accessibility Guidelines  and in particular
comply with all the priority 1, 2 and 3
W3C Web Content
Accessibility Checklist .
Accessibility features that can be measured have been tested for compliance.
WhyWaitForever believe the consultancy pages on this site validate as
HTML 4.01 strict
and can be independently validated using
W3C Markup Validation Service .
Where possible, text rich pages on this site use structured semantic markup.
H1
tags are used for page titles.
H2
tags are used for main titles.
H3
tags are used for sub titles.
In these text rich pages JAWS users can skip to the next section by pressing
the key combination
ALT+INSERT+3
.
WhyWaitForever has created a style sheet in addition to
using the standard "Steely" which is available from
W3C Core Styles .
The website contains a
sitemap .
Each page contains menu links.
Each page contains "breadcrumb" navigation.
All content images used in this site include descriptive ALT attributes.
Complex images include
LONGDESC
attributes or
inline descriptions to explain the significance of each image to non-visual 
readers.
This website uses cascading style sheets for visual layout.
This website uses relative font sizes, compatible with the
user-specified "text size" option in visual browsers.
This website is still readable if the browser or
browsing device used does not support stylesheets.
The website has been designed to allow for printing
without truncation of information.
It is best to check using print preview and adjust using the print
page setup margins if necessary.
W3C Web
Accessibility Initiative  which aims for access by everyone.
W3C Web Content
Accessibility Guidelines  which explains the reasons behind each guideline.
W3C Web Content
Accessibility Techniques  which explains implementation details.
W3C Web Content
Accessibility Checklist  which provides summary information.
JAWS
for Windows  a screen reader for Windows.
Lynx  a text browser.
Opera  a general browser
with accessibility related features.

The anchor (links) elements:

<a href="ld-d0e23.html" target="longdesc">D</a>
<a accesskey="1" href="index.html" class="menuheader" title="To Home" 
onMouseover="window.status='To Home';return true;" 
onMouseout="window.status='';return true;"> Home </a>
<a accesskey="2" href="consultancy.html" class="menuheader" title="To 
Consultancy" onMouseover="window.status='To Consultancy';return true;" 
onMouseout="window.status='';return true;"> Consultancy </a>
<a accesskey="3" href="technology.html" class="menuheader" title="To 
Technologies" onMouseover="window.status='To Technologies';return true;" 
onMouseout="window.status='';return true;"> Technology </a>
<a accesskey="4" href="contact.html" class="menuheader" title="To Contact" 
onMouseover="window.status='To Contact';return true;" 
onMouseout="window.status='';return true;"> Contact </a>
<a accesskey="5" href="sitemap.html" class="menuheader" title="To Sitemap" 
onMouseover="window.status='To Sitemap';return true;" 
onMouseout="window.status='';return true;"> Sitemap </a>
<a accesskey="1" href="index.html" class="navigation" title="To Home" 
onMouseover="window.status='To Home';return true;" 
onMouseout="window.status='';return true;"> Home </a>
<a accesskey="0" href="accessibility.html" class="navigation" title="To 
Accessibility Statement" onMouseover="window.status='To Accessibility 
Statement';return true;" onMouseout="window.status='';return true;"> 
Accessibility </a>
<a name="icaccess"></a>
<a href="index.html" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> WhyWaitForever Consultancy
(www.whywaitforever.com/consultancy)</a> website.
<a href="mailto:webmaster@whywaitforever.com" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> webmaster@whywaitforever.com </a>
<a name="icaccess-s1"></a>
<a name="icaccess-s2"></a>
<a href="http://bobby.watchfire.com/bobby/html/en/browsereport.jsp" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Bobby Guidelines </a>
<a href="http://www.w3.org/TR/WCAG10/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;"> W3C Web Content
Accessibility Guidelines </a> and in particular
<a href="http://www.w3.org/TR/WCAG10/full-checklist.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
Accessibility Checklist </a>.
<a href="http://www.w3.org/TR/html4/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;"> HTML 4.01 strict </a>
<a href="http://validator.w3.org/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> W3C Markup Validation Service </a>
<a href="http://www.w3.org/StyleSheets/Core/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Core Styles </a>
<a name="icaccess-s3"></a>
<a href="sitemap.html" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> sitemap </a>
<a name="icaccess-s4"></a>
<a name="icaccess-s5"></a>
<a name="icaccess-s6"></a>
<a href="http://www.w3c.org/WAI/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> W3C Web
Accessibility Initiative </a> which aims for access by everyone.
<a href="http://www.w3.org/TR/WCAG10/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;"> W3C Web Content
Accessibility Guidelines </a> which explains the reasons behind each guideline.
<a href="http://www.w3.org/TR/WCAG10-TECHS/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
Accessibility Techniques </a> which explains implementation details.
<a href="http://www.w3.org/TR/WCAG10/full-checklist.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
Accessibility Checklist </a> which provides summary information.
<a name="icaccess-s7"></a>
<a href="http://www.freedomscientific.com/fs_downloads/jaws.asp" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> JAWS
for Windows </a> a screen reader for Windows.
<a href="http://lynx.browser.org/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> Lynx </a>
<a href="http://www.opera.com/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> Opera </a>
<a accesskey="0" href="accessibility.html" class="menuheader" title="To 
Accessibility Statement" onMouseover="window.status='To Accessibility 
Statement';return true;" onMouseout="window.status='';return true;"> 
Accessibility </a>
<a accesskey="6" href="privacy.html" class="menuheader" title="To Privacy" 
onMouseover="window.status='To Privacy';return true;" 
onMouseout="window.status='';return true;"> Privacy </a>
<a accesskey="7" href="terms.html" class="menuheader" title="To Website Terms 
and Conditions" onMouseover="window.status='To Website Terms and 
Conditions';return true;" onMouseout="window.status='';return true;"> Terms </a>
<a accesskey="p" href="accessibility-print.html" class="menuheader" title="To 
Printer friendly version" onMouseover="window.status='To Printer friendly 
version';return true;" onMouseout="window.status='';return true;"> Printable 
</a>
<a accesskey="h" href="accessibility.html" class="menuheader" title="To HTML 
version" onMouseover="window.status='To HTML version';return true;" 
onMouseout="window.status='';return true;"> HTML </a>
<a accesskey="x" href="accessibility-xhtml.html" class="menuheader" title="To 
XHTML version" onMouseover="window.status='To XHTML version';return true;" 
onMouseout="window.status='';return true;"> XHTML </a>

The image elements:

<img src="images/keyboard.jpg" height="138" alt="Computer Keyboard" 
longdesc="ld-d0e23.html">

The META element COPYRIGHT attribute:

Copyright © 2005-2007 WhyWaitforever

Validation

Spelling check and Tidy can return warning or error messages. Search websites looks for correctly spelled words. A website can be down ranked for poor spelling and grammar. It is important all errors and warnings are addressed.

The spelling check messages:

The Tidy messages:

Tidy (vers 4th August 2000) 
Doctype given is "-//W3C//DTD HTML 4.01//EN"
Document content looks like HTML 4.01 Transitional
no warnings or errors were found

The HTML or equivalent page with line counts (for use with messages):

     1	<!DOCTYPE html
     2	PUBLIC "-//W3C//DTD HTML 4.01//EN" 
"http://www.w3.org/TR/html4/strict.dtd">
     3	<html><head>
     4	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
     5	<title> WhyWaitForever Accessibility Statement </title><link 
rel="stylesheet" href="css/main-portlet.css" type="text/css"><link 
rel="stylesheet" href="css/main-layout.css" type="text/css"><link rev="made" 
title="WhyWaitForever" href="mailto:sales@whywaitforever.co.uk"><meta 
name="description" content="This page describes the accessibility support 
implemented in the WhyWaitForever website."><meta name="keywords" 
content="accessibility"><meta name="copyright" content="Copyright &copy; 
2005-2007 WhyWaitforever"><meta name="generator" content="WhyWaitForever 
extending DocBook XSL Stylesheets V1.65.1"></head><body><div class="body"><div 
class="header"><span class="header"> WhyWaitForever </span><span 
class="headerLeft"> IT Consultancy </span></div><div class="banner"><div 
class="mediaobject"><img src="images/keyboard.jpg" height="138" alt="Computer 
Keyboard" longdesc="ld-d0e23.html"><div class="longdesc-link" align="right"><br 
clear="all"><span class="longdesc-link">[<a href="ld-d0e23.html" 
target="longdesc">D</a>]</span></div><div class="caption"><p 
class="imagecaption">Computer Keyboard lying on a 
desk.</p></div></div></div><div class="menuheader"><span class="menup"><a 
accesskey="1" href="index.html" class="menuheader" title="To Home" 
onMouseover="window.status='To Home';return true;" 
onMouseout="window.status='';return true;"> Home </a></span><span 
class="menup"><a accesskey="2" href="consultancy.html" class="menuheader" 
title="To Consultancy" onMouseover="window.status='To Consultancy';return 
true;" onMouseout="window.status='';return true;"> Consultancy </a></span><span 
class="menup"><a accesskey="3" href="technology.html" class="menuheader" 
title="To Technologies" onMouseover="window.status='To Technologies';return 
true;" onMouseout="window.status='';return true;"> Technology </a></span><span 
class="menup"><a accesskey="4" href="contact.html" class="menuheader" title="To 
Contact" onMouseover="window.status='To Contact';return true;" 
onMouseout="window.status='';return true;"> Contact </a></span><span 
class="menup"><a accesskey="5" href="sitemap.html" class="menuheader" title="To 
Sitemap" onMouseover="window.status='To Sitemap';return true;" 
onMouseout="window.status='';return true;"> Sitemap </a></span></div><div 
class="navigation"><span class="navigation"><a accesskey="1" href="index.html" 
class="navigation" title="To Home" onMouseover="window.status='To Home';return 
true;" onMouseout="window.status='';return true;"> Home </a></span><span 
class="navigation-text">  &gt;  </span><span class="navigation"><a 
accesskey="0" href="accessibility.html" class="navigation" title="To 
Accessibility Statement" onMouseover="window.status='To Accessibility 
Statement';return true;" onMouseout="window.status='';return true;"> 
Accessibility </a></span><span class="navigation-text"> </span></div><div 
class="layout-01"><div class="portlet-01"><div class="chapter"><h1 
class="chaptert"><a name="icaccess"></a> WhyWaitForever Accessibility Statement 
</h1><p class="chapterp"> This is the accessibility statement for the
     6	<a href="index.html" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> WhyWaitForever Consultancy
     7	(www.whywaitforever.com/consultancy)</a> website.
     8	Visitors with questions or comments can email WhyWaitForever at
     9	<a href="mailto:webmaster@whywaitforever.com" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> webmaster@whywaitforever.com </a>.</p><div class="section"><h2 
class="access"><a name="icaccess-s1"></a> Access keys </h2><p class="access"> 
When a page is viewed in a browser it is possible to
    10	move directly to a specific link by typing key combinations.
    11	On Windows, the <span class="emphasis"><em>ALT</em></span> + an access 
key can be used.
    12	On Macs, the <span class="emphasis"><em>Control</em></span> + an access 
key can be used. </p><p>All pages on this web site have the following access 
keys defined:</p><div class="itemizedlist"><ul><li><p> Access key <span 
class="emphasis"><em>0</em></span> - Accessibility Statement </p></li><li><p> 
Access key <span class="emphasis"><em>1</em></span> - Home </p></li><li><p> 
Access key <span class="emphasis"><em>2</em></span> - Consultancy 
</p></li><li><p> Access key <span class="emphasis"><em>3</em></span> - 
Technology </p></li><li><p> Access key <span class="emphasis"><em>4</em></span> 
- Contact </p></li><li><p> Access key <span class="emphasis"><em>5</em></span> 
- Site map </p></li><li><p> Access key <span class="emphasis"><em>6</em></span> 
- Privacy Statement </p></li><li><p> Access key <span 
class="emphasis"><em>7</em></span> - Terms and Conditions of use of website 
</p></li><li><p> Access key <span class="emphasis"><em>p</em></span> - Printer 
friendly version </p></li><li><p> Access key <span 
class="emphasis"><em>x</em></span> - XHTML version 
</p></li></ul></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s2"></a> Standards compliance </h2><div class="orderedlist"><ol 
type="1"><li><p> WhyWaitForever believe all pages on this site comply with all 
the
    13	<a href="http://bobby.watchfire.com/bobby/html/en/browsereport.jsp" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Bobby Guidelines </a>.
    14	Accessibility features that can be measured have been tested for 
compliance.
    15	</p></li><li><p> WhyWaitForever believe all pages on this site follow
    16	<a href="http://www.w3.org/TR/WCAG10/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    17	Accessibility Guidelines </a> and in particular
    18	comply with all the priority 1, 2 and 3
    19	<a href="http://www.w3.org/TR/WCAG10/full-checklist.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    20	Accessibility Checklist </a>.
    21	Accessibility features that can be measured have been tested for 
compliance.
    22	</p></li><li><p> WhyWaitForever believe the consultancy pages on this 
site validate as
    23	<a href="http://www.w3.org/TR/html4/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> HTML 4.01 strict </a>
    24	and can be independently validated using
    25	<a href="http://validator.w3.org/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;"> W3C Markup Validation 
Service </a>.
    26	</p></li><li><p> Where possible, text rich pages on this site use 
structured semantic markup.
    27	<span class="emphasis"><em>H1</em></span> tags are used for page titles.
    28	<span class="emphasis"><em>H2</em></span> tags are used for main titles.
    29	<span class="emphasis"><em>H3</em></span> tags are used for sub titles.
    30	In these text rich pages JAWS users can skip to the next section by 
pressing
    31	the key combination <span class="emphasis"><em>ALT+INSERT+3</em></span>.
    32	</p></li><li><p> WhyWaitForever has created a style sheet in addition to
    33	using the standard "Steely" which is available from
    34	<a href="http://www.w3.org/StyleSheets/Core/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Core Styles </a>.
    35	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s3"></a> Navigation aids </h2><div class="orderedlist"><ol 
type="1"><li><p> The website contains a <a href="sitemap.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> sitemap </a>. </p></li><li><p> Each page contains menu links. 
</p></li><li><p> Each page contains "breadcrumb" navigation. 
</p></li></ol></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s4"></a> Images </h2><div class="orderedlist"><ol 
type="1"><li><p> All content images used in this site include descriptive ALT 
attributes.
    36	</p></li><li><p> Complex images include <span 
class="emphasis"><em>LONGDESC</em></span> attributes or
    37	inline descriptions to explain the significance of each image to 
non-visual readers.
    38	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s5"></a> Visual design </h2><div class="orderedlist"><ol 
type="1"><li><p> This website uses cascading style sheets for visual layout.
    39	</p></li><li><p> This website uses relative font sizes, compatible with 
the
    40	user-specified "text size" option in visual browsers. </p></li><li><p> 
This website is still readable if the browser or
    41	browsing device used does not support stylesheets. </p></li><li><p> The 
website has been designed to allow for printing
    42	without truncation of information.
    43	It is best to check using print preview and adjust using the print
    44	page setup margins if necessary. </p></li></ol></div></div><div 
class="section"><h2 class="access"><a name="icaccess-s6"></a> Accessibility 
references </h2><div class="orderedlist"><ol type="1"><li><p> <a 
href="http://www.w3c.org/WAI/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> W3C Web
    45	Accessibility Initiative </a> which aims for access by everyone.
    46	</p></li><li><p> <a href="http://www.w3.org/TR/WCAG10/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    47	Accessibility Guidelines </a> which explains the reasons behind each 
guideline.
    48	</p></li><li><p> <a href="http://www.w3.org/TR/WCAG10-TECHS/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    49	Accessibility Techniques </a> which explains implementation details.
    50	</p></li><li><p> <a 
href="http://www.w3.org/TR/WCAG10/full-checklist.html" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> W3C Web Content
    51	Accessibility Checklist </a> which provides summary information.
    52	</p></li></ol></div></div><div class="section"><h2 class="access"><a 
name="icaccess-s7"></a> Accessibility software </h2><div 
class="orderedlist"><ol type="1"><li><p> <a 
href="http://www.freedomscientific.com/fs_downloads/jaws.asp" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> JAWS
    53	for Windows </a> a screen reader for Windows.
    54	</p></li><li><p> <a href="http://lynx.browser.org/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Lynx </a> a text browser.
    55	</p></li><li><p> <a href="http://www.opera.com/" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Opera </a> a general browser
    56	with accessibility related features.
    57	</p></li></ol></div></div></div></div></div><div 
class="menufooter"><span class="menup"><a accesskey="0" 
href="accessibility.html" class="menuheader" title="To Accessibility Statement" 
onMouseover="window.status='To Accessibility Statement';return true;" 
onMouseout="window.status='';return true;"> Accessibility </a></span><span 
class="menup"><a accesskey="6" href="privacy.html" class="menuheader" title="To 
Privacy" onMouseover="window.status='To Privacy';return true;" 
onMouseout="window.status='';return true;"> Privacy </a></span><span 
class="menup"><a accesskey="7" href="terms.html" class="menuheader" title="To 
Website Terms and Conditions" onMouseover="window.status='To Website Terms and 
Conditions';return true;" onMouseout="window.status='';return true;"> Terms 
</a></span><span class="menup"><a accesskey="p" href="accessibility-print.html" 
class="menuheader" title="To Printer friendly version" 
onMouseover="window.status='To Printer friendly version';return true;" 
onMouseout="window.status='';return true;"> Printable </a></span><span 
class="menup"><a accesskey="h" href="accessibility.html" class="menuheader" 
title="To HTML version" onMouseover="window.status='To HTML version';return 
true;" onMouseout="window.status='';return true;"> HTML </a></span><span 
class="menup"><a accesskey="x" href="accessibility-xhtml.html" 
class="menuheader" title="To XHTML version" onMouseover="window.status='To 
XHTML version';return true;" onMouseout="window.status='';return true;"> XHTML 
</a></span></div><div class="footer"><span class="footer"> Websites For The 
Future </span><span class="headerLeft"> Accessibility. </span><span 
class="headerMiddle"> Usability. </span><span class="headerRight"> Visibility. 
</span></div></div></body></html>

The script elements:

The style (CSS) inline elements:

The link (CSS) external elements:

<link rel="stylesheet" href="css/main-portlet.css" type="text/css">
<link rel="stylesheet" href="css/main-layout.css" type="text/css">
<link rev="made" title="WhyWaitForever" 
href="mailto:sales@whywaitforever.co.uk">

The comments elements:

Search Engine Visibility

The following elements are important in search website visibility.

The TITLE element:

 WhyWaitForever Consultancy 

The META element DESCRIPTION attribute:

This page describes the consultancy undertaken by WhyWaitForever.

The META element KEYWORDS attribute:

consultancy

The H1 elements:

<h1 class="common">
<a name="iconsultancy-c1"></a> Consultancy </h1>

The H2 elements:

<h2 class="common">
<a name="iconsultancy-c1s1"></a> Search Visibility </h2>
<h2 class="common">
<a name="iconsultancy-c1s2"></a> Business Intelligence Gathering </h2>
<h2 class="common">
<a name="iconsultancy-c1s3"></a> Email Marketing, Visitor Sources and Analysis 
</h2>
<h2 class="common">
<a name="iconsultancy-c1s4"></a> Web Analytics </h2>
<h2 class="common">
<a name="iconsultancy-c1s5"></a> Content Management </h2>
<h2 class="common">
<a name="iconsultancy-c1s6"></a> Registered Customers </h2>
<h2 class="common">
<a name="iconsultancy-c1s7"></a> Store Processing </h2>
<h2 class="common">
<a name="iconsultancy-c1s8"></a> Hotel Processing </h2>

The H3 elements:

The information in the paragraph elements:

Our strengths are in website implementation.
In a typical website development creative web designers (user interface 
developers)
design and produce sitemaps, key screen shots, key wireframes, branding,
look, feel and user journeys. Some high level UML may be produced.
The website owner approves these elements and the project progresses
to the implementation stages.
Creative agencies have different strengths.
An agency may be less strong in website implementation
Website implementation is a software engineering discipline.
WhyWaitForever can handle a complete
website development project or can work with a company's existing creative 
agency
and handle website implementation.
Knowledge of website implementation possibilities at the design stage
means future developments such as extending content management
and extending personalisation can be handled at far less cost.
In addition to website developments,
here are some other website related projects we have undertaken.
Search visibility analyses a website to
understand which content elements are visible to the search engine software
used by search websites.
A WhyWaitForever expert reviews the information
and produces a set of recommendations on how the
implementation of website could be improved.
By improving search visibility the quality of
information obtained through web analytics and from email marketing
is improved.
Better information increases web visitors
and results in increased web sales.
more
Search visibility software is run against a number
of competitor websites to extract information about products and prices.
This information is formatted into a report.
Extracts of the information can be formatted as emails and sent
to interested parties.
Advantages of automated intelligence gathering
include the ability to trawl through many websites,
collating only pertinent information and delivering to
the time constrained individuals who can make most benefit of the information.
Email marketing is straightforward.
Individuals register to receive information about products and services.
A company periodically sends out mailings to those that are
registered.
The email has to be tagged in such a way that every web page visited
and every web sale made as a result of the email is accounted for.
It is important to track all sources of visitors.
If the interests of particular types of visitors are known
more web sales can be made.
Understanding why web sales are made is very useful for improving
website personalisation and extended scenario processing.
Business rules are devised whereby content specific to the
interests of the visitor is presented to the visitor
in a way best suited to achieving sales.
One challenge is that companies with many products
typically use webservers that automatically generate URLs which are
not memorable or meaningful.  Unique session identifiers can be
difficult to map to particular customers .
Tracking can be difficult.
WhyWaitForever has expertise in marking up emails, configuring
logging settings and running web analytics to provide
accurate quality marketing information.
An example of a series of email marketing reports
produced for a large web retailer.
The reports have been desensitised and the emails removed to keep the
actual company confidential.
more
Web analytics is the analysis of web activity.
In common with all software auditing it is necessary to know
who did what to what where and when.
The standard tools provide a basic level of analysis.
WhyWaitForever extends these tools to provide more detailed information
for more web aware marketing department.
WhyWaitForever can run web analytics and will provide a series of
observations and recommendations based on the results.
A company would provide access to the logs or would provide a copy of the logs 
on
a set of CDs. The analysis in the form of reports would be returned.
Here are a good starter set of reports for the WhyWaitForever website
for each of the last few years.
Website owners should take great care of their raw web logs.
They are a valuable company asset.
WhyWaitForever has written a web application to support
content management.
It uses the
OpenCms
content management system as a base.
Customised forms are used to create, amend or delete content.
There is support for workflow and users with different security rights
can be set up.
Typically WhyWaitForever uses the content management
system to create document fragments.
These are automatically processed to create other derived document
fragments.  For example when a news item is created, summary
information is created.  This summary is automatically extracted
to create document fragments used in menu and index pages.
WhyWaitForever has written a web application to support
web accounts and web customers.
It is fast in that it uses individual XML
documents to hold customer information.
It is secure in that each XML document can be individually encrypted differently
than any other.
It is easy to incorporate with existing front and back office applications
which usually use a secure relational database to hold information.
WhyWaitForever has written a web application to support
store processing, catalogues, products, orders and purchases.
It provides support for accessing third party payment card processing
websites.
It is fast in that it uses individual XML
documents to hold customer information.
It is secure in that each XML document can be individually encrypted differently
than any other.
It is easy to incorporate with existing front and back office applications
which usually use a secure relational database to hold information.
WhyWaitForever has written a web application to support
hotel processing.
This includes hotel search, room availability search,
room selection, room booking and room cancellation.
It provides support for accessing third party payment card processing
websites or for capturing payment card information for the hotel
reservation process.
It is fast in that the application holds availability information
in cache which means a hotel reservation search can support
cross hotel searches including both price constrained searches and
time constrained searches.
A business customer would typically be time constrained.
A leisure customer would typically have some flexibility as to when
the booking can be made and is more price sensitive.
It is fast for registered customers
in that it uses individual XML documents to hold preferences, reference 
information,
previous room availability searches, previous room selections, bookings and 
cancellations.
Holding preferences and references allows "quick book" and "repeat book"
to only require the date to be input for the confirmed booking to be made.
Preferences includes elements such as room type e.g. suite or double or single.
Reference information includes elements such as loyalty card identifiers.
It is secure in that each XML document can
be individually encrypted differently than any other.
It is easy to incorporate with existing front and back office applications
which usually use a secure relational database to hold information.
A monitor task can be run to routinely exchange information between
the hotel reservation application and the web application.
A customer can cancel a web booking directly through the hotel call centre
and within a few minutes the status of the booking is changed online.
The web application can connect directly to the
hotel reservation such as the OPERA Enterprise Solution from
Micros Fidelio.
It can connect to the major global travel industry aggregators,
distributors and switches
such as
Pegasus or
WizCom.
It can connect to specialist travel industry application suppliers
such as
Chauntry.
As the information is held in XML document format
it is straight forward to exchange information with affiliates, partners and 
others
using message exchange protocols such as SOAP, XML dialects such as the
Open Travel Alliance
and
Really Simple Syndication
or RDF Site Summary (RSS)  feeds.
By building a "parallel" web booking application
the "master" hotel reservation is better protected from the peaks of Internet
traffic.  If direct Internet access to the hotel reservation system is allowed
volumes could overwhelm the hotel reservation system.
A typical hotel reservation system connected to the Internet has a response time
of seconds for a general availability request.
The WhyWaitForever application has a response time of milliseconds.

The anchor (links) elements:

<a name="iconsultancy-c1"></a>
<a name="iconsultancy-c1s1"></a>
<a 
href="http://www.whywaitforever.com/consultancy/search-visibility/product-info.h
tml" class="home-link" title="To Search Visibility" 
onMouseover="window.status='To Search Visibility';return true;" 
onMouseout="window.status='';return true;"> more </a>
<a name="iconsultancy-c1s2"></a>
<a name="iconsultancy-c1s3"></a>
<a 
href="http://www.whywaitforever.com/consultancy/email-marketing/admin/email/inde
x.htm" class="home-link" title="To Example Email Marketing Report" 
onMouseover="window.status='To Example Email Marketing Report';return true;" 
onMouseout="window.status='';return true;"> more </a>
<a name="iconsultancy-c1s4"></a>
<a href="http://www.whywaitforever.com/consultancy/web-logs/y2004/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2004" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2004';return 
true;" onMouseout="window.status='';return true;"> 2004 </a>
<a href="http://www.whywaitforever.com/consultancy/web-logs/y2003/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2003" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2003';return 
true;" onMouseout="window.status='';return true;"> 2003 </a>
<a href="http://www.whywaitforever.com/consultancy/web-logs/y2002/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2002" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2002';return 
true;" onMouseout="window.status='';return true;"> 2002 </a>
<a href="http://www.whywaitforever.com/consultancy/web-logs/y2001/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2001" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2001';return 
true;" onMouseout="window.status='';return true;"> 2001 </a>
<a href="http://www.whywaitforever.com/consultancy/web-logs/y2000/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2000" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2000';return 
true;" onMouseout="window.status='';return true;"> 2000 </a>
<a name="iconsultancy-c1s5"></a>
<a href="http://www.opencms.org/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;"> OpenCms </a>
<a name="iconsultancy-c1s6"></a>
<a name="iconsultancy-c1s7"></a>
<a name="iconsultancy-c1s8"></a>
<a href="http://www.micros.com/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;">Micros Fidelio</a>
<a href="http://www.pegs.com/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;">Pegasus</a>
<a href="http://www.wizcom.com/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;">WizCom</a>
<a href="http://www.chauntry.com/" onMouseover="window.status='';return true;" 
onMouseout="window.status='';return true;">Chauntry</a>
<a href="http://www.opentravel.org/" onMouseover="window.status='';return 
true;" onMouseout="window.status='';return true;">Open Travel Alliance</a>
<a href="http://web.resource.org/rss/1.0/spec" 
onMouseover="window.status='';return true;" onMouseout="window.status='';return 
true;"> Really Simple Syndication
or RDF Site Summary (RSS) </a> feeds. </p>

The image elements:

The META element COPYRIGHT attribute:

Copyright © 2005-2007 WhyWaitforever

Validation

Spelling check and Tidy can return warning or error messages. Search websites looks for correctly spelled words. A website can be down ranked for poor spelling and grammar. It is important all errors and warnings are addressed.

The spelling check messages:

The Tidy messages:

Tidy (vers 4th August 2000) 
Doctype given is "-//W3C//DTD HTML 4.01//EN"
Document content looks like HTML 4.01 Transitional
no warnings or errors were found

The HTML or equivalent page with line counts (for use with messages):

     1	<!DOCTYPE html
     2	PUBLIC "-//W3C//DTD HTML 4.01//EN" 
"http://www.w3.org/TR/html4/strict.dtd">
     3	<html><head>
     4	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
     5	<title> WhyWaitForever Consultancy </title><link rel="stylesheet" 
href="css/main-portlet.css" type="text/css"><link rel="stylesheet" 
href="css/main-layout.css" type="text/css"><link rev="made" 
title="WhyWaitForever" href="mailto:sales@whywaitforever.co.uk"><meta 
name="description" content="This page describes the consultancy undertaken by 
WhyWaitForever."><meta name="keywords" content="consultancy"><meta 
name="copyright" content="Copyright &copy; 2005-2007 WhyWaitforever"><meta 
name="generator" content="WhyWaitForever extending DocBook XSL Stylesheets 
V1.65.1"></head><body><div class="body"><div class="header"><span 
class="header"> WhyWaitForever </span><span class="headerLeft"> IT Consultancy 
</span></div><div class="layout-01"><div class="portlet-01"><div 
class="chapter"><h1 class="common"><a name="iconsultancy-c1"></a> Consultancy 
</h1><p class="common"> Our strengths are in website implementation.
     6	In a typical website development creative web designers (user interface 
developers)
     7	design and produce sitemaps, key screen shots, key wireframes, branding,
     8	look, feel and user journeys. Some high level UML may be produced.
     9	The website owner approves these elements and the project progresses
    10	to the implementation stages. </p><p class="common"> Creative agencies 
have different strengths.
    11	An agency may be less strong in website implementation
    12	Website implementation is a software engineering discipline. </p><p 
class="common"> WhyWaitForever can handle a complete
    13	website development project or can work with a company's existing 
creative agency
    14	and handle website implementation.
    15	Knowledge of website implementation possibilities at the design stage
    16	means future developments such as extending content management
    17	and extending personalisation can be handled at far less cost.
    18	</p><p class="common"> In addition to website developments,
    19	here are some other website related projects we have undertaken. 
</p><div class="section"><h2 class="common"><a name="iconsultancy-c1s1"></a> 
Search Visibility </h2><p class="common"> Search visibility analyses a website 
to
    20	understand which content elements are visible to the search engine 
software
    21	used by search websites.
    22	A WhyWaitForever expert reviews the information
    23	and produces a set of recommendations on how the
    24	implementation of website could be improved. </p><p class="common"> By 
improving search visibility the quality of
    25	information obtained through web analytics and from email marketing
    26	is improved.
    27	</p><p class="common"> Better information increases web visitors
    28	and results in increased web sales.
    29	<a 
href="http://www.whywaitforever.com/consultancy/search-visibility/product-info.h
tml" class="home-link" title="To Search Visibility" 
onMouseover="window.status='To Search Visibility';return true;" 
onMouseout="window.status='';return true;"> more </a></p></div><div 
class="section"><h2 class="common"><a name="iconsultancy-c1s2"></a> Business 
Intelligence Gathering </h2><p class="common"> Search visibility software is 
run against a number
    30	of competitor websites to extract information about products and prices.
    31	This information is formatted into a report.
    32	Extracts of the information can be formatted as emails and sent
    33	to interested parties. </p><p class="common"> Advantages of automated 
intelligence gathering
    34	include the ability to trawl through many websites,
    35	collating only pertinent information and delivering to
    36	the time constrained individuals who can make most benefit of the 
information.
    37	</p></div><div class="section"><h2 class="common"><a 
name="iconsultancy-c1s3"></a> Email Marketing, Visitor Sources and Analysis 
</h2><p class="common"> Email marketing is straightforward.
    38	Individuals register to receive information about products and services.
    39	A company periodically sends out mailings to those that are
    40	registered.
    41	The email has to be tagged in such a way that every web page visited
    42	and every web sale made as a result of the email is accounted 
for.</p><p class="common">  It is important to track all sources of visitors.
    43	If the interests of particular types of visitors are known
    44	more web sales can be made.
    45	</p><p class="common">
    46	Understanding why web sales are made is very useful for improving
    47	website personalisation and extended scenario processing.
    48	Business rules are devised whereby content specific to the
    49	interests of the visitor is presented to the visitor
    50	in a way best suited to achieving sales.
    51	</p><p class="common"> One challenge is that companies with many 
products
    52	typically use webservers that automatically generate URLs which are
    53	not memorable or meaningful.  Unique session identifiers can be
    54	difficult to map to particular customers .</p><p class="common"> 
Tracking can be difficult.
    55	WhyWaitForever has expertise in marking up emails, configuring
    56	logging settings and running web analytics to provide
    57	accurate quality marketing information.</p><p class="common"> An 
example of a series of email marketing reports
    58	produced for a large web retailer.
    59	The reports have been desensitised and the emails removed to keep the
    60	actual company confidential.
    61	<a 
href="http://www.whywaitforever.com/consultancy/email-marketing/admin/email/inde
x.htm" class="home-link" title="To Example Email Marketing Report" 
onMouseover="window.status='To Example Email Marketing Report';return true;" 
onMouseout="window.status='';return true;"> more </a></p></div><div 
class="section"><h2 class="common"><a name="iconsultancy-c1s4"></a> Web 
Analytics </h2><p class="common"> Web analytics is the analysis of web activity.
    62	In common with all software auditing it is necessary to know
    63	who did what to what where and when. </p><p class="common">
    64	The standard tools provide a basic level of analysis.
    65	WhyWaitForever extends these tools to provide more detailed information
    66	for more web aware marketing department. </p><p class="common"> 
WhyWaitForever can run web analytics and will provide a series of
    67	observations and recommendations based on the results.
    68	A company would provide access to the logs or would provide a copy of 
the logs on
    69	a set of CDs. The analysis in the form of reports would be returned.
    70	</p><p class="common">
    71	Here are a good starter set of reports for the WhyWaitForever website
    72	for each of the last few years.</p><div class="itemizedlist"><ul><li>
    73	<a 
href="http://www.whywaitforever.com/consultancy/web-logs/y2004/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2004" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2004';return 
true;" onMouseout="window.status='';return true;"> 2004 </a>
    74	</li><li>
    75	<a 
href="http://www.whywaitforever.com/consultancy/web-logs/y2003/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2003" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2003';return 
true;" onMouseout="window.status='';return true;"> 2003 </a>
    76	</li><li>
    77	<a 
href="http://www.whywaitforever.com/consultancy/web-logs/y2002/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2002" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2002';return 
true;" onMouseout="window.status='';return true;"> 2002 </a>
    78	</li><li>
    79	<a 
href="http://www.whywaitforever.com/consultancy/web-logs/y2001/index.html" 
class="home-link" title="To WhyWaitForever Web Analytics for 2001" 
onMouseover="window.status='To WhyWaitForever Web Analytics for 2001';return 
true;" onMouseout="window.status='';return true;"> 2001 </a>
    80	</li><li>
    8