WebAgency-Requirements 18.2 KB

Raw Blame History Permalink

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
    <title>Buy standards compliant Web sites — W3C QA</title>
    <meta name="Keywords" content="qa, quality assurance, conformance" />
<meta name="keywords" content="qa, quality assurance, conformance, validity, requirements, standards" />
<meta name="description" content="W3C QA - Why and how you should require that Web agencies deliver standard compliant Web sites" />
<link rel="schema.DC" href="http://purl.org/dc" />
<meta name="DC.Date.Created" content="2002-07-04" />
<meta name="DC.Language" scheme="RFC1766" content="en" />
<meta name="DC.Creator" content="Dominique Hazaël-Massieux" />
<meta name="DC.Publisher" content="W3C - World Wide Web Consortium - http://www.w3.org" />
<meta name="DC.Rights" content="http://www.w3.org/Consortium/Legal/copyright-documents-19990405" />

    <style type="text/css" media="all">
    @import "/QA/2006/01/blogstyle.css";
    </style>
    <meta name="description" content="" />
    <meta name="revision" content="$Id: WebAgency-Requirements.html.en,v 1.21 2010/09/15 15:58:43 dom Exp $" />
<link rel="alternate" hreflang="fr" href="WebAgency-Requirements.html.fr" title="French translation"/>

</head>
<body>
    <div id="banner">
      <h1 id="title">
	<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a><a href="http://www.w3.org/QA/"><img src="http://www.w3.org/QA/2002/12/qa.png" alt="Quality Assurance" /></a>
</h1>
    </div>

    <ul class="navbar" id="menu">
            <li><strong><a href="/QA/" title="Quality Assurance Web Site Home">[QA Home]</a></strong></li>

        <li><a href="../Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
        <li><a href="../Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
        <li><a href="#contact">Feedback</a></li>
    </ul>

<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>

</form>
</div>


    <div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->


        <div id="jumpbar">
<h2><a id="abstract" name="abstract">Abstract</a></h2>
<p>Are you in the process of ordering a Web site to a Web Agency, or maybe to the <abbr title="Information Technologies">IT</abbr> department of your company? Are you delegating the creation of your Web site to another entity? Then, you're probably aware that setting the right requirements will help create a better final product in a shorter time. Relying on open standards can help you in this task.</p>
<p>Defining the set of requirements for a Web site is always tricky: it's especially difficult to set a verifiable level of quality for the final product.</p>
<p>Adding standards compliance to your requirements helps achieve a more powerful, accessible, and maintainable final product, and leverages the energies put into standards.</p>
<p>This document details those benefits induced by the use of standards and summarizes the <a href="#reqlist">specific requirements</a> that will help you achieve this goal.</p>
<h2><a id="status" name="status">Status</a></h2>
<p>This article was written in 2002 as part of the <acronym title="World Wide Web Consortium">W3C</acronym> <a href="../../IG/">Quality Assurance Interest Group</a> work. Please send any public feedback on it to the <a href="http://lists.w3.org/Archives/Public/www-qa/"><strong>publicly archived</strong></a> mailing list <a href="mailto:www-qa@w3.org">www-qa@w3.org</a> or for private feedback to <a href="mailto:dom@w3.org">dom@w3.org</a>.</p>
<p>This document is also <a href="WebAgency-Requirements.html.fr" hreflang="fr" rel="alternate">available in French</a> and <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=WebAgency-Requirements">other languages</a>.</p>

 </div>

<div id="Content">
<h2>Buy standards compliant Web sites</h2>

<h3><a name="open" id="open">Open Standards for the Web</a></h3>
<p>Ignored for a long time by many developers, standards such as <a href="/Protocols"><abbr title="HyperText Tranport Proctol">HTTP</abbr></a>, <a href="/MarkUp/"><abbr title="HyperText Markup Language">HTML</abbr></a> or <a href="/XML/"><abbr title="eXtensible Markup Language">XML</abbr></a> are <strong>at the very core of the success of the Web</strong>. The current trend of stressing standards compliance on the Web is not due to chance: they are a win-win for all participants.</p>
<p>Developed by experts and with input from the whole Web community, standards work together to provide the foundation to build increasingly powerful applications. Standards are <strong>the result of a lot of energy and expertise</strong> and are <strong>available for free</strong>: don't miss the opportunity to benefit from their leveraging effect!</p>
<h4><a name="powerful" id="powerful">For a more powerful Web site</a></h4>
<p>On the Web, being up-to-date with the latest technologies is a difficult exercise: choosing the wrong tool or architecture can lead to losses in money, time, or customers.</p>
<p>By using standards, your Web site's foundation is built upon technologies that have been developed and tested by leading experts in the Web community. For example, the W3C Process ensures that a technology reaching its last state of development has been implemented into several compatible products. With almost 500 companies and organizations from the IT world contributing <abbr title="Research and Development">R&amp;D</abbr> efforts to the production of W3C standards, these standards are truly the <strong>leading edge of the Web</strong>.</p>
<p>Standards organizations, like the W3C, build a consensus among these groups and experts to maintain and develop consistent architectural principles. Groups such as the <a href="/2001/tag/">Technical Architecture Group</a> at W3C make sure that technologies can be combined nicely, building a Web coherent with the decisions that allowed the Web to grow so quickly.</p>
<p>Orienting your choices toward standards means getting the latest innovations, but only those that are solid enough to gather consensus, and hence, the <strong>technologies that are here to stay</strong>:</p>
<ul>
<li>HTML has a non-diminishing success for its 12 years of existence, thanks to the careful developments and innovations it has integrated during that time;</li>
<li>HTTP is a network protocol that finds new usages every so often: originally used to <q>surf</q> the Web, its recent use as a messaging protocol through <a href="/2000/xp/Group/">SOAP</a> is only a step toward the <a href="/2002/ws/">Web Services</a> deployment; and</li>
<li>XML, only 4 years old, is used almost everywhere nowadays, and new use cases of its flexibility are regularly discovered and implemented.</li>
</ul>
<p>More recently achieved standards such as <a href="/Graphics/SVG/"><abbr title="Scalable Vector Graphics">SVG</abbr></a> and <a href="/P3P/">P3P</a> are catching on quickly, and still hold many possible new applications!</p>
<h4><a name="maintainance" id="maintainance">Reduced maintenance costs</a></h4>
<p>Everything goes very fast on the Web, and maintaining a Web site can imply fairly big operational costs. Without a compliant Web site, migrating to new platforms and adding functionalities to your applications can be expensive operations.</p>
<p>However, if your applications are developed on <strong>open</strong> standards, your <strong>applications won't depend on a unique provider</strong>:</p>
<ul>
<li>you won't be stuck with formats you don't have access to;</li>
<li>you can influence how the standards are developed; and</li>
<li>you can benefit from the best backward- and even forward-compatibility.</li>
</ul>
<p>Have you ever had difficulties re-using  existing code produced by a former provider? Even if you haven't, you can be sure that anything developed for a unique product ("browser X is the most popular, why bother with the others?") or using non-standard technologies won't scale with time and your needs, which means that it will cost a lot to maintain.</p>
<p>Because standards are built to be combined, developing new applications from an existing base is much easier: the tools to manipulate open technologies get more sophisticated, more numerous, and more powerful all the time. Moving your Web pages to <a href="/MarkUp/"><abbr title="eXtensible HyperText Markup Language">XHTML</abbr></a>, for instance, means that you can easily transform the data to other formats using <a href="/Style/XSL/"><abbr title="eXtensible Stylesheet Language Transformations">XSLT</abbr></a> or ask for a powerful publishing system with validating mechanisms using <a href="/XML/Schema">XML Schema</a>. And for each of these operations, you can choose from a wide range of tools from many different producers.</p>
<p>Finally, standards usually <strong>avoid the infamous <a href="http://www.antionline.com/jargon/featurecreep.php">feature creep</a></strong> of other formats and clearly separate orthogonal applications: using <a href="/Style/CSS/"><abbr title="Cascading StyleSheets">CSS</abbr></a> lets you cleanly separate the presentation from the structure of your data. This very same separation also saves in the operational costs: using CSS means less HTML code for each page, and therefore bandwidth saving.</p>
<p>Your data are probably one of your company's biggest assets. Don't put them in proprietary formats you cannot control and which limit potential solution providers. You never know what the future holds, so invest in <strong>technologies that already belong to the future</strong>.</p>
<h4><a name="accessible" id="accessible">Benefit from accessibility designs</a></h4>
<p>Making a Web site accessible is both beneficial and challenging:</p>
<ul>
<li><em>beneficial</em> because it broadens your potential audience and makes it much more usable for everyone &mdash; some level of accessibility is also required by law in a growing number of countries; and</li>
<li><em>challenging</em> because it requires thorough designing and testing to address diverse issues.</li>
</ul>
<p>Thanks to various efforts (<a href="/WAI/">the Web Accessibility Initiative</a> for instance), <strong>accessibility has been integrated into an important number of standards</strong>, either natively or by using techniques specifically designed for them. Using standards technologies lets you benefit directly from design decisions that have been tested by the Web community and are complemented by a large set of tools.</p>
<p>More generally, open standards are reviewed from important and difficult points-of-view. For example, W3C standards are checked not only against <a href="/WAI/">accessibility</a> features, but against <a href="/International/">internationalization</a> capacities, and <a href="/2001/di/">device independence</a>, which guarantees their capacity to scale quickly to new audiences.</p>
<p>Don't be fooled: sooner or later, your site (be it public, an extranet, or an intranet) will need to be available for more people with increasingly demanding requirements.</p>
<h4><a name="best" id="best">Accept only the best</a></h4>
<p>More and more, the Web will be the <strong>central key for your knowledge management</strong> with initiatives such as the <a href="/2001/sw/">Semantic Web</a>. Hence your site must have very <strong>strong requirements</strong>, and <strong>compliance to standards</strong> must be part of them to guarantee the general quality. There are <a href="/QA/Tools/">tools available to check</a> that the final product complies with these standards.</p>
<h3><a name="reqlist" id="reqlist">What should you include in your requirements list?</a></h3>
<p>You should set compliance to standards as a generic principle, but having a list of actual requirements will certainly make everybody's life easier:</p>
<table border="1" summary="The list of requirement you may ask with their rationale and the tool to test the final product">
<thead>
<tr>
<th scope="col">Requirement</th>
<th scope="col">Details</th>
<th scope="col">Rationale</th>
<th scope="col">Test tool</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">Use valid (X)HTML</th>
<td>Using valid HTML means having an HTML code that follows one of the <abbr title="Document Type Definition">DTDs</abbr> of the HTML specification. Your best choice is valid <code>XHTML strict</code> markup: <code>XHTML</code> means that the code will benefit from all the XML power, and <code>strict</code> ensures your site won't mix presentation markup with the structure.</td>
<td>Valid HTML code is a first step toward more compatibility with browsers and better rendering on the latest ones. Using only strict HTML (that is, the Strict HTML DTD) makes the site easier to maintain and evolve.</td>
<td>The <a href="http://validator.w3.org/">W3C HTML Validator</a> is one of the many options available. <a href="/QA/Tools/LogValidator/">The LogValidator</a> is especially helpful in maintaining a valid Web site.</td>
</tr>
<tr>
<th scope="row">Use extensively valid CSS</th>
<td>Avoid any presentational markup and keep all the layout features in well-defined CSS style sheets.</td>
<td>Linked style sheets allow presentation to be decoupled completely from the page structure of your site, and lets you quickly change its layout and rendering. It also guarantees that everybody can adjust the rendering to their needs and tastes.</td>
<td>The <a href="http://jigsaw.w3.org/css-validator/">CSS Validator</a> detects any non-compliant use of the CSS technologies.</td>
</tr>
<tr>
<th scope="row">Use HTTP properly</th>
<td>Make sure that each page of your site is accessible with a stable address (<abbr title="Uniform Resource Locator">URL</abbr>) and that the HTTP caching properties are set correctly. Make sure if you migrate to a new site version that the URLs are either kept as is or at least redirected to the new ones.</td>
<td>HTTP is a very powerful protocol and you get most of its power with stable URLs and an efficient caching system: bookmarks and links don't break, network access is faster, users are happy!</td>
<td>The <a href="http://validator.w3.org/checklink">W3C Link Checker</a> can provide some help. Besides, the <a href="/TR/chips">advices given in the <cite>Common HTTP Implementation Problems</cite> Note</a> can help assess what needs to be respected.</td>
</tr>
<tr>
<th scope="row">Use SVG and <a href="/Graphics/PNG/"><abbr title="Portable Network Graphics">PNG</abbr></a> for graphics</th>
<td>Use PNG for raster images, and SVG for all others.</td>
<td>PNG is a much more capable format than other binary formats for raster images because it provides better compression, more options, and it's free. The best format you should require is SVG: it's scalable, XML-based, very light, and has <em>a lot</em> of capabilities, for example, animation using <a href="/AudioVideo/"><acronym title="Syncronized Multimedia Integration Language">SMIL</acronym></a>, which is supported on cell phones, etc.</td>
<td>N/A</td>
</tr>
<tr>
<th scope="row">Use techniques to make your content accessible</th>
<td><a href="/WAI/Resources/#te">Details</a>.</td>
<td>Making a site accessible benefits all of your users, and broadens your current audience. This requirement may be required by law in some countries.</td>
<td>See <a href="/WAI/ER/existingtools.html#Evaluation">Evaluation Tools for Web Content Accessibility</a>.</td>
</tr>
<tr>
<th scope="row">Use standards scripting languages</th>
<td>Use the <a href="/DOM/"><acronym title="Document Object Model">DOM</acronym></a> <abbr title="Application Programming Interface">API</abbr> combined with Ecmascript (but don't make the use of scripts mandatory to navigate in the site!).</td>
<td>DOM and Ecmascript (the common standard behind Javascript and JScript) are the best way to go to get interoperable scripts to create animations in your Web site. But do not forget your users that don't have these scripting capacities enabled.</td>
<td>N/A</td>
</tr>
</tbody>
</table>
</div>
<!-- Footer -->
<hr />
<div class="disclaimer">
<a href="http://validator.w3.org/check/referer"><img src="http://validator.w3.org/images/vxhtml10" alt="Valid XHTML 1.0!" height="31" width="88" /></a><span class="dot">&nbsp;&middot;</span>
<a href="/WAI/WCAG1AAA-Conformance" title="Explanation of Level Triple-A Conformance"><img height="32" width="88" src="http://www.w3.org/WAI/wcag1AAA" alt="Level Triple-A conformance icon, W3C-WAI Web Content Accessibility Guidelines 1.0" /></a>
<address class="author">
Created Date: 2002-07-04 by <a href="mailto:dom@w3.org">Dominique Haza&euml;l-Massieux</a>
<br />
Last modified $Date: 2010/09/15 15:58:43 $ by $Author: dom $
</address>
<p class="policyfooter">
<a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &#xa9; 2000-2003
<a href="/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&#xae;</sup>
(<a href="http://www.lcs.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
<a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
<a rel="Copyright" href="/Consortium/Legal/copyright-documents">document use</a> and
<a rel="Copyright" href="/Consortium/Legal/copyright-software">software licensing</a> rules apply. Your interactions with this site are in accordance with our
<a href="/Consortium/Legal/privacy-statement#Public">public</a> and
<a href="/Consortium/Legal/privacy-statement#Members">Member</a> privacy statements.
</p>
</div>
</div>
</body>
</html>