Under the Disability Discrimination Act 1995 (DDA), a disability is defined as:

A physical or mental impairment that has a long-term or substantial effect on a person’s ability to carry out day to day tasks.

This ranges from people with physical and sensory impairments to people with diabetes, disfigurements, heart disease and epilepsy.

Accessibility, therefore, can be viewed as the “ability to access” the functionality of a system or entity. Furthermore, accessibility is a somewhat general term used to describe the degree to which a product (e.g. device, service and environment) is accessible to as many people as possible. Accessibility is often used to focus on people with disabilities and their right of access to entities, often through use of assistive technology.

A dimension of accessibility is web accessibility. Web accessibility refers to the practice of making websites usable by people of all abilities and disabilities. When sites are correctly designed, developed and edited, all users can have equal access to information and functionality. In many countries this has led to initiatives, laws and regulations that aim toward providing universal access to the internet.

Digital Web Magazine has a great article on whether accessibility statements are useful, which is well worth a read.

The main points of consideration that can be garnered from the article are as follows:

1. Make the accessibility link prominent and provide it in a consistent location so that website visitors can find it easily.
2. Provide rich content that explains how to use the accessibility features provided, rather than just listing the features themselves.
3. Separate the content into sections and provide headings for each section.
4. Provide contact information in various formats so that website visitors can directly contact the team responsible for accessibility queries.
5. Actively promote feedback from website visitors. Use comments to continually improve the website.
6. Provide a known barriers section which details inaccessible areas of the website along with alternative ways of obtaining the information or services.
7. List technical and conformance information at the end of the accessibility statement. This will allow the information to be readily available, whilst not being placed in a prominent position.

Your accessibility statement will be organic — you may only start with a few lines but as your site develops in terms of accessibility, and your understanding of the accessibility of the site develops, so will your statement. As it can often be created and then forgotten about, it is worthwhile taking time every so often to check through the statement to ensure that it is up-to-date and reflects the work done to enhance the site’s accessibility.

To avoid undesirable content in the search indexes, webmasters can instruct spiders not to crawl certain files or directories through the standard robots.txt file. Conversely and importantly, webmasters can also notify the search engines about the existence and importance of pages with a sitemap.xml file. (Both files are placed in the root directory of the domain.)

Fortunately for the webmaster, the major search engines provide various tools to help manage both Sitemap and Robot files.

To gain an understanding of both ‘protocols’, I’ll discuss them briefly below.

Sitemaps (Inclusion Protocol)

The Sitemaps protocol allows a webmaster to inform search engines about URLs on a website that are available for crawling. A Sitemap is an XML file that lists the URLs for a site. It allows webmasters to include additional information about each URL: when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. This allows search engines to crawl the site more intelligently. Sitemaps are a URL inclusion protocol and complement robots.txt, a URL exclusion protocol.

The webmaster can generate a Sitemap containing all accessible URLs on the site and submit it to search engines. Since Google, MSN, Yahoo!, and Ask use the same protocol now, having a Sitemap would let the biggest search engines have the updated pages information.

Sitemaps supplement and do not replace the existing crawl-based mechanisms that search engines already use to discover URLs. By submitting Sitemaps to a search engine, a webmaster is only helping that engine’s crawlers to do a better job of crawling their site(s). Using this protocol does not guarantee that web pages will be included in search indexes, nor does it influence the way that pages are ranked in search results.

The following is a cut-down version of the sitemap.xml for this website. WordPress, via a plugin, automatically updates this file each time a new post or page is written.

<urlset xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
<url>
<loc>http://www.simonwhatley.co.uk/</loc>
<lastmod>2008-10-08T14:50:16+00:00</lastmod>
<changefreq>daily</changefreq>
<priority>1.0</priority>
</url>
<url>
<loc>
http://www.simonwhatley.co.uk/big-city-little-people
</loc>
<lastmod>2008-10-08T14:50:16+00:00</lastmod>
<changefreq>monthly</changefreq>
<priority>0.1</priority>
</url>
</urlset>

More information about sitemaps can be found on the Sitemaps.org website.

Robots (Exclusion Protocol)

The robot exclusion standard, also known as the Robots Exclusion Protocol or robots.txt protocol, is a convention to prevent cooperating web spiders and other web robots from accessing all or part of a website which is otherwise publicly viewable. Robots are often used by search engines to categorise and archive web sites. The standard complements Sitemaps, a robot inclusion standard for websites.

A robots.txt file on a website will function as a request that specified robots ignore specified files or directories in their search. This might be, for example, out of a preference for privacy from search engine results, or the belief that the content of the selected directories might be misleading or irrelevant to the categorisation of the site as a whole.

The protocol, however, is purely advisory. It relies on the cooperation of the web robot, so that marking an area of a site out of bounds with robots.txt does not guarantee privacy. Some web site administrators have tried to use the robots file to make private parts of a website invisible to the rest of the world, but the file is necessarily publicly available and its content is easily checked by anyone with a web browser.

For example, the following tells all crawlers not to enter four directories of a website:

User-agent: *
Disallow: /cgi-bin/
Disallow: /images/
Disallow: /tmp/
Disallow: /private/

Exclusion can also be achieved on a page-level basis using a Meta-tag. This is a tag that would be placed in the HTML head of of a web page. The robots attribute controls whether search engine spiders are allowed to index a page, or not, and whether they should follow links from a page, or not.

A common example could be as follows:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-GB" xml:lang="en">
 <head profile="http://gmpg.org/xfn/11">
	<title>Simon Whatley</title>
	<meta http-equiv="robots" content="index,follow" />
</head>
<body>
</body>
</html>

A word of caution though, Meta tags are not the best option to prevent search engines from indexing content of your website.

More information about Robots.txt files can be found on the Robotstxt.org website.

Webmaster Tools

The top 3 search providers all have their own webmaster tools admin interface. The Google offering is the most advanced, but it’s good practice to use and submit information to all three.

Links to their services are provided below:

• Google Webmasters
• Yahoo! Site Explorer
• Live Search Webmaster Centre

Ask doesn’t have an interface. However, you can still ping their Submission Service using the URL http://submissions.ask.com/ping?sitemap= in conjunction with your sitemap URL.

Further Information

• Sitemap Generator
• Sitemap 3rd Party porgrams and websites
• Webmaster Toolkit

Websites are increasingly the key communication vehicle for a company, its brand and products. Despite this, research from Magus shows that many of the world’s leading organisations don’t have formal brand and technical standards defined to govern their websites. Even those that do are failing to effectively implement or enforce them, achieving full compliance with less than 20% of their own web standards. The websites of these organisations significantly under-perform or damage the brand as a result.

PAS 124 will help to protect the significant investment organisations are making in their web presence and online brands, by establishing best practice for “defining, implementing and managing organisational web standards”. It will provide a clear framework to help organisations apply standards effectively to significantly improve online performance and protect the integrity of their brands.

More detail can be found on the BSI’s press release.

Remember to make back-up copies of all your Apache configuration files, in case one of the changes you make while experimenting renders the Web server inoperable.

Also, remember that configuration changes you make don’t take effect until you restart Apache.

Configure the httpd.conf File:

The httpd.conf file can be found in the conf directory in your Apache installation. In my case, this is the following location:

C:\Program Files\Apache Software Foundation\Apache2.2\conf

1. To include the correct default or index file, you need to find the following code and make sure that your default file name is included (see screenshot).

<IfModule>
DirectoryIndex index.htm index.html
</IfModule>

For ColdFusion and PHP you would also need to include their equivalents, i.e. index.cfm and index.php.

2. Set up a virtual host definition:

<virtualhost>
DocumentRoot c:\WebRoot
ServerName localhost
<directory>
Order allow,deny
Allow from all
</directory>
</virtualhost>

Make sure that the directory permissions are set otherwise a directory forbidden message (such as below) will be displayed.

3. Restart the Apache service. You should then be able to browse to your local website.

4. If you’re doing something cunning like setting up an alias for the local site, e.g. http://whatley.local/ rather than the usual http://localhost/whatley/ then you may need to edit your hosts file e.g.:

In my case, the hosts file is found in the following location: C:\Windows\System32\drivers\etc. You can simply edit this file in notepad, much like with httpd.conf.

And that is all there is to it.

• B to B
• ClickZ
• CRMGuru
• CRMIQ
• DM News
• Drilling Down
• EmailSherpa
• Ezine-Tips
• iMarketing News
• Larry Chase’s Search Engine for Marketers
• MarketingProfs
• Marketing Sherpa
• The Newsletter on Newsletters
• SearchCRM.com
• Spam Laws
• Web Marketing Today – WilsonWeb
• WordBiz
• Email Marketing Reports