Web Standards
Web standards should be taken into account when designing a web site because they can improve business and increase revenues.
The main standards used on the web are the languages used to create web sites eg HTML, XHTML and CSS. HTML or XHTML are used to create the structure of web sites while CSS is used to style, format and position the structure and content of web sites. To be standards compliant is to use these languages correctly for example, table tags should not be used for layout - should only be used to contain information (tabular data).
Complying with web standards can help a business because quality, web standards compliant code has the benefit of giving a web site forward compatibility, increased download speed, browser compatibility, making site maintenance easier and will target a broader audience.
Accessibility
Web accessibility encompasses all disabilities that affect access to the Web, including visual, auditory, physical, speech, cognitive, and neurological disabilities.
The Web Accessibility Initiative (WAI) guidelines support two themes for accessible design. First ensuring “graceful transformation” which means pages remain accessible given different operating environments. The key to graceful transformation is a separation of:
- content (what you say to visitors)
- structure (how its organized)
- presentation (what it looks like)
The second theme focuses on "making content understandable and navigable." A lot of that is simple, straightforward language. But it also means providing tools for easy maneuvering around the site.
Each checkpoint in the guidelines has a priority level assigned based on the checkpoint's impact on accessibility.
Priority 1
A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.
Priority 2
A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents.
Priority 3
A Web content developer may address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents.
The WAI has also defined three levels of conformance. You are assigned a conformance level depending on what priority level checkpoints are satisfied. Below are the three conformance levels:
- Conformance Level "A": all Priority 1 checkpoints are satisfied
- Conformance Level "Double-A": all Priority 1 and 2 checkpoints are satisfied
- Conformance Level "Triple-A": all Priority 1, 2, and 3 checkpoints are satisfied
- Following is a list of my understanding of the 14 Web Content Accessibility Guidelines. Please visit http://www.w3.org/WAI/ for lots more information.
- Provide equivalent alternatives to auditory and visual contents - Go to town with the Alt tag and provide a text equivalent for every non-text element. This includes images and audio files etc.
- Don't rely on colour alone - Ensure that all information conveyed with colour is also available without colour, for example from context or markup – Focus on contrast
- Use mark-up and style sheets properly. Control presentation with style sheets rather than presentation elements and attributes. All absolute units will go to relative units.
- Clarify natural-language usage – reduce acronym use. Use mark-up that facilitates pronunciation or interpretation of abbreviated or foreign text.
- Create tables that transform gracefully - Tables for layout equals NO-NO.
- Ensure that pages featuring new technologies transform gracefully - Lose your style sheets and see what happens! Make sure page is still accessible if newer technologies are not supported or are turned off.
- Ensure user control of time-sensitive content changes. Auto-refreshing your pages? Think again. Ensure that moving, blinking, scrolling, or auto-updating objects or pages may be paused or stopped.
- Ensure direct accessibility of embedded user interfaces - Scripts and applets should work for ALL devices.
- Design for device-independence. Allow the client to use features that enable activation of page elements via a variety of input devices.
- Use interim solutions so that assistive technologies and older browsers will operate properly - No more pop-ups without informing the user.
- Use W3C technologies and guidelines. Be aware of requiring plug-ins or stand-alone applications.
- Provide context and orientation information to help users understand complex pages or elements. Every frame should have a title.
- Provide clear navigation mechanisms. Too obvious - make sure all navigation is consistent, that search works, and don't forget the site map.
- Ensure that documents are clear and simple. Headings are a must - Keep it simple and leave out the jargon.