Web Standards [The Basics Part Three] - The Checklist
By complying with XHTML, CSS, and basic accessibility standards; Interactive Properties ensure their long-term viability as browsers and standards evolve.
Quality of code
- The site has full and correct Doctype
- The site uses character set
- The site uses valid (X)HTML
- The site uses valid CSS
- The site uses minimal CSS hacks
- The site has no unnecessary classes or ids
- The site uses well structured code
- The site has no broken links
- The site has been checked for speed and page size
- The site has no JavaScript errors
Degree of separation between content and presentation
- Where possible, decorative images in CSS
- The site uses CSS for all presentational aspects
Accessibility for users
- The site uses “alt” attributes for images
- The site uses relative units for text size
- The site layout is stable if font size increases
- The site uses visible skip menus
- The site uses accessible forms
- The site uses accessible tables
- The site has sufficient colour brightness/contrasts
- The site does not use colour alone for critical information
- The site uses delayed responsiveness for dropdown menus
- The site uses descriptive links
Accessibility for devices
- The site works acceptably across target browsers
- Content is accessible without CSS
- Content is accessible without images
- Content is meaningful in text browsers
- The content is accessible when printed?
- The content is accessible on Hand Held devices?
- The site has detailed metadata?
- The site work well in different window sizes?
Basic Usability
- The site has clear visual hierarchy?
- Headings clearly indicate the structure of the document
- Navigation is easy to understand
- Navigation is consistent throughout site
- The site uses underlined links
- The site uses consistent and appropriate language?
- The site has easy to find sitemap and contact page
- The site has a search tool
- The site has link to the home page on every page
- The site has clearly defined visited links
Site management
- The site has a meaningful 404 error page
- The site has friendly URLs
- The site allows URLs to work without “www”
- The site has a favicon
Learn more: Web Standards Project
Note: I do not claim original authorship over the checklist. The origin of the original checklist is unknown. This has become one of those documents I have taken with me through many employers and adapted as necessary.
Subscribe to RSS Feed
Categories: design, web standards
- February 9th, 2006
- 4comments
- I am a proud member of the 9rules network
Thanks for putting this up. I printed it out and posted it in the office :)
- Tom
No problem. Glad to contribute!
Just a pointer, that last link in the list of articles just links back to this article.
And what about linking to related articles on “each” point?
Like, what is the correct Doctype, how can I avoid css hacks.
“Where possible, decorative images in CSS”
Thats not true, any picture that has with layout and design sould not be img, but content related images should always be an img Not trying to trash every article you write, just giving you my thouts.
Thanks for the pointer — not sure how that happened (sort of embarrassing on the accessibilities section, LOL). Good thing I didn’t include usability.
This was just a simple tutorial for those who know of “web standards”, but have no real design/development background — the business/project managers of the world. I am trying to educate without scaring people away — sort of start small and simple. I’ve had too many ignorant co-workers/clients try and manage projects that require web standards — it’s a painful sight. Once non-designers/developers feel more comfortable with web standards and intimidating buzz words (AJAX, XML, XHTML, JavaScript) they will begin broadening their horizons and adapting the more strict standards (or so I hope).
I appreciate the feedback though. Thank You!