A Web Standards Checklist, How to make a proper website A web standards checklist 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. About the checklist 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: * to show the breadth of web standards * as a handy tool for developers during the production phase of websites * as an aid for developers who are interested in moving towards web standards The checklist 1.Quality of code 1. Does the site use a correct Doctype? 2. Does the site use a Character set? 3. Does the site use Valid (X)HTML? 4. Does the site use Valid CSS? 5. Does the site use any CSS hacks? 6. Does the site use unnecessary classes or ids? 7. Is the code well structured? 8. Does the site have any broken links? 9. How does the site perform in terms of speed/page size? 10. Does the site have JavaScript errors? 2. Degree of separation between content and presentation 1. Does the site use CSS for all presentation aspects (fonts, colour, padding, borders etc)? 2. Are all decorative images in the CSS, or do they appear in the (X)HTML? 3. Accessibility for users 1. Are "alt" attributes used for all descriptive images? 2. Does the site use relative units rather than absolute units for text size? 3. Do any aspects of the layout break if font size is increased? 4. Does the site use visible skip menus? 5. Does the site use accessible forms? 6. Does the site use accessible tables? 7. Is there sufficient colour brightness/contrasts? 8. Is colour alone used for critical information? 9. Is there delayed responsiveness for dropdown menus (for users with reduced motor skills)? 10. Are all links descriptive (for blind users)? 4. Accessibility for devices 1. Does the site work acceptably across modern and older browsers? 2. Is the content accessible with CSS switched off or not supported? 3. Is the content accessible with images switched off or not supported? 4. Does the site work in text browsers such as Lynx? 5. Does the site work well when printed? 6. Does the site work well in Hand Held devices? 7. Does the site include detailed metadata? 8. Does the site work well in a range of browser window sizes? 5. Basic Usability 1. Is there a clear visual hierarchy? 2. Are heading levels easy to distinguish? 3. Does the site have easy to understand navigation? 4. Does the site use consistent navigation? 5. Are links underlined? 6. Does the site use consistent and appropriate language? 7. Do you have a sitemap page and contact page? Are they easy to find? 8. For large sites, is there a search tool? 9. Is there a link to the home page on every page in the site? 10. Are visited links clearly defined with a unique colour? 6. Site management 1. Does the site have a meaningful and helpful 404 error page that works from any depth in the site? 2. Does the site use friendly URLs? 3. Do your URLs work without "www"? 4. Does the site have a favicon? 1. Quality of code 1.1 Does the site use a correct Doctype? A doctype (short for 'document type declaration') informs the validator which version of (X)HTML you're using, and must appear at the very top of every web page. Doctypes are a key component of compliant web pages: your markup and CSS won't validate without them. CODE http://www.alistapart.com/articles/doctype/ More: CODE http://www.w3.org/QA/2002/04/valid-dtd-list.html CODE http://css.maxdesign.com.au/listamatic/about-boxmodel.htm CODE http://gutfeldt.ch/matthias/articles/doctypeswitch.html 1.2 Does the site use a Character set? If a user agent (eg. a browser) is unable to detect the character encoding used in a Web document, the user may be presented with unreadable text. This information is particularly important for those maintaining and extending a multilingual site, but declaring the character encoding of the document is important for anyone producing XHTML/HTML or CSS. CODE http://www.w3.org/International/tutorials/tutorial-char-enc/ More: CODE http://www.w3.org/International/O-charset.html 1.3 Does the site use Valid (X)HTML? Valid code will render faster than code with errors. Valid code will render better than invalid code. Browsers are becoming more standards compliant, and it is becoming increasingly necessary to write valid and standards compliant HTML. CODE http://www.maxdesign.com.au/presentation/sit2003/06.htm More: CODE http://validator.w3.org/ 1.4 Does the site use Valid CSS? You need to make sure that there aren't any errors in either your HTML or your CSS, since mistakes in either place can result in botched document appearance. CODE http://www.meyerweb.com/eric/articles/webrev/199904.html More: CODE http://jigsaw.w3.org/css-validator/ 1.5 Does the site use any CSS hacks? Basically, hacks come down to personal choice, the amount of knowledge you have of workarounds, the specific design you are trying to achieve. CODE http://www.mail-archive.com/wsg@webstandardsgroup.org/msg05823.html More: CODE http://css-discuss.incutio.com/?page=CssHack CODE http://css-discuss.incutio.com/?page=ToHackOrNotToHack CODE http://centricle.com/ref/css/filters/ 1.6 Does the site use unnecessary classes or ids? I've noticed that developers learning new skills often end up with good CSS but poor XHTML. Specifically, the HTML code tends to be full of unnecessary divs and ids. This results in fairly meaningless HTML and bloated style sheets. CODE http://www.clagnut.com/blog/228/ 1.7 Is the code well structured? Semantically correct markup uses html elements for their given purpose. Well structured HTML has semantic meaning for a wide range of user agents (browsers without style sheets, text browsers, PDAs, search engines etc.) CODE http://www.maxdesign.com.au/presentation/benefits/index04.htm More: CODE http://www.w3.org/2003/12/semantic-extractor.html 1.8 Does the site have any broken links? Broken links can frustrate users and potentially drive customers away. Broken links can also keep search engines from properly indexing your site. More: CODE http://validator.w3.org/checklink 1.9 How does the site perform in terms of speed/page size? Don't make me wait... That's the message users give us in survey after survey. Even broadband users can suffer the slow-loading blues. CODE http://www.websiteoptimization.com/speed/ 1.10 Does the site have JavaScript errors? Internet Explore for Windows allows you to turn on a debugger that will pop up a new window and let you know there are javascript errors on your site. This is available under 'Internet Options' on the Advanced tab. Uncheck 'Disable script debugging'. 2. Degree of separation between content and presentation 2.1 Does the site use CSS for all presentation aspects (fonts, colour, padding, borders etc)? Use style sheets to control layout and presentation. CODE http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-style-sheets 2.2 Are all decorative images in the CSS, or do they appear in the (X)HTML? The aim for web developers is to remove all presentation from the html code, leaving it clean and semantically correct. CODE http://www.maxdesign.com.au/presentation/benefits/index07.htm 3. Accessibility for users 3.1 Are "alt" attributes used for all descriptive images? Provide a text equivalent for every non-text element CODE http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-text-equivalent 3.2 Does the site use relative units rather than absolute units for text size? Use relative rather than absolute units in markup language attribute values and style sheet property values'. CODE http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-relative-units More: CODE http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-relative-units CODE http://www.clagnut.com/blog/348/ 3.3 Do any aspects of the layout break if font size is increased? Try this simple test. Look at your website in a browser that supports easy incrementation of font size. Now increase your browser's font size. And again. And again... Look at your site. Does the page layout still hold together? It is dangerous for developers to assume that everyone browses using default font sizes. 3.4 Does the site use visible skip menus? A method shall be provided that permits users to skip repetitive navigation links. CODE http://www.section508.gov/index.cfm?FuseAction=Content&ID=12 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. CODE http://www.w3.org/TR/WCAG10-TECHS/#tech-group-links ...blind visitors are not the only ones inconvenienced by too many links in a navigation area. Recall that a mobility-impaired person with poor adaptive technology might be stuck tabbing through that morass. CODE http://joeclark.org/book/sashay/serialization/Chapter08.html#h4-2020 More: CODE http://www.niehs.nih.gov/websmith/508/o.htm 3.5 Does the site use accessible forms? Forms aren't the easiest of things to use for people with disabilities. Navigating around a page with written content is one thing, hopping between form fields and inputting information is another. CODE http://www.htmldog.com/guides/htm...
susus