<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd">
<document> 
  <header> 
    <title>Standards Compliance</title> 
  </header> 
  <body> 
    <section>
      <title>Introduction</title>
      <p>
        Forrest is still quite young, so there are known issues.
        Standards compliance is a definite major goal. Please send patches
        for the Forrest skin stylesheets to ensure such compliance.
      </p>
      <note>
        For your testing, use the Forrestbot generated website, because that
        reflects the current CVS ...
        <link href="http://forrestbot.cocoondev.org/sites/xml-forrest/">http://forrestbot.cocoondev.org/sites/xml-forrest/</link>
      </note>
    </section> 

    <section>
      <title>HTML</title>

      <p>
        Tested using the W3C HTML Validation Service (<link
          href="http://validator.w3.org/">validator.w3.org</link>). The
        index.html page of Forrest sites will have a link to this validator,
        unless the user has turned this off.
      </p>
      <p>
        The <code>forrest-site</code> skin currently (v0.4) validates as HTML
        4.0.1,
      </p>
      <p>
        The <code>avalon-tigris</code> skin currently (v0.4) validates as HTML
        4.0.1,
      </p>
      <p>
        <code>krysalis-site</code> skin does not validate, due (at least) to
        incorrectly nesting lists (&lt;ul&gt;&lt;ul&gt;&lt;li...) forming the
        menu.  Some CSS expertise needed to eliminate this without hurting the
        presentation.
      </p>
    </section> 

    <section>
      <title>WAI</title>
<p>See
<link href="http://www.w3.org/WAI/">Web Accessibility Initiative (WAI)</link>
</p>
<p>
  There are actually many accessibility issues with the heavy use of
  tables and images. These skins are gradually being improved.
</p>
<p>
Bobby with WAI:
<link href="http://bobby.watchfire.com/">bobby.watchfire.com</link>
</p>
<p>Issues ...</p>
<ol>
  <li>
    Priority 1: alt text for images.
  </li>
  <li>Priority 2: <link
      href="http://bobby.watchfire.com/bobby/html/en/gls/g41.html">Explicitly
      associate form controls and their labels with the LABEL element</link>.
    Perhaps we could have a label hidden with CSS?</li>
  <li>FIXME: need to list other issues here, or attend to them.</li>
</ol>
<note>The forrest-site skin does not have any missing alts. Perhaps Bobby
  does not like the trick with empty alt attributes. However, it only
  complains about the two in the footer, and not about the other 40.</note>
<p>
Bobby with U.S. Section 508 Guidelines:
<link href="http://bobby.watchfire.com/">bobby.watchfire.com</link>
</p>
<p>Issues ...</p>
<ol>
  <li>The same issues as above</li>
</ol>
    </section> 

    <section>
      <title>CSS</title>
<p>
Jigsaw:
<link href="http://jigsaw.w3.org/css-validator/">jigsaw.w3.org</link>
</p>
<p>Issues ...</p>
<ol>
 <li>CSS 2: No errors. Some warnings.</li>
 <li>CSS 1: Errors: hover class, @media-print. Some warnings.</li>
 <li>FIXME: need to list other issues here, or attend to them.</li>
</ol>
    </section> 

    <section>
      <title>Other discussion</title>
<p>Please add links to relevant forrest-dev email thread here:</p>

    </section> 
  </body>
</document>
