Changeset 68448 in vbox for trunk/doc/manual/en_US
- Timestamp:
- Aug 17, 2017 4:33:34 PM (7 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/Accessibility.xml
r68360 r68448 23 23 <chapter> 24 24 <title>Introduction</title> 25 26 <para>Add text here.</para> 27 28 <sect1> 29 <title>Sample section</title> 30 31 <para>Add more text.</para> 32 </sect1> 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 precicely 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&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> 33 69 </chapter> 34 70 </book>
Note:
See TracChangeset
for help on using the changeset viewer.