gnome-devel-docs r559 - in trunk: . gadg



Author: vpalexander
Date: Sat Aug 16 16:03:33 2008
New Revision: 559
URL: http://svn.gnome.org/viewvc/gnome-devel-docs?rev=559&view=rev

Log:
del dead link

Modified:
   trunk/ChangeLog
   trunk/gadg/gad.xml

Modified: trunk/gadg/gad.xml
==============================================================================
--- trunk/gadg/gad.xml	(original)
+++ trunk/gadg/gad.xml	Sat Aug 16 16:03:33 2008
@@ -187,7 +187,7 @@
 <section id="gad-api">
 <title>The Accessibility API</title>
 <para>
-Here are a few of the basic API calls you may need to use in your application to ensure it works well with assistive technologies. The full accessibility API is extensive, to allow you to write your own accessible custom widgets for example. The full documentation can be found at <ulink url="http://developer.gnome.org/doc/API/2.0/atk/book1.html";>http://developer.gnome.org/doc/API/2.0/atk/book1.html</ulink>.
+Here are a few of the basic API calls you may need to use in your application to ensure it works well with assistive technologies. The full accessibility API is extensive, to allow you to write your own accessible custom widgets, for example.
 </para>
 <table frame="all">
 <title>Commonly used ATK API calls</title>
@@ -801,7 +801,7 @@
 </listitem>
 <listitem>
 <para>
-Minimize users' memory load. For example, let the user view multiple documents at the same time, and ensure online help or other instructions can remain visible while they carry out the procedure being described.  Allow them to copy any information that is displayed, and paste it anywhere that data can be entered.
+Minimize users' memory load. For example, let the user view multiple documents at the same time, and ensure online help or other instructions can remain visible while they carry out the procedure being described. Allow them to copy any information that is displayed, and paste it anywhere that data can be entered.
 </para>
 </listitem>
 <listitem>
@@ -851,7 +851,7 @@
 </listitem>
 <listitem>
 <para>
-Don't override existing system-level accessibility features. For example, <ulink url="http://www.rehab.uiuc.edu/accessx/overview.html";>AccessX</ulink> is an Xserver extension that has been supported since X11R6. The "MouseKeys" feature of this extension allows mouse movement and button clicks to be simulated using the keypad. Therefore you should not add features to your application that can only be accessed by pressing keys on the keypad, as users relying on the MouseKeys feature will not be able to use them.
+Don't override existing system-level accessibility features. For example, <ulink url="http://www.rehab.uiuc.edu/accessx/overview.html";>AccessX</ulink> is an Xserver extension that has been supported since X11R6. The MouseKeys feature of this extension allows mouse movement and button clicks to be simulated using the keypad. Therefore you should not add features to your application that can only be accessed by pressing keys on the keypad, as users relying on the MouseKeys feature will not be able to use them.
 </para>
 </listitem>
 <listitem>



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