www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/accessibility accessibility.html


From: Matt Lee
Subject: www/accessibility accessibility.html
Date: Mon, 17 May 2010 19:15:17 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Matt Lee <mattl>        10/05/17 19:15:17

Modified files:
        accessibility  : accessibility.html 

Log message:
        added links to libreplanet/mailing list, as well as better formatting 
of resources section...
        
        note: this page has a little bit of custom CSS, which could be copied 
into layout.css, i just didn't want to be the one to make that decision.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/accessibility/accessibility.html?cvsroot=www&r1=1.3&r2=1.4

Patches:
Index: accessibility.html
===================================================================
RCS file: /web/www/www/accessibility/accessibility.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- accessibility.html  26 Apr 2010 13:21:15 -0000      1.3
+++ accessibility.html  17 May 2010 19:15:13 -0000      1.4
@@ -1,16 +1,37 @@
 <!--#include virtual="/server/header.html" -->
 <title>GNU Accessibility Statement</title>
+<style type="text/css">
+
+#conversation { width: 300px; background-color: #bdf; border: 1px solid #999; 
float: right; padding: 12px; margin: 12px;  }
+
+#conversation h5 { font-size: 24px !important; text-align: center;}
+
+#conversation li { margin-bottom: 0.5em; }
+
+</style>
+
 <!--#include virtual="/server/banner.html" -->
 
 <h2>GNU Accessibility Statement</h2>
 
-<p>Project GNU urges people working on free software to follow
-standards and guidelines for universal accessibility on GNU/Linux and
-other free operating systems.  Multi-platform projects should use the
-cross platform accessibility interfaces available that include
-GNU/Linux distributions and the GNOME desktop.  Project GNU also
-advises developers of web sites to follow the guidelines set forth by
-the World Wide Web Consortium's Web Accessibility Initiative.</p>
+<p><a href="/gnu/">Project GNU</a> urges people working on free
+software to follow standards and guidelines for universal
+accessibility on GNU/Linux and other free operating systems.
+Multi-platform projects should use the cross platform accessibility
+interfaces available that include GNU/Linux distributions and the
+GNOME desktop.  Project GNU also advises developers of web sites to
+follow the guidelines set forth by the World Wide Web Consortium's Web
+Accessibility Initiative.</p>
+
+<div id="conversation">
+  <h5>Join the conversation</h5>
+
+  <ul>
+    <li><a href="http://lists.gnu.org/mailman/listinfo/accessibility";>GNU 
accessibility mailing list</a></li>
+    <li><a href="http://groups.fsf.org/wiki/Group:Accessibility";>LibrePlanet 
accessibility group</a>
+  </ul>
+  
+</div>
 
 <p>According to the United Nations in 2005, there were 600 million
 people with disabilities in the world.  To use computers, many of them
@@ -74,27 +95,35 @@
 <h3>Recommendations</h3>
 
 <p>Application software developers should learn how to use the
-accessibility features of the
-<acronym title="Integrated Development Environment">IDE</acronym> or
-toolkit they employ to build their user interface.  Programmers who
-need to implement access technology, or work on a desktop or OS-level
-accessibility problem, will need to understand the accessibility
-<acronym title="Application Programming Interface">API</acronym>, and
-should choose the one that is compatible with free OS/desktops.  These
-include the GNOME accessibility API (GNU/Linux platforms only), the
-Java accessibility API (GNU/Linux and Windows) and iAccessible2
-(GNU/Linux and Windows).</p>
-
-<p>Web developers should follow the guidelines at
-<a href="http://www.w3c.org/wai";>http://www.w3c.org/wai</a> and, for
-complex web applications, the developers should follow the Aria
-standard, also to be found at the World Wide Web Consortium web site.
-FANGS enables web developers to see how a screen reader will handle
-the web pages they are developing.  Nontrivial Javascript code
-distributed to the user should be free software
-(<a 
href="/philosophy/javascript-trap.html">http://www.gnu.org/philosophy/javascript-trap.html</a>),
-and please don't invite users to do something on a server that they
-could conceivably do on their own computers.</p>
+accessibility features of the <acronym title="Integrated Development
+Environment">IDE</acronym> or toolkit they employ to build their user
+interface.  Programmers who need to implement access technology, or
+work on a desktop or OS-level accessibility problem, will need to
+understand the accessibility <acronym title="Application Programming
+Interface">API</acronym>, and should choose the one that is compatible
+with free OS/desktops.  These include the <a 
href="http://library.gnome.org/devel/accessibility-devel-guide/stable/index.html.en";>GNOME
 accessibility API</a>
+(GNU/Linux platforms only), the <a 
href="http://java.sun.com/javase/technologies/accessibility/docs/jaccess-1.3/doc/core-api.html";>Java
 accessibility API</a> (GNU/Linux and
+Windows) and <a 
href="http://www.linuxfoundation.org/collaborate/workgroups/accessibility/iaccessible2";>iAccessible2</a>
 (GNU/Linux and Windows).</p>
+
+<ul>
+  <li>Web developers should follow the <a
+href="http://www.w3c.org/wai";>W3C web accessibility guidelines</a>
+and, for complex web applications, the developers should follow the <a
+href="http://www.w3.org/WAI/intro/aria"; title="Accessible Rich
+Internet Applications">ARIA standard</a>.</li>
+<li><a
+href="http://www.standards-schmandards.com/projects/fangs/";>FANGS</a>
+enables web developers to see how a <a
+href="http://en.wikipedia.org/wiki/Screen_reader";>screen reader</a>
+will handle the web pages they are developing.</li>
+<li><a href="<a
+href="/philosophy/javascript-trap.html">Nontrivial Javascript code
+distributed to the user</a> should be free software.</li>
+<li>Please don't invite users to <a 
+href="/philosophy/who-does-that-server-really-serve.html">do something
+on a server that they could conceivably do on their own
+computers</a>.</li>
+</ul>
 
 </div>
 <!--#include virtual="/server/footer.html" -->
@@ -111,12 +140,10 @@
 <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
 </p>
 
-<p>
-Please see the
-<a href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting
-translations of this article.
-</p>
+<p> Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.  </p>
 
 <p>Copyright &copy; 2010 Free Software Foundation, Inc.</p>
 
@@ -133,7 +160,7 @@
 
 <p>Updated:
 <!-- timestamp start -->
-$Date: 2010/04/26 13:21:15 $
+$Date: 2010/05/17 19:15:13 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]