blob: b06755c1e725d2d6c739059d6e6e317e0df9d7b2 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
#use wml::debian::template title="Debian-Accessibility"
#use wml::debian::translation-check translation="82f3d1721149ec88f5974028ed2c2d8d454b4071" maintainer="galaxico"
{#style#:<link rel="stylesheet" href="style.css" type="text/css" />:#style#}
<h2>Project description</h2>
<p>Debian-Accessibility is an internal project to develop Debian into an
operating system that is particularly well fit for the requirements of
people with disabilities.
The goal of Debian-Accessibility is a completely accessible system
which offers users with disabilities the highest possible amount
of independence, built completely on free software.
</p>
<p>We envisage that Debian-Accessibility will add value to existing
packages by providing patches to fix problems very specific
to certain user groups or conducting Accessibility validation tests and
providing modification suggestions based on the results.
</p>
<h2><a id="email-list" name="email-list">Email List</a></h2>
<p>The Debian-Accessibility mailing list is the central point of communication
for Debian-Accessibility. It serves as a forum for potential, as
well as current, users of the Debian system who do have special needs.
Additionally, it is used to coordinate development efforts around the various
topics of Accessibility. You can subscribe to and unsubscribe from it using
<a href="https://lists.debian.org/debian-accessibility/">the list web
page</a>, and also read the
<a href="https://lists.debian.org/debian-accessibility/">list archives</a>.
</p>
<h2><a id="projects" name="projects">Relevant Software</a></h2>
<p>The first attempt to put the software into categories might be not the
best. Send any suggestions for improvements to <a href="#email-list">the
mailing list</a>, or to <a href="mailto:sthibault@debian.org">Samuel Thibault</a>.
</p>
<ul>
<li><a href="software#speech-synthesis">Speech synthesis and related
APIs</a></li>
<li><a href="software#console">Console (text-mode) screen
readers</a></li>
<li><a href="software#emacs">Screen review extensions for
Emacs</a></li>
<li><a href="software#gui">Graphical User Interfaces</a>:
<ul>
<li><a href="software#gnome">GNOME Accessibility</a></li>
<li><a href="software#input">Non-standard input
methods</a></li>
</ul></li>
</ul>
<h2><a id="goals" name="goals">Project goals</a></h2>
<ul>
<li>Provide information and documentation of Accessibility.</li>
<li>Ensure that Accessibility software like drivers for specialized
peripheral devices can be loaded if necessary as early as possible in the
system startup phase, including the Debian installation process. This is
to ensure that people with special needs retain a high level of
independence during maintenance of their own systems.</li>
<li>Verify and ensure that Debian core infrastructure like our Web site does
comply with Accessibility Guidelines.</li>
<li>Bring authors of different projects with similar goals together.</li>
<li>Help upstream authors to get their products packaged for Debian.</li>
<li>Show commercial assistive technology vendors the strengths of Free
Software based systems and make them consider to port their software to
Linux or even to switch to Open Source.</li>
</ul>
<h2><a id="help" name="help">What can I do to help?</a></h2>
<ul>
<li>Work on enhancing and translating these web pages.</li>
<li>Create a logo.</li>
<li>Documentation and translation.</li>
<li>Internationalization (which is more than just translating, see
<a href="software#i18nspeech">internationalized speech
synthesis</a> for some ideas).</li>
<li>Verify that the debian.org web site is Accessible according to
established Accessibility Guidelines and submit enhancement suggestions
based on your findings. It could eventually be desirable to apply for
something like Bobby Approval at some point.</li>
</ul>
<h2><a id="links" name="links">Links</a></h2>
<ul>
<li>The <a href="https://wiki.debian.org/accessibility">Debian Accessibility Wiki</a>.</li>
<li>The <a href="https://wiki.debian.org/accessibility-maint">Debian Accessibility Wiki for all Debian maintainers</a>.</li>
<li>The <a href="https://wiki.debian.org/accessibility-devel">Debian Accessibility Developer Wiki</a>.</li>
<li>The <a href="https://wiki.linuxfoundation.org/accessibility/start">Free Standards Group Accessibility
Workgroup</a>.</li>
<li>The <a href="https://wiki.gnome.org/Accessibility">GNOME
Accessibility Project</a>.</li>
<li>The <a href="https://community.kde.org/Accessibility">KDE Accessibility
Project</a>.</li>
<li><a href="https://wiki.ubuntu.com/Accessibility">Ubuntu Accessibility</a></li>
<li><a href="http://leb.net/blinux/">BLINUX</a>: Improve usability of the
GNU/Linux operating system for the user who is blind.</li>
<li><a href="http://www.linux-speakup.org/">The Linux Speakup
Project</a>.</li>
<li><a href="http://www.w3.org/WAI/">W3C's Web Accessibility Initiative
(WAI)</a>:
<ul>
<li>The <a href="http://www.w3.org/TR/WCAG10/">Web Content
Accessibility Guidelines</a> explain in detail how to make a Web
site accessible for people with a variety of disabilities.</li>
<li>The <a href="http://www.w3.org/TR/ATAG10/">Authoring Tool
Accessibility Guidelines</a> explain how to make a variety of
authoring tools support the production of accessible Web
content, and also how to make the software itself accessible.</li>
</ul></li>
</ul>
|
