Somewhere along the line in web development (late 1990’s at a guess), design was firmly decoupled from development. Then as design tools became more complex, design incorporated development of its own. This was right and proper, and in keeping with traditional software development – frontend and backend. But what we ended up with are designers who are poor coders, but expected to do that work by default. While perfection is impossible to achieve, a small amount of coding from a designer, can wreck a lot of a website’s aim, i.e. quality. Running most websites through coding standards checkers highlights the main problems.
1. Sloppy coding (missing Alt tags still irritatingly common).
2. Adopting the latest development options without considering backwards compatibility.
Point 1. is a very common guilt, including myself. It is to do with attitude – on this site, I employ a constant reasonning of “I will do it later”. Fair enough for a blog site, though I chide myself that by employing this attitude I am creating accessibility and usability issues I harp on about in a professional QA capacity. As I also develop, I do have a more sympathetic and pragmatic approach that most QA people. Designers and developers are usually overworked, so my argument is that this kind of clean-up work should at least be prioritized and scheduled. A more sensitive scenario however is that the designer in question is not sufficently skilled enough to really understand what the problems are, and hence will just repeat them.
It is not job of contract staff to point out weaknesses in development – it can simply look “bitchy”. However, testing can be an easy scapegoat for a management and development, so how can you protect your corner? Pushing the case for enforcing standards. The more chaotic the development, the easier it is to sell this case. As a minimum released code to conform to XHTML Transitional, CSS 2.1 and WCAG Level A. These are versions that I currently consider to be safe for most OS/Browser combinations AND (perhaps more importantly) maintainable. That is not expecting too much. But just passing it once is not enough, the checks should be run for every release. Anyone who resists this is plain lazy, or plain doesn’t understand even the basics of good web development. Good design is all well and good, but not if it causes problems for large sections of your audience.



