LocalAction 20.4 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>W3C QA - Think globally, Act locally</title>
        <meta name="Keywords" content="qa, quality assurance, conformance, validity, test suite, evangelism, standards, local, action" />
        <meta name="Description" content="W3C QA - a local approach to web standards education and outreach effort" />
        <link rel="schema.DC" href="http://purl.org/dc" />
        <meta name="DC.Subject" lang="en" content="evangelism, standards, local, action" />
        <meta name="DC.Title" lang="en" content="Think globally, Act locally" />
        <meta name="DC.Description.Abstract" lang="en" content="a local approach to web standards education and outreach effort" />
        <meta name="DC.Date.Created" content="2002-08-12" />
        <meta name="DC.Language" scheme="RFC1766" content ="en" />
        <meta name="DC.Creator" content="Olivier Thereaux" />
        <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>
</head>
<body>

<!-- Header -->
	    <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="../IG/" title="The Quality Assurance Interest Group">QA IG</a></li>
		        <li><a href="../Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
                        <li><a href="./Tools/" title="Validators and other Tools">Tools</a></li>
        		<li><a href="/QA/IG/#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">

                        <p><strong>In a global strategy to improve the overall quality of the websites,
                        local communities, city hall, city library, school,
                        university, etc. may be a good first target for punctual evangelism effort.</strong>
                        </p>

                        <h2 id="status">About this document</h2>
                        <p>This article has been produced as part of the <acronym title="World Wide Web Consortium">W3C</acronym> <a href="/QA/IG/">Quality Assurance Interest Group</a> work. Please send any public feedback on it to the <a href="http://lists.w3.org/Archives/Public/public-evangelist/"><strong>publicly archived</strong></a> mailing list <a href="mailto:public-evangelist@w3.org">public-evangelist@w3.org</a> or for private feedback to <a href="http://www.w3.org/People/olivier/">olivier Thereaux</a> &lt;<a href="mailto:ot@w3.org">ot@w3.org</a>&gt;.</p>


                        <h3><a name="sotd-translat" id="sotd-translat">Translation</a></h3>

                        <p>Translation of this document is welcome. Please check the <a href="http://www.w3.org/Consortium/Translation/#volunteer">Translations instructions</a>
                                and make sure you warn others on the <a href="http://lists.w3.org/Archives/Public/w3c-translators/">translators mailing-list</a> before you get started.</p>

			</div>

<!-- content -->
<div id="Content">
<h2>Think globally, Act locally</h2>


<h3 id="strategy">A local approach to web standards education</h3>

<p>Web Standards are here, documented, implemented in modern Web browsers, but many developers, around the world, seem to ignore that fact. They also seem to ignore that <a href="http://devedge.netscape.com/viewsource/2003/why-web-standards/">Web Standards bring a lot to the table</a> in terms of accessibility, ease of maintenance and coding.</p>
<p>Why are Web standards so little known in non-English-speaking regions of the world? The answer is complex, but here are a few takes:</p>
<ul>
   <li>The language barrier, as documentation is mainly written in English;</li>
   <li>The inevitable inertia of human being: "why, as a Web developer, should I change my old habits?";</li>
   <li>The fact that modern browsers are not well known and largely ignored by webmasters;</li>
   <li>The perceived complexity of W3C recommendations (more precisely, the fact that they are normative and not aimed at Web developers);</li>
   <li>The benefits of Web standards are not (yet) perceived by Web developers.</li>
</ul>

<p>Basically, it comes down to marketing and education: specifications are well done, but surely need evangelists to make them accessible to the average developer who may not have the patience to learn how to read specification in English, but may want to read easy-to-understand, ready-to-use documentation in his mother tongue.</p>

<p>Besides, it is quite obvious that marketing and education works better
face-to-face: it is always easier to convince someone when you can discuss with
this person in front of a coffee. Those of us who have tried to explain
the need to follow Web Standards by sending a 'nice, polite, informative
e-mail with loads of links to comprehensive resources' and failed nevertheless
know that face-to-face dialog is a more efficient medium for pedagogy than most
remote methods.</p>

<h3><a name="group" id="group">You are not alone : Regrouping good will</a></h3>

<p>Taking over the task of promoting Web standards in a given country can be exhausting.
Actually, it may not even be doable by a single person (wait, maybe in the Vatican ;-)
Therefore, the first thing to do is to find other people in your area,
speaking the same language, having the same willing to help the Web move to the next step.
How could you achieve that?</p>

<h4><a name="associations">Open-source and Free Software associations</a></h4>
<p>Such assocations are concerned by Web standards and are active in discouraging
the monopoly of a single browser; they care about Web standards because of their
inherent interoperability. Contacting such local associations could help you
in your gathering of contributors to the effort you are undertaking.
Also, such associations can help you in hosting a common tool for contact.
See below.</p>

<h4><a name="meetup">Meetup service</a></h4>
<p>The <a href="http://www.meetup.com/">MeetUp service</a> enables you to physically
meet up with other people around a cup of coffee and some common interest.
In our case, the <a href="http://webstandards.meetup.com/">Web Standards meetup</a>
is probably the best choice, while the
<a href="http://webdesign.meetup.com/">Web Design meetup</a> is also interesting.</p>

<h4><a name="usenet">Usenet Newsgroups and Website forums</a></h4>
<p>Usenet newsgroups and Web forums dedicated to authoring and browsers can be
a nice place to prospect for fellow web developers that may have an interest for W3C standards.</p>

<h3><a name="getting-started">Getting Started</a></h3>
<p>Once you have met (in real life or online) these people who share the same interest,
the more difficult is to unify those people, and to come up with a plan.
What was done with the newly created Interop group in Paris (France) for example,
was to make an inventory of existing or burgeoning projects.
Then people around the room were asked to which project they would like to participate,
and what would be the boundaries of each project, so that we eliminate work
replication as much as possible. After that, was chosen a mean of discussing together the
common efforts, which was basically an existing mailing-list.
You may also consider using a Wiki, on top of the mailing list.</p>

<h4 id="target">Finding a proper target</h4>
<p>"Public" sites are a good target, for two reasons.</p>

<ul>
<li> Proximity : you can actually go see the person in charge of the
   website and offer to help</li>
<li> Quality constraints : it may sound manichean, but where the private
   sector is driven by marketing (hence the "no thank you, my customer
   base uses IE5/NS4/your-browser-here" typical answer), the public
   sector has some obligations towards quality. A few examples :
   <a href="http://www.section508.gov/">section 508</a>
   for accessibility of government-funded websites in the USA,
   or the <a href="http://www.e-government.govt.nz/docs/web-guidelines-v1/">new-Zealand web guidelines</a>.
</li>
</ul>

<h4 id="localinitiative">Starting local initiatives</h4>

<p>There is space for a nice initiative where volunteers would
convince local authorities to improve the quality of their websites,
and possibly helping them to do so.</p>

<p>An annex project would be to author a paper with two parts : advice
for the "evangelist" (like "be friendly - remember : you're here to
help" or "try to find some local data for your argumentation"), and key
information for the "people in charge" in public administrations. </p>


<p>Your strategy and work will be very different whether you are in an English-speaking part
of the world or not: The english-speaking world is quite an exception, as there is already
a lot of documentation available, and therefore awareness of the problem, whereas in other places,
English is not well read, so bad habits tend to stick longer because lack of information.
</p>

<p>Below is a summary of the projects put together in France / French-speaking part
of the world to promote Web standards, in the hope that it can be useful to other regions.
</p>

<h3><a id="projects" name="projects">List of potential projects</a></h3>
<p>Here is a list of projects to bridge the gap between the
(recommendations of the) W3C and Web developers that one person (or group)
can undertake locally. Some of these projects, as mentioned earlier, are
adapted to non-english-speaking parts of the world, while others are adapted
to all contexts.</p>

<h4><a name="translation">Translating content</a></h4>
<p>There is a very significant amount of material already available in English that can be leveraged. Either as an individual or a group, you can start translating some of this content</p>
<ul>
   <li>Web Standards Project (WaSP) has an interesting <a href="http://www.webstandards.org/learn/faq/" title="What are web standards, and why should I use them">FAQ</a> which can help as an introduction to Web standards. It has already been translated into French, Italian and Japanese. Netscape, with <a
 href="http://devedge.netscape.com/">DevEdge</a> has also content in <a href="http://devedge.netscape.com/index_ja.html">Japanese</a>, <a href="http://devedge.netscape.com/index_pt_br.html">Portuguese</a> and <a href="http://devedge.netscape.com/index_fr.html">French</a>.</li>
   <li>Some W3 recommendations are <a href="http://www.w3.org/Consortium/Translation/">already translated in various languages</a>. See if you can contribute to this effort.</li>
   <li>Various other sources, such as <a href="http://www.alistapart.com/">AListApart</a>, <a href="http://evolt.org/">Evolt</a> or other web logs provide very interesting content that is worth translating. It may be interesting to create a web site to host all those translations, which would publish new documents on a regular basis. In France, we have re-activated an existing site, dubbed <a href="http://pompage.net/">Pompage.net</a>, to do this. A motivated group leader takes suggestions for translations, contacts original author for translation authorization, and manages translation and proofreading before publication.</li>
</ul>

<h4><a name="tutorials">Providing technical, Standards-based tutorials</a></h4>
<p>While it may currently exist several resources for Web developers to learn HTML, most of those are promoting development techniques inherited for the last century, making extensive use of tables, GIF-spacers and font-tag-based design. After quite some effort, it has not been possible --at least in France-- to convince people who manage these resources to upgrade their content to teach standards-based design. Therefore, a dozen volunteers (from a <a href="news:fr.comp.infosystemes.www.auteurs">French Usenet Newsgroup</a>) has started creating some content that would teach that. The resulting effort, named <a href="http://openweb.eu.org/">OpenWeb</a>, is aimed at 4 different audiences:</p>
<ol>
   <li>Decision-makers (how can standards can benefit my company), </li>
   <li>Beginners (how do I create a Web page), </li>
   <li>Experienced developers (how do I use standards to be better at my job), and </li>
   <li>Gurus, who already know the specs by heart, but are willing to learn more of bleeding edge Web design</li>
</ol>
<p>While it has been exhausting to build this Web site (professional-level design, XSLT-based backend, currently more than 60 articles), it was surely and exhilarating experience, which has taught a lot to each of us, leveraging each other's experience with all the technologies involved. Furthermore, creating original content is very rewarding. Creating such a site shows that it is possible to create a very good-looking, real-life-sized site, and challenged existing HTML-teaching Web sites to upgrade their content.</p>

<h4><a name="helping">Helping Web developers switch to standards</a></h4>
<p>While Web developers now have some technical tutorials about Web standards, they also need assistance while teaching themselves these new techniques. It may prove itself difficult, because one often tries to replicate with CSS old table-based techniques. In many cases, discussing his/her problem with more experienced developers, the person will find the experience more rewarding. Such experience sharing can be done on Usenet newsgroups, Web site forums or mailing lists. For example, OpenWeb contributors often participate to <a href="news:fr.comp.infosystemes.www.auteurs">FCIW.auteurs</a> and <a href="news:fr.comp.infosystemes.www.navigateurs">FCIW.navigateurs</a> Usenet groups, the <a href="http://pompage.net/liste/">Pompeurs</a> mailing list, and other <a href="http://forum.hardware.fr/forum1.php3?cat=12&amp;config=&amp;interface=&amp;subcat=402">web site forums</a>.</p>

<h4><a name="contacting">Contacting Webmasters owning incompatible Web sites</a></h4>
<p>Because of a chicken-and-egg situation, incompatible Web sites have the tendency to remain incompatible over time with modern, alternative browsers. Why is that? Because standards-compliant browser users avoid these services. Therefore, the alternative browsers do not look significant in terms of marketshare when the webmasters looks at the site's statistics. While users of such services should take the initiative of contacting these Websites, an existing association, such as the open-source association mentioned before, can be of great help. Because they represent many users at ounce, they do have more impact when they contact Web sites. Very interesting progress has been made in this field in France by the <acronym title="Association Francophone des Utilisateurs de Linux et des Logiciels Libres / Free Software association">AFUL</acronym>/<acronym title="Association Pour la Promotion et la Recherche en Informatique Libre">APRIL</acronym> <a href="http://www.aful.org/gdt/interop/" title="Interoperability Working Group">Interop project</a>. It is to be noticed that a similar endeavor is being done by the <a href="http://www.mozilla.org/projects/tech-evangelism/">Mozilla Technology Evangelism project</a>, which may be used to unify efforts in a global manner.</p>

<h4><a name="accessibility">Leveraging Accessibility policies</a></h4>
<p>As new policies about people with disabilities are made, Web Content Accessibility is becoming a major challenge for big web sites in many countries. Webmasters suddenly realize that their existing sites are far from being accessible. By design, Web standards may help a lot in achieving accessibility. Showing the relationship between Web standards and accessibility may be a way to get attention from large private or governmental Web sites. For this very reason, the OpenWeb project has a section on accessibility and is itself accessible.</p>

<h4><a name="buzz">Creating buzz</a></h4>
<p>With the fast-growing number of blog-tools, it has now become very easy to publish information on the Web. Creating your own blog on Web development based on W3C standards is also an interesting way to share your knowledge and progress in this field. It also helps raising awareness about modern browsers, and recent techniques for Web design. If you consider starting a Web log, then talking about Web standards could be the excuse you have been waiting for, just make sure your blog is standards-compliant, and even accessible!</p>

<h4><a name="browsers">Promoting modern browsers</a></h4>
<p> This last point may sound a bit off-topic, but promoting modern, standards-comformant browser also helps the cause of web standards. They tend to offer better standard conformance than other older browsers, along with very useful tools for the developers, such as Mozilla's DOM-Inspector and JS-Debugger.</p>

<p>In our example case in France, they chose to translate the <a href="http://mozfr.mozdev.org/">Mozilla documentation into French</a>, while other groups <a href="http://frenchmozilla.sourceforge.net/">translated the application itself</a> or the <a href="http://mozillazine-fr.org/">news around the project</a>.</p>


<h3 id="post-scriptum">Post-Scriptum</h3>
<h4 id="Acknowledgements">Acknowledgements</h4>
<dl>
<dt>Authors</dt>
<dd><a href="http://www.nitot.com">Tristan Nitot</a>,</dd>
<dd><a href="/People/olivier/">olivier Thereaux</a>, W3C,</dd>
<dt>Editor</dt>
<dd>
<a href="/People/olivier/">olivier Thereaux</a>, W3C
</dd>
</dl>

<p>The authors and editor want to thank the following people for their contribution:</p>

<ul>
	<li>Karl Dubost and Dominique Haza&euml;l-Massieux, W3C, for their initial input</li>
	<li>Terje Bless, for the idea of making this article out of the original e-mail message,
	and the title suggestion</li>
	<li>... and all the participants of the
	<a href="http://lists.w3.org/Archives/Public/public-evangelist/">public-evangelist@w3.org</a>
	mailing-list.</li>
</ul>

</div>
<!-- Footer -->


      </div><!-- End of "main" DIV. -->
	<address>
	Created Date: 2002-08-12 by <a href="mailto:ot@w3.org">Olivier Thereaux</a><br />
	Last modified $Date: 2007/02/06 09:05:14 $ by $Author: ot $
	</address>


    <p class="copyright">
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 1994-2006
      <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>&reg;
      (<a href="http://www.csail.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="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
      <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
      and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
      rules apply. Your interactions with this site are in accordance
      with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
      <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
      statements.
    </p>


  </body>
</html>