forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs compliance.xml
Date Wed, 12 Feb 2003 06:30:49 GMT
crossley    2003/02/11 22:30:49

  Modified:    src/documentation/content/xdocs compliance.xml
  Log:
  Minor text tweaks. No new issues. No more resolved.
  Explained the issue with alt attributes for img elements.
  
  Revision  Changes    Path
  1.3       +31 -21    xml-forrest/src/documentation/content/xdocs/compliance.xml
  
  Index: compliance.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/compliance.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- compliance.xml	27 Jan 2003 13:47:22 -0000	1.2
  +++ compliance.xml	12 Feb 2003 06:30:49 -0000	1.3
  @@ -7,28 +7,33 @@
     <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 to the Forrest skin stylesheets to
  -ensure such compliance.
  -</p>
  +      <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
  +        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.3) validates as HTML
  +        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.3) validates as HTML
  +        The <code>avalon-tigris</code> skin currently (v0.4) validates as HTML
           4.0.1,
         </p>
         <p>
  @@ -45,6 +50,10 @@
   <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>
  @@ -53,21 +62,22 @@
     <li>
       Priority 1: alt text for images.
     </li>
  - <li>FIXME: need to list other issues here.</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>Though, examining the source I can't see any missing alts.  Perhaps it
  -  doesn't like blank alts?</note>
  +<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 (bogus?) alt complaint as above</li>
  -  <li><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>The same issues as above</li>
   </ol>
       </section> 
   
  @@ -75,13 +85,13 @@
         <title>CSS</title>
   <p>
   Jigsaw:
  -<link href="http://jigsaw.w3.org/css-validator/validator-uri.html">jigsaw.w3.org</link>
  +<link href="http://jigsaw.w3.org/css-validator/">jigsaw.w3.org</link>
   </p>
   <p>Issues ...</p>
   <ol>
  - <li>CSS 2: no errors, but some warnings</li>
  - <li>CSS 1: hover class</li>
  - <li>FIXME: need to list other issues here.</li>
  + <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> 
   
  
  
  

Mime
View raw message