[Top][All Lists]

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

www/server/staging/nav-bar/test9 accessibility....

From: Therese Godefroy
Subject: www/server/staging/nav-bar/test9 accessibility....
Date: Tue, 18 Mar 2014 09:18:42 +0000

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Therese Godefroy <th_g> 14/03/18 09:18:42

Added files:
        server/staging/nav-bar/test9: accessibility.html 

Log message:
        New test file (for .note).


Index: accessibility.html
RCS file: accessibility.html
diff -N accessibility.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ accessibility.html  18 Mar 2014 09:18:42 -0000      1.1
@@ -0,0 +1,216 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<!-- start of server/head-include-1.html -->
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:address@hidden"; />
+<link rel="icon" type="image/png" href="/graphics/gnu-head-mini.png" />
+<meta name="ICBM" content="42.355469,-71.058627" />
+<meta name="DC.title" content="gnu.org" />
+<!-- end of server/head-include-1.html --><!-- end of server/header.html 
--><!-- Parent-Version: 1.75 -->
+<title>GNU Accessibility Statement
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/accessibility/po/accessibility.translist" -->
+<!-- start of server/banner.html -->
+<!-- start of head-include-2.html -->
+<link rel="stylesheet" href="combo.css" media="screen" />
+<link rel="stylesheet" href="layout5.css" media="screen" />
+<link rel="stylesheet" href="/mini.css" media="handheld" />
+<link rel="stylesheet" href="/print.css" media="print" />
+<!-- end of head-include-2.html --></head>
+<div  class="inner">
+<!--#include virtual="body-include-1.html" -->
+<!--#include virtual="body-include-2.html" -->
+<div id="content">
+<!-- end of server/banner.html -->
+<h2>GNU Accessibility Statement</h2>
+<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>
+<blockquote class="note">
+  <p><strong>Rejoignez la conversation</strong></p>
+  <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></li>
+  </ul>
+<p>According to the United Nations in 2005, there were 600 million
+people with disabilities in the world.  To use computers, many of them
+need special software known as &ldquo;access technology&rdquo;.  Like
+other programs, these can be free software or proprietary.  Those
+which are free software respect the freedom of their users; the rest,
+proprietary programs, subject those users to the power of the
+program's owner.</p>
+<p>In order for access technology to work, the other software in use
+must interoperate with it.  The majority of computer programs and web
+sites (85% in one estimate) do not comply with accessibility standards
+and guidelines, so they do not work with access technology.  They
+provide a frustrating experience, and can bar users from job or school
+<p>Proprietary file formats that require proprietary reading programs
+are poison to both accessibility and to the freedoms that we as free
+software activists hope to establish.  The biggest offender is Flash
+format; it usually requires proprietary software that doesn't
+cooperate with accessibility.  Microsoft Silverlight is similar.
+<acronym title="Portable Document Format">PDF</acronym> is also
+difficult; though there is free software to view it, it does not
+support free access technology software.  GNU PDF aims to do
+<p>People with disabilities deserve to have control of their own
+technological destinies.  When they use proprietary access technology,
+they have little or no way to correct whatever is wrong with it.
+Virtually all major decisions of the proprietary developers are made
+by people who do not have the disability; 20 years' experience shows
+that people with unusual combinations of disabilities, who require
+relatively unusual software, or who encounter a bug that keeps them
+from doing their job have no way to obtain the changes they need.
+These products are only changed or improved when the vendors see a
+business reason for doing the work; this leaves many users behind.  As
+a secondary problem, proprietary access software is far more expensive
+than a PC.  Many users cannot afford to give up their freedom in this
+<p>For users with disabilities, as for all other users, free software
+is the only way the users can control their own computing, their only
+chance to make software fit their needs rather than passively
+accepting whatever developers choose to offer them.</p>
+<p>Nations with large populations also have large numbers of people
+with disabilities.  Countries including Brazil and Russia are
+discussing whether to standardize government purchases on GNU/Linux
+platforms.  These nations are all signatories to the UN Convention on
+the Rights of Persons with Disabilities, and include technology in
+their agenda for providing such rights.  This will require them to
+hire programmers to work on accessibility software for their
+populations.  If it is free software, the rest of the world will be
+able to use it too.  The hackers who work on free access technology
+will provide tools that people with disabilities can use to expand
+their horizons enormously.</p>
+<p>Ensuring that your application or web site is accessible is the
+right thing to do.  And it fits naturally with free software.</p>
+<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 <a 
 accessibility API</a>
+(GNU/Linux platforms only), the <a 
 accessibility API</a> (GNU/Linux and
+Windows) and <a 
 (GNU/Linux and Windows).</p>
+  <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>
+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
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="footer-text.html" -->
+<div id="footer">
+<div class="unprintable">
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2010, 2013 Free Software Foundation, Inc.</p>
+<p>This page is licensed under a <a rel="license"
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+<p>The Recommendations section may also be used under the Creative
+Commons Attribution license, and may be relicensed to the GNU Free
+Documentation License version 1.3 or later.</p>
+<!--#include virtual="/server/bottom-notes.html" -->
+<p></p><p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2014/03/18 09:18:42 $
+<!-- timestamp end -->

reply via email to

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