gnome-devel-docs r566 - trunk/gadg

[vpalexander svn gnome org]

Author: vpalexander
Date: Mon Aug 25 17:09:19 2008
New Revision: 566
URL: http://svn.gnome.org/viewvc/gnome-devel-docs?rev=566&view=rev

Log:
unstubbing

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

Modified: trunk/gadg/gad.xml
==============================================================================
--- trunk/gadg/gad.xml	(original)
+++ trunk/gadg/gad.xml	Mon Aug 25 17:09:19 2008
@@ -95,21 +95,19 @@
 
 <section id="dev-start">
 <title>Developer Quick Start</title>
-<para>
-Ensuring your application is accessible to those with disabilities can be a simple process during development (when planned for) or even afterwards - it may not require much development effort.
-</para>
+<para>Here are some common starting points:</para>
 
 <section id="dev-start-1">
 <title>How do I check to see if my application is accessible or not?</title>
 <para>
-stub
+To start right in, see <link linkend="gad-overview">Making a GNOME Application Accessible - Overview</link>. For a pre-codng perspective, see <link linkend="gad-ui-guidelines">User Interface Guidelines for Supporting Accessibility</link> or <link linkend="gad-coding-guidelines">Coding Guidelines for Supporting Accessibility</link>. For a checklist of post-design test items, see <link linkend="gad-checklist">User Interface Checklist</link>.
 </para>
 </section>
 
 <section id="dev-start-2">
 <title>What are the common pitfalls?</title>
 <para>
-stub
+The <link linkend="gad-checklist">User Interface Checklist</link> covers all the areas that sometimes get overlooked in the design stage.
 </para>
 </section>
 
@@ -147,7 +145,6 @@
 stub
 </para>
 </section>
-
 </section>
 
 <section id="gad-overview">

Modified: trunk/gadg/gtest.xml
==============================================================================
--- trunk/gadg/gtest.xml	(original)
+++ trunk/gadg/gtest.xml	Mon Aug 25 17:09:19 2008
@@ -1,7 +1,7 @@
 <chapter id="gtest" status="draft">
 <title>Testing</title>
 <para>
-Thre are several points of review to conduct before declaring an application accessible. Over the course of development you may want to consider automated testing techniques. There are many tools available to complement an automated testing plan.
+There are several points of review to conduct before declaring an application accessible. Over the course of development you may want to consider automated testing techniques. <ulink url="http://people.redhat.com/zcerza/dogtail";>Dogtail</ulink>, for example, may complement your automated testing plan.
 </para>
 <para>
 This section describes a number of tests you can perform manually on an application to test its accessibility. Passing all the tests does not necessarily imply that the application is fully accessible, but if the application fails any of these tests, then further work may need to be done to improve that aspect of its accessibility.
@@ -775,7 +775,7 @@
 <section>
 <title>Accerciser</title>
 <para>
-<application>Accerciser</application> is an interactive Python accessibility explorer for the GNOME Desktop. It uses AT-SPI to inspect and control widgets, allowing you to check if an application is providing correct     information to assistive technologies and automated test frameworks. <application>Accerciser</application> has a simple plugin framework which you can use     to create custom views of accessibility information.
+<application>Accerciser</application> is an interactive Python accessibility explorer for the GNOME Desktop. It uses AT-SPI to inspect and control widgets, allowing you to check if an application is providing correct     information to assistive technologies and automated test frameworks. <application>Accerciser</application> has a simple plugin framework which you can use     to create custom views of accessibility information. Full documentation can be found <ulink url="http://library.gnome.org/devel/accerciser/stable";>here</ulink>.
 </para>
 <note>
 <para>