www/accessibility accessibility.html

[karl]

CVSROOT:        /web/www
Module name:    www
Changes by:     karl <karl>     14/05/04 18:20:04

Modified files:
        accessibility  : accessibility.html 

Log message:
        make all the recommendations a list, since they are; change java url to 
one that works

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

Patches:
Index: accessibility.html
===================================================================
RCS file: /web/www/www/accessibility/accessibility.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- accessibility.html  12 Apr 2014 12:39:25 -0000      1.21
+++ accessibility.html  4 May 2014 18:20:03 -0000       1.22
@@ -84,30 +84,38 @@
 
 <h3>Recommendations</h3>
 
-<p>Application software developers should learn how to use the
+<ul>
+<li>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
+interface.</li>
+
+<li>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>
+understand the appropriate 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://docs.oracle.com/javase/7/docs/technotes/guides/access/jaapi.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).</li>
 
-<ul>
-  <li>Web developers should follow the <a
+<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
+Internet Applications">ARIA standard</a>.  Furthermore,
+<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="/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
@@ -175,7 +183,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/04/12 12:39:25 $
+$Date: 2014/05/04 18:20:03 $
 <!-- timestamp end -->
 </p>
 </div>