VirtualBox

source: vbox/trunk/doc/manual/en_US/Accessibility.xml@ 68716

Last change on this file since 68716 was 68450, checked in by vboxsync, 7 years ago

Docs: Accessibility Support: General concept.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 8.7 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
3"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
4<book>
5 <bookinfo>
6 <title>@VBOX_PRODUCT@<superscript>®</superscript></title>
7
8 <subtitle>Accessibility Reference</subtitle>
9
10 <edition>Version @VBOX_VERSION_STRING@</edition>
11
12 <corpauthor>@VBOX_VENDOR@</corpauthor>
13
14 <address>http://www.virtualbox.org</address>
15
16 <copyright>
17 <year>2016-@VBOX_C_YEAR@</year>
18
19 <holder>@VBOX_VENDOR@</holder>
20 </copyright>
21 </bookinfo>
22
23 <chapter>
24 <title>Introduction</title>
25 <para>
26 Welcome to the <emphasis role="strong">VirtualBox Accessibility Support</emphasis> documentation! This document is primarily
27 a reference to help people who are interested in our project accessibility support and will describe how to use VirtualBox
28 user interface step-by-step. Since whole the application navigation will be explained here, this document will also be
29 helpful for those who are not familiar with our product user interface and wish to learn more. It will be written in a bit
30 excessive manner so that many obvious things will be explained too precisely to make it easier to understand by ear for a
31 blind users. The document will be periodically updated with recent changes and test-cases allowing us to more strictly
32 follow the required guidelines and make our product fully accessible.
33 </para>
34 <para>
35 Our application is based on Qt5, a powerful cross-platform library which allows to visualize various user interface ideas
36 the most flexible and native way. This also means that the library we use is responsible for many navigation and
37 accessibility aspects (like fonts, size hints, colors, look&amp;feel patterns and many other things), but not for all of
38 them. Nativity as one of the main ideas of the Qt-based application sometimes brings additional complexity because there is
39 always at least one host which uses unique combination of fonts and colors which breaks accessibility support in an
40 unpredictable way.
41 </para>
42 <para>
43 Independently on platform we are supporting screen-reader applications which can communicate with Qt5 accessibility
44 interface which supports Microsoft Active Accessibility (MSAA), OS X Accessibility, and the Unix/X11 AT-SPI standard.
45 </para>
46 <para>
47 Our application user interface is able to be started in two modes:
48 <itemizedlist>
49 <listitem>
50 <para>
51 First of them is <emphasis role="strong">VirtualBox Manager</emphasis> user interface, the main application window
52 which allows to manage and configure virtual machines and their groups. Besides that, this window provides user with
53 access to various global and machine related tools allowing to administrate some of VirtualBox objects and their
54 settings.
55 </para>
56 </listitem>
57 <listitem>
58 <para>
59 Second application mode is <emphasis role="strong">Virtual Machine</emphasis> user interface, which allows to control
60 virtual machine guest screens as separate application windows. Besides that, this interface allows to access some of
61 machine tools and adjust guest screens up to your needs, by changing their resolution and toggling full-screen,
62 seamless and scaled modes.
63 </para>
64 </listitem>
65 </itemizedlist>
66 But first of all we should start from the <emphasis role="strong">General Concept</emphasis> which is related to whole the
67 GUI and summarizes the navigation and accessibility aspects we are using for whole application.
68 </para>
69 </chapter>
70
71 <chapter>
72 <title>General concept</title>
73 <para>
74 This chapter describes the general navigation and accessibility concept. We should note that not every detail of this
75 concept is already implemented and not every widget in our project already follows that concept. There is still large work
76 to be done in that regard. But in the end whole the project should correspond to this concept.
77 </para>
78 <para>
79 In short, every application window of our project should be navigated using the following approaches:
80 <itemizedlist>
81 <listitem><para>Mouse Navigation</para></listitem>
82 <listitem><para>Keyboard Navigation</para></listitem>
83 <listitem><para>Screen-reader Navigation</para></listitem>
84 </itemizedlist>
85 </para>
86 <sect1>
87 <title>Mouse Navigation</title>
88 <itemizedlist>
89 <listitem>
90 <para>
91 Each interactable widget can be focused with mouse (if that is not restricted by underlying host OS).
92 </para>
93 </listitem>
94 <listitem>
95 <para>
96 Each hovered interactable widget causes own tool-tip to appear.
97 </para>
98 </listitem>
99 <listitem>
100 <para>
101 Each tool-tip is given either in imperative mood (ex. "Create new virtual machine") or in short form (ex. "New").
102 </para>
103 </listitem>
104 <listitem>
105 <para>
106 Short tool-tip form is only used if context is obvious for a user.
107 </para>
108 </listitem>
109 <listitem>
110 <para>
111 Tool-tip can contain shortcut mentioned in parentheses.
112 </para>
113 </listitem>
114 <listitem>
115 <para>
116 Each hovered menu bar / toolbar action causes own status-tip to appear (if window have status-bar).
117 </para>
118 </listitem>
119 <listitem>
120 <para>
121 Each status-tip is given in imperative mood only.
122 </para>
123 </listitem>
124 <listitem>
125 <para>
126 TBD...
127 </para>
128 </listitem>
129 </itemizedlist>
130 </sect1>
131 <sect1>
132 <title>Keyboard Navigation</title>
133 <itemizedlist>
134 <listitem>
135 <para>
136 Each interactable widget can be focused with keyboard (if that is not restricted by underlying host OS).
137 </para>
138 </listitem>
139 <listitem>
140 <para>
141 Focusing is possible through tabbing or mnemonic navigation.
142 </para>
143 </listitem>
144 <listitem>
145 <para>
146 Each button and menu bar / toolbar action can be directly activated with keyboard.
147 </para>
148 </listitem>
149 <listitem>
150 <para>
151 Activation is possible via shortcut or mnemonic.
152 </para>
153 </listitem>
154 <listitem>
155 <para>
156 Each shortcut is configurable through application preferences.
157 </para>
158 </listitem>
159 <listitem>
160 <para>
161 Mnemonic mentioned above is underlined alphanumeric character which is a part of widget label (if widget has label).
162 Mnemonic being triggered in conjunction with the Alt key.
163 </para>
164 </listitem>
165 <listitem>
166 <para>
167 Each mnemonic is unique within the visible part of current application window, there are no collisions.
168 </para>
169 </listitem>
170 <listitem>
171 <para>
172 TBD...
173 </para>
174 </listitem>
175 </itemizedlist>
176 </sect1>
177 <sect1>
178 <title>Screen-reader Navigation</title>
179 <itemizedlist>
180 <listitem>
181 <para>
182 Each interactable widget can be focused with screen-reader cursor.
183 </para>
184 </listitem>
185 <listitem>
186 <para>
187 Each focused widget have clear name (or full description) in native user language.
188 </para>
189 </listitem>
190 <listitem>
191 <para>
192 Each button and menu bar / toolbar action can be directly activated through the screen-reader cursor functionality.
193 </para>
194 </listitem>
195 <listitem>
196 <para>
197 Each complex widget which has children (like list, tree, table and similar) is represented as closed group which
198 encapsulates it's children clearly.
199 </para>
200 </listitem>
201 <listitem>
202 <para>
203 While navigating user is able to skip any group without forcing to be entered inside.
204 </para>
205 </listitem>
206 <listitem>
207 <para>
208 Each group child can be a group itself with the same rules as above applicable.
209 </para>
210 </listitem>
211 <listitem>
212 <para>
213 Each text-field can be directly edited through the screen-reader cursor functionality.
214 </para>
215 </listitem>
216 <listitem>
217 <para>
218 TBD...
219 </para>
220 </listitem>
221 </itemizedlist>
222 </sect1>
223 </chapter>
224</book>
225<!-- vim: set shiftwidth=2 tabstop=2 expandtab: -->
Note: See TracBrowser for help on using the repository browser.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette