Standards & Accessibility - a quick guide

Standards exist so that there is an agreement between different browsers on how documents should be presented/rendered.
Looking forward to the future there is always a new next generation browser and adhering to standards ensures that the web pages keep their original look.
Part of that standard is writing clean mark-up and separating presentation from the content. This gives the user the control over how they want access the content.
This also makes it easier for redesigning a website and providing different versions, including a text only version in high contrasting colours.

I design websites that validate using the W3C validation tool for XHTML and CSS. This means that complying with accessibility requirements is easier and and I always try to make considerable progress to comply with the WCA Guidelines. There are fourteen guidelines but only a few are relevant for most websites. The guidelines have been assigned checkpoints and that allow the web designer to check whether or not the web site conforms to the guidelines. Each checkpoint has been assigned a priority level or 1, 2, or 3. The priority level tells the web designer how important the checkpoint is.
The Priority 1 checkpoints identify the basic steps that should be taken to ensure that most people can access the website.
I have summarised the relevant and commonly applied WCA guidelines
1. Provide text equivalents for pictures i.e. meaningful alt tags.
2. Don’t rely on colour alone
3. Use mark up and style sheets
6. Ensure pages featuring new technologies transform gracefully

Guidelines 1, 2 and 3 I will always include, but sometimes it can be difficult to implement guidline 6, but don't forget the website will still validate XHTML and CSS.
Dreamweaver has tools to check validation for XHTML, which seemed very accurate although I usually use the W3C’s validation tool alongside. I used the tool to check for browser compatibility and at it will highlight if there are any issues in for example Internet Explorer 6. Usually I have no presentation issues in Firefox 3.0 or Internet Explorer 7/8, which are the browsers I consistently check the pages in.
I always check each page for accessibility using Dreamweaver’s tool which picks ups, non obvious things like not providing meta data for all pages, needing to provide some title’s to links on some pages and sometimes things like needing to provide a text alternative to the JavaScript rollovers. The rollovers could actually be done using CSS and in the future I will do that instead.

cheers

martin

further reading can be found at
http://www.w3.org/TR/WCAG10/

Keywords - explained

Keywords are a type of meta data which describe content. Appropriate keywords for a site are words taken from the text of the pages, as anything else can be penalised (Get Into Bed with Google by Jon Smith 2008) and result in a lower ranking. Other keywords I could include in the meta data are misspelled versions, plurals, and abbreviations.

The relevance of keywords is not as important as it once was. Google no longer takes any notice of them according to searchenginewatch.com. What Google looks at is key. Nielsen online has publicised the search engine share rating January 08 for each of the major search engines.
Google Search captures 62.8% of all searches, followed by Yahoo at 16.2% and MSN at 11.2%.
The highest of the others is no higher than 4% and most are below 1%.
Google places more focus on titles, headers, alt tags and main text, i.e. the content so always when writing code I ensure that it can be easily read by Google and the other search engines.

How does a website happen? A short guide.

The basics of how it happens.
1. Talk to the client
2. Register a domain name and arrange hosting
3. Resource Preparation - images, text
4. Plan page layouts, navigation structure.
5. Decide on how much usability, standards and accessibility I need to build in.
6. Start coding in HTML and CSS, building SEO in to the content.
7 .FTP - Upload the code to the server
8. Test in different browsers
9. User testing
10. Editing and agree future maintenance.