summaryrefslogtreecommitdiff
path: root/en/boot-installer/accessibility.xml
blob: 976f4903ae82dcd7e3e5363a89c7b17c99c3ecb6 (plain)
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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->

 <sect1 id="boot-installer-accessibility" arch="not-s390">
 <title>Accessibility</title>
<para>

Some users may need specific support because of e.g. some visual
impairment.
<phrase arch="ia64;powerpc;ppc64el;x86">USB braille displays are detected
automatically (not serial displays connected via a serial-to-USB converter),
but most other</phrase>
<phrase arch="arm;hppa;mips;mipsel;sparc">Most</phrase>
accessibility features have to be enabled manually.
<phrase arch="x86">On machines that support it, the boot menu emits a beep
when it is ready to receive keystrokes.</phrase>
Some boot parameters can <phrase arch="x86">then</phrase> be appended to
enable accessibility features<phrase arch="x86"> (see also
<xref linkend="boot-screen"/>)</phrase>.
Note that on most architectures the boot loader interprets your keyboard as
a QWERTY keyboard.

</para>

  <sect2>
  <title>Installer front-end</title>
<para>

The &debian; installer supports several front-ends for asking questions, with
varying convenience for accessibility: notably, <userinput>text</userinput>
uses plain text while <userinput>newt</userinput> uses text-based dialog
boxes.  The choice can be made at the boot prompt, see the documentation for
<userinput>DEBIAN_FRONTEND</userinput> in <xref linkend="installer-args"/>.

</para>
  </sect2>

  <sect2 arch="ia64;powerpc;ppc64el;x86">
  <title>USB Braille Displays</title>
<para>

USB braille displays should be automatically detected. A textual version
of the installer will then be automatically selected, and support for the
braille display will be automatically installed on the target system.
You can thus just press &enterkey; at the boot menu.
Once <classname>brltty</classname> is started, you can choose a braille
table by entering the preference menu. Documentation on key
bindings for braille devices is available on the <ulink
url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>.

</para>
  </sect2>

  <sect2 arch="ia64;powerpc;ppc64el;x86">
  <title>Serial Braille Displays</title>
<para>

Serial braille displays cannot safely be automatically detected
(since that may damage some of them). You thus need to append the
<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput>
boot parameter to tell <classname>brltty</classname> which driver it
should use. <replaceable>driver</replaceable> should be replaced by the
two-letter driver code for your terminal (see the
<ulink url="&url-brltty-manual;">BRLTTY manual</ulink>).
<replaceable>port</replaceable> should be replaced by the name of the
serial port the display is connected to, <userinput>ttyS0</userinput> is
the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the
braille table to be used (see the <ulink url="&url-brltty-manual;">BRLTTY
manual</ulink>); the English table is the default. Note that the table can
be changed later by entering the preference menu. Documentation on key
bindings for braille devices is available on the <ulink
url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>.

</para>
  </sect2>


  <sect2 arch="x86">
  <title>Software Speech Synthesis</title>
<para>

Support for software speech synthesis is available on all installer images which
have the graphical installer, i.e. all netinst, CD and DVD images, and the
netboot gtk variant. It can be activated by selecting it in the
boot menu by typing <userinput>s</userinput> &enterkey;. The textual version
of the installer will then be automatically selected, and support for software
speech synthesis will be automatically installed on the target system.

</para><para>

The first question (language) is spoken in english, and the remainder
of installation is spoken in the selected language (if available in
<classname>espeak</classname>).

</para><para>

The default speech rate is quite slow. To make it faster, press
<keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>.
To make it slower, press
<keycombo><keycap>CapsLock</keycap><keycap>5</keycap></keycombo>.

The default volume should be medium. To make it louder, press
<keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>.
To make it quieter, press
<keycombo><keycap>CapsLock</keycap><keycap>1</keycap></keycombo>.

To get more details on the browsing shortcuts, see the
<ulink url="&url-speakup-guide;">Speakup guide</ulink>.

</para>
  </sect2>

  <sect2 arch="x86">
  <title>Hardware Speech Synthesis</title>
<para>

Support for hardware speech synthesis devices is available on all installer
images which have the graphical installer, i.e. all netinst, CD and DVD images,
and the netboot gtk variant. You thus need to select a <quote>Graphical
install</quote> entry in the boot menu.

</para><para>

Hardware speech synthesis devices cannot be automatically detected. You
thus need to append the
<userinput>speakup.synth=<replaceable>driver</replaceable></userinput>
boot parameter to tell <classname>speakup</classname> which driver it should
use. <replaceable>driver</replaceable> should be replaced by the driver code
for your device (see <ulink url="&url-speakup-guide;">driver code
list</ulink>). The textual version of the installer will then be
automatically selected, and support for the speech synthesis device will be
automatically installed on the target system.

</para>
  </sect2>

  <sect2 arch="linux-any"><title>Board Devices</title>
<para>

Some accessibility devices are actual boards that are plugged inside the
machine and that read text directly from the video memory. To get them
to work framebuffer support must be disabled by using the
<userinput arch="x86">vga=normal</userinput> <userinput>fb=false</userinput>
boot parameter. This will however reduce the number of available languages.

</para><para arch="x86">

If desired a textual version of the bootloader can be activated before adding
the boot parameter by typing <userinput>h</userinput> &enterkey;.

</para>
  </sect2>

  <sect2><title>High-Contrast Theme</title>
<para>

For users with low vision, the installer can use a high-contrast
color theme that makes it more readable. To enable it, append the
<userinput>theme=dark</userinput> boot parameter.

</para>
  </sect2>

  <sect2><title>Preseeding</title>
<para>

Alternatively, &debian; can be installed completely automatically by using
preseeding. This is documented in <xref linkend="appendix-preseed"/>.

</para>
  </sect2>

  <sect2><title>Accessibility of the installed system</title>
<para>

Documentation on accessibility of the installed system is available on the
<ulink url="&url-debian-wiki-accessibility;">Debian Accessibility wiki page</ulink>.

</para>
  </sect2>

 </sect1>