Because ODF is an open standard, projects are under development throughout the
accessibility community to create automated checking and analysis tools. As time goes
on, these building and checking tools will increase in number and sophistication. We
anticipate that ODF accessibility tools will eventually exceed the number of accessibility
tools available for proprietary document formats.
Background and Accessibility Design of Symphony
Symphony is based on OpenOffice.org and uses Eclipse
as its front end to provide an
integrated set of productivity applications. Symphony has made many usability,
interoperability and accessibility enhancements on the OpenOffice.org code base to
satisfy the productivity tool requirements of persons with disabilities (PwD).
Ease of use was a primary objective and was necessary to achieve the accessibility
compliance requirements. Symphony provides full keyboard access, visual focus and
high contrast for all functions, including dialog controls and editing areas. The user
interfaces of some key features were redesigned to increase usability.
In addition to usability enhancements, there are many improvements in document
interoperability with other document formats, such as Microsoft
format and Portable Document Format (PDF). All information required for
accessibility is maintained when opening and saving documents, thus avoiding any
accessibility loss during document conversion.
Accessible information is critical for people with disabilities (PwDs). Assistive
technologies such as screen readers must rely on standard APIs to acquire the accessible
information from applications. The Microsoft Active Accessibility
(MSAA) API is the
most popular API on the Windows platform. It was released in 1995 and supports dialog
controls and menus. Yet, MSAA does not support rich text, tables, lists and other widgets
that are commonly used in modern productivity software and Web applications. Because
of these limitations, ATs must resort to API hacks and application-specific behaviors to
get the desired information. Even worse, some applications have added specific private
interfaces for AT access. Such a model is a huge burden for both applications and ATs to
By merging and extending the virtues of different accessibility APIs, a new accessibility
API IAccessible2 (IA2) was created. IA2 is an open standard, developed by IBM and
donated to the Linux
Foundation. It builds on the existing MSAA architecture by
utilizing its Active Accessibility COM interface and the event generating mechanism and
extends them to support many other document elements, such as table, text, hyperlink,
and more. This allows applications to continue using their current implementation of
MSAA and make only those enhancements needed to support IA2.
Lotus Symphony is the first office application suite to implement IA2. Developers
worked closely with AT companies to ensure a complete solution and achieve the
accessibility requirements of PwDs for both document creation and review. MSAA and
IA2 together parallel the scope of the Linux-based Assistive Technology Service
Provider Interface (AT-SPI). By implementing IA2 along with MSAA, Symphony is able
to identify relationships between labels for controls, headers for table rows and columns,
VB.NET PDF - Convert PDF with VB.NET WPF PDF Viewer
Description. 1. To Word. Convert PDF to Word DOCX document. 2. To TIFF. Export PDF to TIFF file format. 3. To TXT. Export and convert PDF to TXT file. 4. To Image convert pdf to text online; convert .pdf to text
How to C#: File Format Support
PDF. Write pdf. DPX. Read 48-bit DPX. PGM. TIFF(TrueType Font File). Read all truetype convert to image. TXT(A text format). Convert ANSI-Encoding text format to convert pdf to word to edit text online; convert pdf to txt
tree nodes, tree node expansion status, as well as nesting levels for trees and lists.
Symphony's Extensible Design
Lotus Symphony is built on an Eclipse base and has a flexible plug-in design. Many
Symphony-related third party and community built plug-ins are becoming available.
Accessibility enabling tools which build and check ODF content can be integrated
directly into the Lotus Framework. For example, IBM has demonstrated an early
prototype of a Symphony-integrated tool to check and repair ODF files.
Symphony's framework also allows it to be embedded within other Eclipse frameworks.
For example, Lotus Notes 8.5 can host Symphony so that ODF documents can be viewed
in an integrated fashion in Notes tabs.
Symphony supports the ability to import and export several file formats. Symphony
imports and exports Microsoft Office formats up to Office 2003. It also exports PDFs,
retaining accessible content created through Lotus Symphony.
Symphony operates cross-platform on Microsoft Windows
, Linux, and Apple OS X.
Symphony's accessibility features are tested on Windows.
Symphony provides several usability enhancements to achieve accessibility as an
application. These build upon the foundation of IAccessible2, already discussed. These
are the Navigator, dockable sidebar properties, and user controls
Symphony provides an easy way to organize and select graphical objects on the screen
without a mouse. The Navigator view is shown by selecting menu View>Navigator or
pressing Ctrl + Shift + F5. It shows an organizational summary of all the objects in the
text document, presentation, or spreadsheet.
The user has a quick overview and access to all the objects by type. For example, the
user can see a list of all the images, tables, or hyperlinks in the file. The navigator shows
the text of headings in a text document as the text of hyperlinks. Most objects in the
Navigator allow access to their properties dialog through a context menu. Selecting an
object in the Navigator will adjust the editor display so the object can be seen.
The Navigator is a powerful tool for those unable to use a mouse because it allows
selection of one or multiple objects for keyboard menu interaction. To select elements
without a mouse, use the keyboard to move the highlighter bar to the desired node or
object, and then press the Spacebar to select it. Repeat the process to select multiple
items. If the node is already selected, highlighting and pressing the Spacebar deselects it.
Selected nodes are indicated in the Navigator with an “*” next to the name.
Figure 1 shows an example of using the Navigator in a presentation editor session. Each
object on the current slide is shown in the tree structure of the Navigator. The currently
selected object on the slide is highlighted with green handles and simultaneously is shown
in the Navigator with an "*" next to the name.
Figure 1– Symphony presentation editor with the thumbnail,
preview and Navigator panes displayed. A bitmap is selected in
the Navigator and the corresponding image is highlighted in the
The objects shown in the Navigator vary for each type of Symphony file. They are
shown in Table 1.
Objects shown in Navigator
headings, tables, frames, graphics, notes,
objects, sections, indexes, and hyperlinks
pages, title frames, text frames, images,
objects, and tables
cells, sheets, range names, linked areas,
Table 1 - Objects shown in the Navigator by content type
In addition to the standard Properties dialog reached through the context menu, properties
may be shown dynamically for each currently selected element in a sidebar next to the
editing area. The properties in the sidebar represent the most commonly used and
accessed property elements. When typing text for example, the font, effects (e.g.
C# PDF - Extract Text from Scanned PDF Using OCR SDK
NET convert PDF to text, C#.NET convert PDF to images C:\input.pdf"); BasePage page = pdf.GetPage(0 ocrPage.Recognize(); ocrPage.SaveTo(MIMEType.TXT, @"C:\output convert scanned pdf to text online; convert pdf to rich text
Strikethrough) and position (including rotation) of text at the current cursor position is
shown. As other objects are selected, the basic properties are shown. The number of
keystrokes required to change these properties remain approximately the same, but for
those with limited mobility, the ability to see these settings without continuously using
the context menu saves significant time and interaction effort. Figure 2 shows a text
document editing session with the sidebar listing the current properties of the selected
text. The properties are active and updates are shown dynamically in both the properties
and the displayed text document.
Figure 2 – Sample text document editing session showing
text properties in the sidebar.
Settings are provided through the preferences dialog for several common user
accessibility needs. A setting is provided to allow a text selection cursor in read-only text
documents. Another setting turns off all animate graphics and text. The user can also
control the time that help tips remain visible on the screen.
Creating Accessible Symphony Documents, Presentations and
The next sections provide techniques to help authors create accessible content using
Symphony. Except where noted, the techniques apply to all Symphony content: text
documents, presentations and spreadsheets.
It is important to identify the primary language of the content (document, presentation or
spreadsheet). The language setting is used by the AT to correctly read the content. In
Symphony, use the Preferences dialog (File > Preferences) to define the primary
language of the document.
Figure 3 – Preferences dialog
Text formats and color usage
Screen readers may have difficulty reading text formatting or detecting text color. As a
result, the screen reader will read the formatted text as if it contained no formatting. For
users who are color-blind or visually impaired, the use of the colored, underlined, and
bold formatting fails to convey the intended information. For all users to understand and
gain the full benefit of a document, text formatting and color may be used as an
enhancement, but not as the only way to convey information.
To create documents, presentations and spreadsheets with accessible text formatting and
use of color, follow these techniques:
1. Use text formatting and colors for enhancement, but not as the only means to
convey information. If you choose to use text formatting or colors to convey
information for the sighted, provide the information in a redundant form so that
color blind, low vision, or screen reader users can differentiate it.
For example, if required user settings are listed in red and optional settings are
displayed in green, preface the setting with an asterisk or other cue so someone
who is colorblind or someone who is using a screen reader will also be able to
identify the required commands.
* Use accessibility keyboard navigation
Do not prompt when exiting application
Table 2 : Sample Preferences Table illustrating color and indication of color
2. Ensure that there is sufficient contrast between the page text and background.
Some color combinations can make reading difficult even for sighted users who
are not color blind. To solve this problem, create a high contrast in your
document. Black text on a white background works well, but light gray text on a
white background does not. In addition, avoid patterned page backgrounds
because it makes differentiation between the text and background difficult for
3. Do not add patterned backgrounds to data tables or presentation textboxes.
Although patterned backgrounds do not create a problem for screen reader users,
they can be a problem for individuals who have low vision because of the
difficulty in distinguishing text from a patterned background.
If your document contains colored text or objects, there is an easy way to verify that the
information being conveyed is not color-dependent: print or view the document in black
and white -- the information in black and white should be no less meaningful than a color
Data tables, row and column headers:
Users must be able to understand the purpose of a table, and understand the purpose of
the data contained within the table. When a user of assistive technology navigates
through the cells of a data table, the user must be able to determine the column or row
header in order to understand the meaning of the data contained in it. Ensuring data tables
are accessible requires techniques unique to each Symphony format (e.g., text documents,
presentations, and spreadsheets).
Do not use tabs or spacing to create tables. While it may visually look like a table, it will
not be recognized as a table by assistive technology and will not be accessible.
For text documents, Symphony enables the user to set both the row and column headers.
To create accessible data tables:
1. Using the Table > Create Table dialog for a new table, select the Column Header
and Row Label checkboxes to specify column and row headers of a data table as
shown in Figure 4a.
2. For an existing table, set the row and column headers on the Rows and Columns tab
of Table Properties dialog, via the Table > Table Properties > Row and Columns
tab as shown in Figure 4b. Check the Column header and Row label checkboxes
and provide the number of rows and columns that make the table headers. Because
screen readers cannot read table headers that span more than one row or column,
verify the number of rows and columns are not greater than one.
Figure 4a – Create Table dialog showing the column header and row label checkbox
Figure 4b – Table Properties dialog showing the Column header and Row label
settings on the Rows and Columns tab
3. Provide informative header text that conveys the meaning of the data contained in
the rows and columns. Brevity is appreciated because the text will be repeated
4. Add a caption above or below the table to summarize the purpose of the table.
Select the table by placing the cursor in a cell of the table then select Create >
Caption to add the caption. Alternatively, add a caption by right-clicking anywhere
on the table and selecting Add Caption.
For presentations, setting column headers and row labels is not yet an available option.
To create accessible data tables:
1. Create simple tables using Create > Table which are accessible without any
2. Add a caption above or below the table to summarize the purpose of the table.
3. Do not use patterned backgrounds within tables.
For spreadsheets, screen readers may not be able to interpret large data sets or ranges that
are not labeled properly. If row and column headers are not labeled properly, users might
not know what type of data is expected. To help ensure that data tables in the spreadsheet
are accessible, use row and column headers extensively and avoid ambiguity within these
headers. Make them clear, concise and self-explanatory.
Documents you may be interested
Documents you may be interested