<oXygen/> meets the "Section 508" technical standards of 1194.21, as and to
the extent stated in the accompanying Voluntary Product Accessibility
Template ("VPAT"). We therefore certify compliance with the following
solicitation requirement, or similar solicitation requirements:
"All electronic and information technology (EIT) procured
through this Statement of Work/Bill of Materials and any resulting contract,
task order, delivery order, or purchase order must meet the applicable
accessibility standards at 36 CFR 1194, unless an agency exception to this
requirement exists. 36 CFR 1194 implements Section 508 of the Rehabilitation
Act of 1973, as amended, and is viewable here. The contractor shall indicate
for each line item in the schedule whether each product or service is
compliant or non compliant with the accessibility standards at 36 CFR 1194.
Further, the proposal must indicate where full details of compliance can be
found (e.g., vendor's website or other exact location)."
The
first column contains the paragraphs of the subsections. The second column
describes the supporting features of <oXygen/> with regard to that
paragraph. The third column contains any additional remarks and
explanations.
| Criteria | Supporting Features | Remarks and Explanations |
| (a) When software is designed to run on a system that has a
keyboard, product functions shall be executable from a keyboard
where the function itself or the result of performing a function can
be discerned textually. | Keyboard navigation is
provided for most of the menu commands in <oXygen/> Some of the
functions, such as editing support over the schema diagram, or
source navigation using the outliner are not accessible through the
keyboard. | <oXygen/> partially complies with
this requirement. |
| (b) Applications shall not disrupt or disable activated
features of other products that are identified as accessibility
features, where those features are developed and documented
according to industry standards. Applications also shall not disrupt
or disable activated features of any operating system that are
identified as accessibility features where the application
programming interface for those accessibility features has been
documented by the manufacturer of the operating system and is
available to the product developer. | Note that
application settings in <oXygen/> regarding the font and colors of
the editing area may override the system
settings. | <oXygen/> mostly complies with this
requirement. |
| (c) A well-defined on-screen indication of the current focus
shall be provided that moves among interactive interface elements as
the input focus changes. The focus shall be programmatically exposed
so that Assistive Technology can track focus and focus
changes. | <oXygen/> provides on-screen
indication of current focus that moves among interactive interface
elements as the input focus changes.<oXygen/> does not
programmatically expose the focus, but supports the accessibility
settings of the host operating system. | <oXygen/>
fully complies with this requirement. |
| (d) Sufficient information about a user interface element
including the identity, operation and state of the element shall be
available to Assistive Technology. When an image represents a
program element, the information conveyed by the image must also be
available in text. | <oXygen/> does not provide
programmatic access for assistive technology for user interface
elements. All toolbar buttons provide a textual description through
tooltips. | <oXygen/> partially complies with
this requirement. |
| (e) When bitmap images are used to identify controls, status
indicators, or other programmatic elements, the meaning assigned to
those images shall be consistent throughout an application's
performance. | <oXygen/> user interface
consistently uses bitmap images to identify controls, status
indicators, and other programmatic
elements. | <oXygen/> fully complies with this
requirement. |
| (f) Textual information shall be provided through operating
system functions for displaying text. The minimum information that
shall be made available is text content, text input caret location,
and text attributes. | <oXygen/> provides textual
information through text content, text caret location, and text
attributes with some exceptions. The editing areas are not offering
textual description of the content due to the large size of a
typical XML document. | <oXygen/> partially
complies with this requirement. |
| (g) Applications shall not override user selected contrast
and color selections and other individual display
attributes. | <oXygen/> does not override user
selected contrast & color settings when they are available in
the operating system. | <oXygen/> fully complies
with this requirement. |
| (h) When animation is displayed, the information shall be
displayable in at least one non-animated presentation mode at the
option of the user. | <oXygen/> does not display
any animations. | This requirement is not
applicable to <oXygen/>. |
| (i) Color coding shall not be used as the only means of
conveying information, indicating an action, prompting a response,
or distinguishing a visual element. | <oXygen/>
interface does not use in general color coding as the only means of
conveying information, indicating an action, or distinguishing a
visual element. Exceptions: validate and wellformed buttons
distinguished through color. | <oXygen/> partially
complies with this requirement. |
| (j) When a product permits a user to adjust color and
contrast settings, a variety of color selections capable of
producing a range of contrast levels shall be
provided. |
<oXygen/> allows users to customize the contrast & color
settings of the text and background of a the edited text to a wide
range of colors supported by their system.
| <oXygen/> fully complies with this
requirement. |
| (k) Software shall not use flashing or blinking text,
objects, or other elements having a flash or blink frequency greater
than 2 Hz and lower than 55 Hz. | <oXygen/> does
not use flashing or blinking text, objects, or other elements in the
software's user interface. | This requirement is
not applicable to <oXygen/>. |
| (l) When electronic forms are used, the form shall allow
people using Assistive Technology to access the information, field
elements, and functionality required for completion and submission
of the form, including all directions and
cues. | <oXygen/> does not use electronic forms
for operation. | This requirement is not applicable
to <oXygen/>. |
Mac OS X
Linux/Unix
