Tryangled Solutions web designing tips tricks

Accessible HTML is accessible to both search engine spiders and screen readers. The more accessible you make your pages, the easier it will be for search engines to read and rank your pages.

Google simply puts a 30 days block upon sites that use trivial keyword tricks (hidden text/div or text in the same color as a background), so don’t bother trying this kind of stuff. Detecting and catching a robot with javascript or IP cloacing or using linkfarms to boost your Pagerank are considered even more illegal. They could get you put out of the ranking for good.

Just remember that a robot will be optimized over and over to be able to judge webpages the way a human does. In the end, if you make sure your site is clean and accessible and your content is good and relevant, websurfers will find you and bytes will flow.

Of course this article only covers the rough basics of search engine optimization. If you feel like I have missed out on something, or you’ve got an excellent hint to share, please feel free to post them in the forum! The diagnostics guide from GoogleRankings.com is a great resource for more information (there’s a list of issues at the left side).

It’s important to make sure that the web site loads as quickly as possible and that people can easily access all the pages. Waiting time should not exceed 30 seconds and links to other pages should be easily accessible. .

It is easy to think that everyone has the same abilities as you do. People viewing Web pages don’t have special needs beyond seeing new information, interesting graphics, and useful effects, right? Wrong.

Lots of people with visual impairments, hearing impairments, and mobility impairments use the World Wide Web every day. While Web Designers can’t do much about the hardware that disabled people are using, we can strive to make our pages more accessible to them.

One of the easiest ways to check your page for Accessibility is to send it through the HTML checker, WebXact. WebXact checks your HTML and redisplays the page with images as annotations to help you see where your page might be inaccessible. WebXact checks both browser compatibility problems and disability access problems.

Here are some of the common errors and how to fix them:

* Missing alternative text description
Don’t forget the alternative text in your <img> tags. This helps people who use screen readers know what the images are, it is also useful for people who view the Web with images off

* Page does not have a noframes version
Include a <noframes> version of your framed pages on the top level frameset. A page with a completely replicated noframes version is more accessible than a noframes version that simply suggests the viewer get a different browser.

* Missing alternative text descriptions for image maps
Put an alt=”text” in your HTML area tags For example:

<area shape=rect coords=0,0,10,10 href=”example.htm” alt=”example”>

This helps people with screen readers know where the image map will take them.

* No text only links for image heavy pages
It is a nice touch to add links to text-only versions of your pages. These pages often load faster and when it is text only there is little problem for screen readers.

* No descriptive text for audio files and movie files
While audio files improve the Web experience for blind people, they are inaccessible for deaf people. The reverse is true for movie files. When there is descriptive text for these types of files, they make the page more accessible to more people.