web4kids 0 Report post Posted August 4, 2005 Tutorial: An Introduction to WAI: This is a Turtorial made by Chaos (my co-admin)that he posted on my forums his website is http://forums.xisto.com/no_longer_exists/ Anways Here's the Tutorial: WAI are the guidlines introduced by the W3C in order to make webpages accessible for everybody. The guidlines are made up of three Priorities. If you want your site to be available to everyone then it is important you at least comply with prioriy one. This article will cover all three priorities and how to incoperate them into your site. But remember there are other considerations as well. Basic Practices In order to comply with Priority 1 the following guidlines mus be met. Most of these are common sense and you will find most sites only fall short on one or two points. Always use the Alt attribute when using the IMG tags Dont use Marquee or Blinking text Make sure the document can still be read without a style sheet Provide text links when using image maps Dont use tables for layout - only use them to convey data in a table format Title each frame to facilitate frame identification and navigation. Ensure that pages are still usable if all appletes/scripts etc are turned off These are the basic guidlines your site should follow if you wish it to be accessible to the majoirty of uses. Onto Priority Two Priority two focusses on the interoperability of the web page(How well it can be transfered from one browser to another) The majoiry of the guidlines invovle good web programming practices. If you already code your sites the the XHTML 1.1 standered, you will find your site complies with most guidlines. A few things to note are: Labels must be used to designate form fields. I find that most people tend to markup forms like this: Name<input type="text" name="name" /> You must use labels like this: <label for="name">Name:</label><input type="text" name="name" /> Ensure background and Foreground colors contrast - this is for obvious reasons. Onto Priority Three Priority three expands on priority two, most of the things covered in Priority three tend to be for older and less complex text readers. A few things to note are: You must identify the natural language of the document e.g <html xml:lang="english"> You must have a breaker between adjacent links. This one is the most difficult to grasp. All adjacent links must be broken up by an image or list seperators. Paragraph tags will not work.e.g <li><a href="link">link</a></li><li><a href="link2">link</a></li> These can be easily hidden using CSS for use in graphic browsers. Place holders must be used in otherwise empty input boxes. Rounding off Ok, that completes my introduction to the WAI web standered this should be enough to get you started. Validating It is always important to use a validator to check the main points of your code. Remember to also check things validators cant such as colour contrasts. http://forums.xisto.com/no_longer_exists/ A great validator to check your sites. Also gives a list of things for users to check independantly. If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible page. This will ensure your content is available to anyone who wants it. Hope this helps, if you have any questions please feel free to ask Chaos Share this post Link to post Share on other sites
web4kids 0 Report post Posted August 4, 2005 Ooops sorry guys... This post doesn't need to go toward credits but can a mod move this to awaing approvels in the turtorial place please.... Anaways i gtg sorry if this doesn't make scence Share this post Link to post Share on other sites
whyme 0 Report post Posted August 15, 2005 no this doesn't make any sense, you didn't quote the text, for all the texts that you did not write, you need to quote them. im closing this topic and moving it.whyme Share this post Link to post Share on other sites
