--- a/doc/maintain.texi	Wed May 14 22:06:24 2014 +0100
+++ b/doc/maintain.texi	Thu May 15 05:37:17 2014 -0700
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
-@set lastupdate March 19, 2014
+@set lastupdate May 13, 2014
 @c %**end of header
 
 @dircategory GNU organization
@@ -2062,6 +2062,9 @@
 set them up on whatever site is convenient for you, and make the pages
 on @code{www.gnu.org} link to that site.
 
+Please follow the best practices of accessibility in your web pages
+(see @url{http://www.gnu.org/accessibility/accessibility.html}).
+
 @menu
 * Hosting for Web Pages::
 * Freedom for Web Pages::
@@ -2069,7 +2072,6 @@
 * CVS Keywords in Web Pages::
 @end menu
 
-
 @node Hosting for Web Pages
 @section Hosting for Web Pages
 @cindex web pages, hosting for
@@ -2290,7 +2292,6 @@
 itself.  Also, @code{makeinfo} notices the @code{@@w} and generates
 output avoiding the literal keyword string.
 
-
 @node Ethical and Philosophical Consideration
 @chapter Ethical and Philosophical Consideration
 @cindex ethics

--- a/doc/standards.texi	Wed May 14 22:06:24 2014 +0100
+++ b/doc/standards.texi	Thu May 15 05:37:17 2014 -0700
@@ -3,7 +3,7 @@
 @setfilename standards.info
 @settitle GNU Coding Standards
 @c This date is automagically updated when you save this file:
-@set lastupdate March 31, 2014
+@set lastupdate May 13, 2014
 @c %**end of header
 
 @dircategory GNU organization
@@ -295,7 +295,7 @@
 make heavy use of templates.  So is Java, if you compile it.
 
 When highest efficiency is not required, other languages commonly used
-in the free software community, such as Scheme, Python, Ruby, and
+in the free software community, such as Lisp, Scheme, Python, Ruby, and
 Java, are OK too.  Scheme, as implemented by GNU@tie{}Guile, plays a
 particular role in the GNU System: it is the preferred language to
 extend programs written in C/C++, and also a fine language for a wide
@@ -828,22 +828,25 @@
 to invoke it.  It is useful sometimes to make a link to a utility
 with a different name, and that should not change what it does.
 
-Instead, use a run time option or a compilation switch or both
-to select among the alternate behaviors.
+Instead, use a run time option or a compilation switch or both to
+select among the alternate behaviors.  You can also build two versions
+of the program, with different names and different default behaviors.
 
 @cindex output device and program's behavior
-Likewise, please don't make the behavior of the program depend on the
-type of output device it is used with.  Device independence is an
-important principle of the system's design; do not compromise it merely
-to save someone from typing an option now and then.  (Variation in error
-message syntax when using a terminal is ok, because that is a side issue
-that people do not depend on.)
+Likewise, please don't make the behavior of a command-line program
+depend on the type of output device it gets as standard output or
+standard input.  Device independence is an important principle of the
+system's design; do not compromise it merely to save someone from
+typing an option now and then.  (Variation in error message syntax
+when using a terminal is ok, because that is a side issue that people
+do not depend on.)
 
 If you think one behavior is most useful when the output is to a
 terminal, and another is most useful when the output is a file or a
-pipe, then it is usually best to make the default behavior the one that
-is useful with output to a terminal, and have an option for the other
-behavior.
+pipe, then it is usually best to make the default behavior the one
+that is useful with output to a terminal, and have an option for the
+other behavior.  You can also build two different versions of the
+program with different names.
 
 There is an exception for programs whose output in certain cases is
 binary data.  Sending such output to a terminal is useless and can
@@ -890,6 +893,11 @@
 mode).  Once you are doing the work to provide the functionality and
 the graphical interface, these won't be much extra work.
 
+Please make your program interoperate with access technology such as
+screen readers (see
+@url{http://www.gnu.org/accessibility/accessibility.html}).  This should
+be automatic if you use GTK+.
+
 @node Command-Line Interfaces
 @section Standards for Command Line Interfaces
 @cindex command-line interface