The British Standards Institution recently released official guidelines on making websites more accessible for the disabled, as well as older surfers. Also included in the release (catchily named BS 8878) are recommendations on accessibility testing using automated tools. And really, why would we want to exclude these people from our sites? Unless they are using
BrowserShots may not be anywhere near as fast, or boast the same tools (overlay, onionskin etc) of Adobe’s BrowserLabs, but it does have the ability to check more browsers than its counterpart. A total of 72 browsers (as of writing) can be tested on your budding designs, some of which you’ll probably never have heard
This great little guide from Seybold Seminars gives you a run-down of why using tables for layout is bad, what the benefits of switching to CSS are and how you can go about it. If you’re new to web development, this is a one-stop-shop on how to avoid tabular pitfalls. The guide may be old
Historically, finding something specific like doctype declarations on the W3C website was a chore. With many useful bits of information usually buried in extensive specification documents, finding the exact snippet you were after could be a time-consuming process. Thankfully, these days they’ve provided a single page with a wide selection of doctypes ready for copy-pasting.