Making WordPress Even Easier to Use!
You are currently browsing the archive for the Web Standards category.
Web applications should always adhere to W3C standards and validate correctly. Numerous excellent CSS style Guides are available that discuss the how-tos of achieving these objectives, below are a few:
References:
Tutorial:
Tags: css, Development, Guides, Web Development
Over the years we have come across numerous useful websites; sites that communicate useful information on web development, standards implementation and more. A few are listed here (we’ll update this list as time goes on…)
The following sites provide detailed information on web standards. Please remember that all of sites should adhere to applicable web standards! Use these sites to ensure your code complies with the relevant standards.
Tags: Guides, Web Development, web standards
Establish an overall goal for your web site. Who will your audience be? What information do you want to convey to this audience?
Which of the following will your audience be using?
Design your site so that it meets the specifications of the target (s) chosen. See www.thecounter.com/stats to see current statistics regarding the most frequently used browser versions, monitor resolutions and operating systems.
Tags: Development, Guides, Site Development
For the future, to add presentational effects and Web page style, validate documents at the HTML 4.0 level (for the cleanest possible markup), so pages contain little or no HTML 3.2 presentational markup or proprietary stylistic hacks, and use the World Wide Web Consortium ‘ s Cascading Style Sheet (CSS) language to add stylistic effects to your pages.
Tags: Development, Guides, Site Development, web standards
This web page provides links to resources which can be used to help web developers understand and implement web accessibility compliance requirements and guidelines.
The World Wide Web Consortium (www.w3.org) has, through it Web Accessibility Initiative (WAI), outlined several resources, which are referenced below.
On December 21, 2000, the federal Access Board issued final standards for electronic and information technology under Section 508 of the Rehabilitation Act. On January 22, 2001, the General Services Administration (GSA) issued a notice to adopt these standards into the Federal procurement regulations. For summaries and details related to these standards, see: Section 508 of the Rehabilitation Act: Electronic and Information Technology Accessibility Standards.
The standards adopted by this board regarding accessibility on the web are largely based upon the Web Accessibility Initiative (WAI) of the World Wide Web Consortium. However, there are 5 standards, (l) through (p), that are different than any comparable provision in the Web Content Accessibility quidelines of the WAI. A listing of the standards that apply to web accessibility can be found at: Section 508 Accessibility Requirements for Web Sites on the WebAble site. You may also find guidelines produced by the Access Board for web accessibility in Web-based Intranet and Internet Information and Applications.
ADA-Friendly Web Sites for Students: The Why and the How provides some good background on the portions of the Americans with Disabilities Act and Rehabilitation Act which apply to web accessibility.
Common Myths About Web Accessibility is a site recommended by Carol Yoho. This article dispels some misconceptions about accessible web authoring.
| Section 508 Accessibility Requirements for Web Sites | extracted directly from the final ruling of the Section 508 mandate as released by the Federal Access Board on December 20, 2000. |
| Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 | This list of checkpoints is divided up into THREE levels of priorities |
Tags: Development, Guides, Site Development, web standards
| Quick Tips to Make Accessible Web Sites | ” Quick Tips ” introduce key concepts of accessible Web design. Please note that these are not complete guidelines. |
| Web Accessibility Quick Reference | A document created by AmbientWebs ‘ s Web Services to provide a summary of the items that must be done to accomplish web accessibility using the priorities established by WAI. |
| WebXact | WebXact is a web-based tool that analyzes web pages for their accessibility to people with disabilities. The Center for Applied Special Technology (CAST) offers WebXact as a free public service in order to further its mission to expand opportunities for people with disabilities through the innovative uses of computer technology. To analyze a web page, type in the URL of the page that you want WebXact to examine and select Submit. WebXact will display a report indicating any accessibility and / or browser compatibility errors found on the page. |
| Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 | This list of checkpoints is divided up into THREE levels of priorities. |
| Web Content Accessibility Guidelines 1.0 | This is a very long document which outlines all of the guidelines. If you prefer to digest them all at once, you can read this entire document. |
| Techniques for Web Content Accessibility Guidelines 1.0 | While Web Content Accessibility Guidelines 1.0 strives to be a stable document (as a W3C Recommendation), this document is expected to evolve as technologies change and content developers discover more effective techniques for designing accessible pages. |
Tags: Development, Guides, Site Development, web standards
From the original article by:
Russ Weakley
13-August-04
The term web standards can mean different things to different people. For some, it is ‘ table-free sites ‘, for others it is ‘ using valid code ‘. However, web standards are much broader than that. A site built to web standards should adhere to standards (HTML, XHTML, XML, CSS, XSLT, DOM, MathML, SVG etc) and pursue best practices (valid code, accessible code, semantically correct code, user-friendly URLs etc).
In other words, a site built to web standards should ideally be lean, clean, CSS-based, accessible, usable and search engine friendly .
This is not an uber-checklist. There are probably many items that could be added. More importantly, it should not be seen as a list of items that must be addressed on every site that you develop. It is simply a Guide that can be used:
Tags: Development, Guides, Web Developer, web standards
Recent Comments