II_2 Attachment IV_1_OpenText_Intelligent_Capture_VPAT_2023.pdf

Voluntary Product Accessibility Report

Compliance and Remediation Statement for Section 508 of the US

Rehabilitation Act for OpenText Intelligent Capture 2023

Jan 2023

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 2

Contents Compliance and Remediation Statement for Section 508 of the US Rehabilitation Act for OpenText Intelligent

Capture 2023

Compliance and Remediation Statement for Section 508 of the US Rehabilitation Act for OpenText Intelligent

Capture 2023

Summary of Test Results – Intelligent Capture

Voluntary Product Accessibility – Intelligent Capture

Section 1194.21 – Software Applications and Operating Systems

Section 1194.22 – Web-based Intranet and Internet Information and Applications

Section 1194.31 – Functional Performance Criteria

Section 1194.41 – Information, Documentation, and Support

Summary of Test Results - Intelligent Capture Advanced Recognition

Voluntary Product Accessibility - Intelligent Capture Advanced Recognition

Section 1194.21 – Software Applications and Operating Systems

Section 1194.31 – Functional Performance Criteria

Section 1194.41 – Information, Documentation, and Support

Summary of Test Results - Intelligent Capture for Invoices

Voluntary Product Accessibility - Intelligent Capture for Invoices

Section 1194.21 – Software Applications and Operating Systems

Section 1194.22 – Web-based Intranet and Internet Information and Applications

Section 1194.31 – Functional Performance Criteria

Section 1194.41 – Information, Documentation, and Support

Additional Remarks

Disclaimer

About OpenText

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 3

Compliance and Remediation Statement for Section 508 of the US

Rehabilitation Act for OpenText Intelligent Capture 2023 This statement describes the compliance of OpenText Intelligent Capture 2023, a software product from

OpenText, with the United States Rehabilitation Act Section 508—Electronic and Information Technology

Accessibility Standards. The description of OpenText Intelligent Capture 2023 compliance with Section 508 is presented in the Voluntary Product Accessibility Template (VPAT) format.

Date Jan 2023

Name of Product OpenText Intelligent Capture

Version 23.1

Contact for more information http://www.opentext.com/section508 info@opentext.com

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 4

Summary of Test Results – Intelligent Capture

The following table summarizes the compliance of OpenText Intelligent Capture with the relevant sections of

Subparts B through D of Section 508 of the U.S. Rehabilitation Act. Compliance details are listed in the detail sections on the following pages.

Criteria Applicable Compliance

Section 1194.21 Software

Applications and Operating

Systems

Applicable Supported with exceptions

Section 1194.22 Web-based internet information and applications

Applicable Supported with exceptions

Section 1194.23

Telecommunications Products

Not applicable

Section 1194.24 Video and

Multimedia Products

Not applicable

Section 1194.25 Self-Contained, Closed Products

Not applicable

Section 1194.26 Desktop and

Portable Computers

Not applicable

Section 1194.31 Functional

Performance Criteria

Applicable Supported with exceptions

Section 1194.41 (a) Information, Documentation, and Support

Applicable Supported

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 5

Voluntary Product Accessibility – Intelligent Capture

Section 1194.21 – Software Applications and Operating Systems

Criteria Supporting Features Remarks and Explanations

1194.21 (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.

Supported with exceptions Keyboard support in Intelligent Capture is partly limited and does not include all controls in each window. As a result, major functionality remains inaccessible from the keyboard and requires a mouse to use. For example, replacement items in the objects tree structure in Intelligent

Capture DCTM Advanced Export module or selection an item on Select

Path dialogue cannot be done via the keyboard.

Additionally, Intelligent Capture

Identification and Intelligent Capture

Completion, Intelligent Capture

ScanPlus and Intelligent Capture

NuanceOCR have drag and drop features to create field views. They are entirely mouse-driven features that cannot be made fully accessible from the keyboard without fundamental alteration of the software.

Specific problems related to keyboard accessibility include controls that are not included in the tab order. For example, nearly all sortable column headers across the apps and several expand/collapse controls do not receive keyboard focus.

Other problems are related to controls that are in the tab order and that receive keyboard focus, but that

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 6

do not support activation or use from keyboard commands.

Furthermore, meaningful rollover information in several apps is not keyboard accessible. For example, Error icons in Intelligent Capture Designer contain important rollover error information that is not keyboard accessible.

1194.21 (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.

Supported with exceptions Some apps such as Intelligent

Capture ScanPlus do support Custom

Windows Color Selections; however, most apps in Intelligent Capture fail to respond to High Contrast mode and their text is unreadable.

1194.21 (c) A well-defined onscreen 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.

Supported with exceptions Most controls in Intelligent Capture demonstrates use of standard focus indicator provided by Windows;

however, there are other issues that prevent the application from being entirely accessible, for example, focus is not always indicated visually or not redirected to the appropriate control.

Also, these include inactive or hidden interface elements that receive keyboard focus. This can be very confusing for

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 7

keyboard-only users when they are unable to locate elements receiving focus on the screen.

1194.21 (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.

Not supported Most controls in Intelligent Capture apps such Intelligent Capture Designer, Intelligent Capture

ScanPlus, Intelligent Capture

Identification, and Intelligent

Capture Completion do not have accessible names, descriptions, and values or they are incorrectly defined. In many cases, the apps contain a number of custom controls whose types are not correctly identified by assistive technologies.

Due to the visual layout of the windows, screen readers may incorrectly identify or be unable to identify some form control labels.

Comboboxes in several apps do not have accessible names and screen readers do not read their values correctly.

Tables in nearly all apps including

Intelligent Capture Designer, Intelligent Capture Identification, Intelligent Capture Completion, and

Intelligent Capture Standard Export are not formatted to indicate column header information. Furthermore, screen readers fail to read the information contained in each row and instead render a common accessible name for all data cells. For example, in Intelligent

Capture

Identification, Intelligent Capture

Completion, and Intelligent Capture

Standard Export, screen reader users cannot identify the batch

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 8

name from the table containing batches in order to process a batch.

In CaptureFlow Designer screen readers fail to read the information relevant to steps in CaptureFlow placed on the canvas.

Additionally, Field selection in

Intelligent Capture Identification and

Intelligent Capture Completion requires users to see a scanned image and place a visual field around the portion of the image.

Finally, Intelligent Capture

Identification and Intelligent Capture

Completion involves visual processing of scanned documents to validate the information in the form fields.

1194.21 (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.

Supported All bitmap images present in Intelligent

Capture are used in a standard fashion.

1194.21 (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.

Supported with exceptions Intelligent Capture includes apps that contain informational text that is not rendered by screen readers. For example, the inner text of the Automatic

Logout, Login or About module dialogues used across the apps are not read by screen readers. Similarly, the text parts of Intelligent Capture

Designer’s System Overview screen, some informational text on Intelligent

Capture ScanPlus and Intelligent

Capture DCTM Advanced Export module's screens are also not rendered by screen readers.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 9

1194.21 (g) Applications shall not override user selected contrast and color selections and other individual display attributes.

Supported with exceptions

Some apps such as Intelligent

Capture ScanPlus, Intelligent

Capture Identification and Intelligent

Capture Completion modules do support

Custom Windows Color Selections;

however, most apps in

Intelligent Capture fail to respond to

High Contrast mode and their text is unreadable.

1194.21 (h) When animation is displayed, the information shall be displayable in at least one nonanimated presentation mode at the option of the user.

Not Applicable The apps part of Intelligent Capture does not use animation in any way.

1194.21 (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.

Supported with exceptions

Intelligent Capture Designer uses color to identify errors, field names, and data strings in expression editors.

Intelligent Capture Identification and

Intelligent Capture Completion identifies fields that require validation with orange highlighting. This use of color is the sole method of indicating that a field needs validation. Similarly, in the page view panel, the part of the image that is being validated is highlighted in yellow.

1194.21 (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.

Not Applicable Intelligent Capture does not permit users to adjust color and contrast settings.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 10

1194.21 (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.

Supported Intelligent Capture does not use any blinking or flashing elements.

1194.21 (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.

Not supported Nearly all apps have form label problems. Many form fields are either incorrectly identified or are not identified at all by screen readers. Most controls do not have accessible names.

In Intelligent Capture Designer, several controls and buttons have identical names on the same page.

Intelligent Capture Designer utilizes tables with form fields whose specific meaning are visually implied by the column and row headers, but that are not conveyed in the fields’ accessible names. A typical example is Intelligent

Capture Designer’s System

Configuration tab.

Nearly all apps do not indicate error messages in an accessible manner. In

Intelligent Capture Designer or

Intelligent Capture DCTM Export module, the error messages are indicated as rollover information to an error icon that is not keyboard accessible. The errors are also indicated in the problems panel at the bottom of the screen;

however, errors relevant to a field do not receive focus. Furthermore, the accessibility labels for elements containing error messages in the problems panel are not defined properly.

As a result, errors in the problems panel are not rendered

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 11

correctly by screen readers to tis users.

The errors in Intelligent Capture

Identification, and Intelligent

Capture Completion are indicated using an error icon; however, the error information is not accessible to screen reader users. The errors are displayed dynamically in the message area. Each time the form field with errors receives focus, the error in the message area gets updated. Furthermore, the accessibility labels for form fields do not indicate errors textually. These problems make it extremely difficult for screen reader users to identify if or why errors have occurred.

Most apps use time-based sessions that can cause user to logout of the app due to inactivity. The content of the

Automatic Logout dialog is not read by screen readers. As a result, screen reader users may not be able to extend their session in the available time and may be logged out of the app.

The forms in Intelligent Capture

Identification and Intelligent Capture

Completion involve visual processing which require users to see a scanned image and complete or validate the information in the form fields. These processes fundamentally require vision to complete and cannot be represented in text.

Section 1194.22 – Web-based Intranet and Internet Information and Applications

Criteria Supporting Features Remarks and Explanations

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 12

1194.22 (a) A text equivalent for every non-text element shall be provided

(e.g., via alt, longdesc, or in element content).

Not supported Intelligent Capture Web Client involves visual processing of scanned documents that require users to be able to see a scanned image and complete or validate the information in the form fields. This function fundamentally requires vision to complete and cannot be represented in text.

Furthermore, nearly all image buttons and controls in Intelligent Capture Web

Client are CSS background images that do not provide textual and visual equivalents. The spacer images layered on top of these controls fail to provide alternative text.

Several expand/collapse controls in

Intelligent Capture Web Client such as the Document Type dropdown menu do not indicate any state description when they are expanded or collapsed.

Several split buttons such as the

Choose Scanner do not have a text equivalent for dropdown button.

Error icons which display numbers of issues do not have alt text and description.

On the form, required fields are marked by *, that has not text and description.

On Organize page, each page has an icon buttons for Edit, View or

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 13

Delete. They do not have any alt text, description and cannot be accessed by screen reader.

On Organize page, More Pages button does not have an alt text.

On the Installer screen with products choosing Enter doesn’t work.

1194.22 (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Not Applicable The web components of Intelligent

Capture do not use multimedia presentations.

1194.22 (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

Supported with exceptions

The suggested data on the image is indicated solely using yellow color.

The validated data on the image and in the table is indicated solely using green or red color.

1194.22 (d) Documents shall be organized so they are readable without requiring an associated style sheet.

Not supported

Intelligent Capture Web Client are not accessible with stylesheets turned off.

Nearly all image-based buttons and controls in Intelligent Capture Web

Client are CSS background images that do not provide visual and textual equivalents.

Additionally, the headings on

Intelligent Capture Web Client and the form are not defined using structural

HTML heading elements.

1194.22 (e) Redundant text links shall be provided for each active region of a server-side image map.

Not Applicable

The web components of Intelligent

Capture do not utilize server-side image maps.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 14

1194.22 (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Not Applicable The web components of Intelligent

Capture do not utilize client-side image maps.

1194.22 (g) Row and column headers shall be identified for data tables.

Not supported

In Intelligent Capture Web Client, the data tables are not structured using standard HTML table elements.

Extended table layout does not correct and does not allow screen reader to recognize the structure.

1194.22 (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

Not Applicable

The web components of Intelligent

Capture Web Client do not have data tables that have two or more logical levels of row or column headers.

1194.22 (i) Frames shall be titled with text that facilitates frame identification and navigation.

Not Applicable No functional frames are used.

1194.22 (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Supported with exceptions

Intelligent Capture Web Client does not utilize elements that blink or flicker. But with screen reader ON issues can occurred, that application windows are blocked and starts blinking.

1194.22 (k) A text-only page, with equivalent information or functionality, shall be provided to make a Web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page

Supported Intelligent Capture does not require a text-only page.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 15

shall be updated whenever the primary page changes.

1194.22 (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.

Not supported

In the Intelligent Capture Web Client, several expand/collapse controls such as Crop Menu control, do not indicate any state description as expanded or collapsed. They also fail to define the beginning and ending of their content.

The validation errors messages in

Intelligent Capture Web Client are displayed dynamically using scripting.

Each time the form field with errors receive focus, the error message at the top of the form gets updated dynamically. Screen reader users are not alerted to the presence of the updated error messages in an accessible manner.

1194.22 (m) When a Web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with

Section1194.21(a) through (l).

Not Applicable Intelligent Capture Web Client does not require any plug-ins.

1194.22 (n) When electronic forms are designed to be completed online, 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.

Not supported The forms in Intelligent Capture Web

Client involve visual processing that requires users to be able to see a scanned image and complete or validate the information in the form fields.

These processes fundamentally require vision to complete and cannot be represented in text; therefore, Paragraph (n) qualifies

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 16

for a Fundamental Alteration

Exception

Additionally, Login form controls have explicit labels that do not read by assistive technologies.

Furthermore, validation error messages in Intelligent Capture Web Client are displayed dynamically using scripting.

Each time the form field with errors receive focus, the error message at the top of the form gets updated dynamically.

The updated error messages are not alerted to screen reader users in an accessible manner.

1194.22 (o) A method shall be provided that permits users to skip repetitive navigation links

Supported

Intelligent Capture Web Client does not require a skip mechanism.

Also, user can navigate to the main content area using direct links.

1194.22 (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Supported

In Intelligent Capture Web Client due to inactivity, users are automatically logged out of the application without any explicit session timeout alerts.

Section 1194.31 – Functional Performance Criteria

1194.31 (a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive

Technology used by

Not supported Fundamentally, Intelligent Capture includes a suite of applications that process scanned documents for optical character recognition and processing. Within Intelligent Capture, there are administrative components that can be

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 17

people who are blind or visually impaired shall be provided.

performed independently of the scanned documents, among which there are accessibility issues as summarized below.

Major functionality in apps such as

Intelligent Capture Designer is inaccessible from the keyboard and requires a mouse to use, rendering it inaccessible to screen reader users.

Within the Windows software components of Intelligent Capture, there is no keyboard access to many controls. Also, the labels of some form controls and the types of other controls are not correctly identified. Table data in nearly all apps is not properly associated with table headers. Also, color is used as the sole method of indicating state information and form fields in error.

Furthermore, errors are indicated as rollover text which is not keyboard accessible. In apps such as Intelligent Capture

Identification and Intelligent Capture

Completion, screen reader users are not alerted to any content changed dynamically such as error messages.

Intelligent Capture Web Client process scanned documents which is required to visualize the document and validate field data using the image. There is no keyboard access to some controls, message text and navigation layout are not correctly identified.

Table data is not properly associated with table headers. In a few places, color is used as the sole method of indicating state information and form fields in error.

Furthermore, errors are indicated as rollover text which is not keyboard accessible.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 18

Screen reader users are not alerted to any content changed dynamically such as error messages.

Several image buttons do not have any visual and textual equivalents, form fields have missing explicit labels, and fields in error are indicated by using an error icon without any visual or textual equivalents. No structural heading elements are utilized where they are needed. Data tables do not identify headers and column headers are not in the same table as the data cells.

1194.31 (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.

Supported with exceptions Intelligent Capture does not fully support the use of assistive technologies by people with visual impairments.

Several image buttons in Intelligent Capture

Web Client do not provide visual and textual equivalents.

Several components use color alone to indicate state information, such as on required fields or on fields that are in error.

Both the software and web components use color alone to indicate state information, such as on required fields or on fields that are in error.

Furthermore, some apps use color alone to indicate errors, whereas in some cases such as Intelligent Capture Web Client, color is used solely to indicate selections. Users who are colorblind may not be able to discern the intended meaning.

The buttons used in Intelligent Capture Web

Client do not provide sufficient color contrast between the background and the foreground colors.

Finally, Intelligent Capture’s Windows software applications do not fully support

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 19

custom Windows color selections, and text is unreadable in High Contrast mode.

1194.31 (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive

Technology used by people who are deaf or hard of hearing shall be provided.

Supported Intelligent Capture does not produce sound.

1194.31 (d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

Supported Intelligent Capture does not produce sound.

1194.31 (e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive

Technology used by people with disabilities shall be provided.

Supported Intelligent Capture does not require users to produce speech for use.

1194.31 (f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

Not supported The majority of Intelligent Capture’s apps do not provide full keyboard support. There are some critical components that are inaccessible from the keyboard and that require either the use of a mouse or an assistive technology product that can emulate a mouse.

Within the Windows applications, field selection in Intelligent Capture Identification, the Intelligent Capture

Completion, and the Capture Flows in

Intelligent Capture Designer all involve

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 20

functions that are entirely mouse-driven and inaccessible from the keyboard.

Most form controls in the Windows software applications do not provide explicit labels.

Therefore, they are incorrectly described or not described at all by assistive technologies.

In the web applications, this problem only affects some controls.

Furthermore, the page resizing controls in apps such as Intelligent Capture Designer are not accessible from the keyboard.

Within the web components of Intelligent

Capture, there are a variety of simulated controls that are not accessible from the keyboard. These include add/remove listboxes, context menus, sortable column headers, and clickable table rows. Other issues include the illogical tab order for several interactive elements in Intelligent

Capture Administrator.

Lastly, nearly all image buttons in Intelligent

Capture Web Client do not provide alternative text.

Section 1194.41 – Information, Documentation, and Support

1194.41 (a) Product Support

Documentation provided to endusers shall be made available in alternate formats upon request, at no additional charge

Supported OpenText provides alternative documentation formats to users upon request, free of charge.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 21

1194.41 (b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.

Supported

OpenText provides an overview of the accessibility features present in the product, optimal assistive technology configurations for use, means of requesting alternate formats, and known accessibility issues with the product upon request, free of charge.

1194.41 (c) Support Services for products shall accommodate the communication needs of endusers with disabilities

Supported

OpenText support services provide support for users with hearing impairments via relay services and other means.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 22

Summary of Test Results - Intelligent Capture Advanced Recognition

The following table summarizes the compliance of OpenText Intelligent Capture Advanced Recognition with the relevant sections of Subparts B through D of Section 508 of the U.S.

Rehabilitation Act. Compliance details are listed in the detail sections on the following pages.

Criteria Applicable Compliance

Section 1194.21 Software

Applications and Operating

Systems

Applicable Supported with exceptions

Section 1194.22 Web-based internet information and applications

Not applicable

Section 1194.23

Telecommunications Products

Not applicable

Section 1194.24 Video and

Multimedia Products

Not applicable

Section 1194.25 Self-Contained, Closed Products

Not applicable

Section 1194.26 Desktop and

Portable Computers

Not applicable

Section 1194.31 Functional

Performance Criteria

Applicable Supported with exceptions

Section 1194.41 (a) Information, Documentation, and Support

Applicable Supported

Voluntary Product Accessibility - Intelligent Capture Advanced Recognition

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 23

1194.21 (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.

Not supported

Within Recognition Designer, there are several drag and drop functions that are entirely mouse driven and cannot be accomplished using keyboard. This includes placement of fields and anchors in Index View, using the

Rubberbanding function in Free Form Designer and Template Test, and dragging fields on the positioning panels to define an alignment relation in Free Form Designer. None of these functions can be made fully keyboard accessible without fundamental alteration of the software.

In addition, there are several other keyboard accessibility problems. Various controls do not appear in the tab order of the page. For example, the left navigation controls in Free

Form Designer do not receive focus. Similarly, none of the expand collapse controls and sortable column headers in Recognition

Designer are in the tab order. The page tabs in

Project Options, the Add and Delete Images controls in Project Update Wizard, and many other controls do not receive keyboard focus in

Recognition Designer.

Several read-only form fields do not receive keyboard focus. This makes their content illegible to screen reader users and renders it unavailable for copying and pasting.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 24

The Windows On-Screen Keyboard (WOSK) users are unable to access the menus. For example, WOSK users cannot open the File menu using the Alt+F Key or F10 key.

Other specific problems include focus being forcibly shifted on user input. For example, when uses navigate within the tree control in the Project panel using the arrow key, focus shifts to the Template panel. Similarly, in the

Template Test Window, when users navigate between the images in the column list view control for images, the template test is automatically launched and focus gets shifted to the Index Fields panel for validation.

In Recognition Designer (Classification view), the controls for zoom in, zoom out, and

Template Properties are not duplicated in the menu.

Users are unable to navigate between panes using CTRL+TAB or F6 keys in Recognition

Designer.

Finally, Windows and columns in list view controls cannot be resized from keyboard.

1194.21 (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

Supported with exceptions Some parts of Recognition Designer, Dispatcher Classification, and Dispatch

Collector do support Custom Windows Color

Selections; however, several windows and screens fail to respond properly to Windows

High Contrast mode and the text is unreadable.

Also, the Windows On-Screen Keyboard

(WOSK) users are unable to access the menus in Recognition Designer. For example, WOSK users cannot open the

File menu using the Alt+F Key or F10 key.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 25

documented by the manufacturer of the operating system and is available to the product developer.

1194.21 (c) A well-defined onscreen 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.

Supported with exceptions

Nearly all column list view controls in

Recognition Designer do not receive programmatic focus. As a result, when users tab to an application pane containing Column List

View controls, JAWS announces, "List view 0 items" and is unable to detect the number of list items. There are several windows in

Recognition Designer where hidden and inactive elements receive keyboard focus, confusing users.

The “Keywords Nearby” checkbox in Edit

Keyword Classification – Edit Rules

Window does not indicate focus visually.

1194.21 (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.

Not supported

Nearly all text form fields and comboboxes do not have an accessible name and cannot be identified by screen readers.

Nearly all column list view controls in

Recognition Designer do not provide textual name, roles, and state descriptions. As a result, users who are blind are unable to identify the list item controls and determine their states

(i.e., selected or not).

There are several image controls that are not labelled and that fail to provide name, role and, state descriptions. For example, image controls in left Panel for Free Form Designer and

Keyword Classification do not provide any accessible name, role or state descriptions.

Additionally, these controls are not keyboard accessible.

When JAWS users navigate using JAWS cursor, they are unable to identify the control and its state (selected or not).

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 26

Many controls have improper roles assigned to them. For example, all edit spin box controls have a role of edit, which is not valid. As a result, screen reader users are unable to identify an edit field as a spin box edit field.

Similarly, in Dispatcher Collector and

Dispatcher Classification, the left navigation page tab controls are assigned a role of radio buttons, which is very misleading for screen reader users.

Also, the reading order in some windows of

Recognition Designer is not logical and does not coincide with the tab order of active elements. As a result, assistive technology users lose the meaning of the content and have difficultly completing a form.

Additionally, some of the Window titles in

Recognition Designer, Dispatcher

Classification and Dispatch Collector fail to describe the purpose of the window or dialog.

For example, Recognition Designer Window title do not describe which view is active, i.e., Classification View or Index View.

Finally, Intelligent Capture Advanced

Recognition require visual processing of scanned documents for placing fields and anchors or extracting data from the images.

These processes fundamentally require vision to complete and cannot be represented in text;

therefore, Paragraph (d) qualifies for a

Fundamental Alteration Exception.

1194.21 (e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned

Supported All bitmap images that are part of

Intelligent Capture Advanced Recognition are used in a standard fashion.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 27

to those images shall be consistent throughout an application’s performance.

1194.21 (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.

Supported with exceptions Most of the Window titles in Recognition

Designer, Dispatcher Classification, and

Dispatch Collector are descriptive; however, in some cases, the titles fail to describe the purpose of the window or dialog.

1194.21 (g) Applications shall not override user selected contrast and color selections and other individual display attributes.

Supported with exceptions

Some parts of Recognition Designer, Dispatcher Classification and Dispatch

Collector do support Custom Windows Color

Selections; however, several windows and screens fail to respond properly to High

Contrast mode and their text is unreadable.

1194.21 (h) When animation is displayed, the information shall be displayable in at least one nonanimated presentation mode at the option of the user.

Not Applicable Intelligent Capture Advanced Recognition does not use animation in any way.

1194.21 (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.

Supported with exceptions

The New Recognition Project dialog indicate errors solely using red color.

In Recognition Designer, under Template

Test, the form fields that require validation are solely indicated using red color and the errors are also indicated solely using red color.

In the Project Update Wizard left panel, green color is used to indicate current step in wizard, white color is used to indicated steps to come, gray color is used to indicate visited steps, and red color is for last step in the Wizard.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 28

1194.21 (j) When a product permits a user to adjust color and contrast settings, a variety of color selections

Not Applicable Intelligent Capture Advanced Recognition does not permit users to adjust color and contrast settings.

1194.21 (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.

Supported Intelligent Capture Advanced Recognition does not use any blinking or flashing elements.

1194.21 (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.

Not supported Nearly all text form fields and comboboxes in

Recognition Designer have missing accessible names and cannot be identified by screen readers, making it impossible for vision impaired users to complete the forms.

In Free Form Designer, the Instructions for defining alignment relations are not placed at the top of the form. Instead, it is at the bottom of the form. Similarly, in Index Family Editor, the instructive information related to a field gets updated at the bottom of the Fields

Properties panel each time a field is selected.

This instructive text does not receive focus and is not rendered to users who are blind.

Some buttons and controls do not have descriptive labels. For example, in Dispatcher

Classification Setup, the Add, Remove, Add

All, and Remove All buttons are punctuation symbols that are not read properly by JAWS and that do not make sense when not seen visually. Similarly, under Project Options –

Production Auto Learning tab, the Browse for

Folder button is given the Name' value of "...", which is

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 29

not descriptive for a screen reader user. It is announced as "dot dot dot."

Other specific problems include focus gets forcibly shifted on user input. For example, when users navigate within the tree control in the Project panel using the arrow key, focus shifts to the Template panel. Similarly, in the

Template Test Window, when users navigate between the images in the column list view control for images, the template test is automatically launched and focus gets shifted to the Index Fields panel for validation.

In New Recognition Project dialog and

Template Test Window, the errors are not indicated textually. The errors are indicated solely using red color.

Also, in Template Test Window, each time a form field in error receives focus, the errors in the message area gets updated. This information is not conveyed to screen reader users and they remain completely unaware of the existence of error on the page.

Lastly, the validation forms part of Template

Test in Recognition Designer involves visual processing which require users to see a scanned image and complete or validate the information in the form fields. This fundamentally require vision to complete and cannot be represented in text.

1194.31 (a) At least one mode of operation and information retrieval Not supported Fundamentally, Intelligent Capture

Advanced Recognition is used as part of

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 30

that does not require user vision shall be provided, or support for Assistive

Technology used by people who are blind or visually impaired shall be provided.

a suite of applications that process scanned documents for optical character recognition and processing. Within Advanced

Recognition, there are administrative components that may be performed independently of the scanned documents.

However, there are several functions that require visual processing of scanned documents, such as placement of fields and anchors on the template image, rubberbanding and extracting required data from the image, defining alignment relations, field unit tests, and template test. All these functions are critical to advanced document recognition and cannot be performed by users who are blind.

Additionally, as discussed in §1194.21 (a), lack of keyboard support presents a fundamental barrier to successful use of

Intelligent Capture Advanced Recognition by users who are blind or visually impaired.

As discussed in §1194.21 (d) and (l), nearly all text form fields and comboboxes do not have accessible names, buttons and controls fail to have descriptive labels, instructive text is at the bottom of the form, and some controls are either incorrectly identified or are not identified at all by screen readers.

As mentioned in §1194.21 (c), nearly all column list view controls in Recognition

Designer do not expose programmatic focus.

Also, there are several Windows in

Recognition Designer where hidden and inactive elements receive keyboard focus causing confusion.

Another problem that is more functional in nature is that JAWS is unable to read text

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 31

that is isolated and not associated with any form fields or controls. For example, in

Project Update Wizard, the left column showing widget progress is not read by JAWS.

In addition, in many of the application windows and panes for Intelligent Capture

Advanced Recognition, the focus order of actionable elements is illogical.

1194.31 (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.

Supported with exceptions

As discussed in §1194.21 (b) and (g), Intelligent Capture Advanced Recognition does not fully support Windows default high contrast color schemes used by people who are visually impaired.

Also, as discussed in §1194.21 (i), color is used as a sole method to indicate information.

For example, errors in New Recognition

Project dialog and Template Test Window are indicated using red color. Additionally, in the

Project Update Wizard left panel, green color is used to indicate current step in wizard, white color is used to indicated steps to come, gray color is used to indicate visited steps, and red color is for last step in the Wizard.

As discussed in §1194.21 (a), lack of keyboard support presents a significant barrier to successful use of Intelligent

Capture Advanced Recognition by many users who are visually impaired. Specific problems include focus being forcibly shifted on user input. For example, when uses navigate within the tree control in the Project panel using the arrow key, focus shifts to the Template panel.

Also, users are unable to navigate between panes using CTRL+TAB or F6 keys in

Recognition Designer.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 32

As mentioned in §1194.21 (c), nearly all column list view controls in Recognition

Designer do not expose programmatic focus.

Also, there are several Windows in

Recognition Designer where hidden and inactive elements receive keyboard focus causing confusion.

As discussed in §1194.21 (l), important instructions are sometimes placed at the bottom of forms, where they may be overlooked by users of screen magnification software. For example, in Free Form

Designer, the Instructions for defining alignment relations are at the bottom of the form. Similarly, in Index Family Editor, the instructive information related to a field gets updated at the bottom of the Fields Properties panel each time a field is selected.

In addition, in many of the application windows and panes for Intelligent Capture

Advanced Recognition, the focus order of actionable elements is illogical.

1194.31 (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive

Technology used by people who are deaf or hard of hearing shall be provided.

Supported Intelligent Capture Advanced Recognition does not produce sound.

1194.31 (d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

Supported Intelligent Capture Advanced Recognition does not produce sound.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 33

1194.31 (e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive

Technology used by people with disabilities shall be provided.

Supported Intelligent Capture Advanced Recognition does not require users to produce speech for use.

1194.31 (f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

Not supported

As discussed in §1194.21 (a) Intelligent

Capture Advanced Recognition has heavy dependency on the use of the mouse and lacks full keyboard support. This makes its use prohibitively difficult for users who are not able to use a mouse.

As discussed in §1194.21 (b) Windows On-

Screen Keyboard (WOSK) users are unable to access the menus in Recognition Designer. For example, WOSK users cannot open the File menu using the Alt+F Key or F10 key.

Also, as discussed in §1194.21 (d) and (l), nearly all text form fields and comboboxes do not have accessible names, and some controls are either incorrectly identified or are not identified at all by screen readers.

In Recognition Designer, there are several

Windows where hidden and inactive elements receive keyboard focus, causing confusion.

In many of the application windows and panes for Intelligent Capture Advanced Recognition, the focus order of actionable elements is illogical.

OPENTEXT PRODUCT VPAT ACCESSIBILITY REPORT 34

1194.41 (a) Product Support

Documentation provided to endusers shall be made available in alternate formats upon request, at no additional charge

Supported OpenText provides alternative documentation formats to users upon request, free of charge.

1194.41 (b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.

Supported

OpenText provides an overview of the accessibility features present in the product, optimal assistive technology configurations for use, means of requesting alternate formats, and known accessibility issues with the product upon request, free of charge.

1194.41 (c) Support Services for products shall accommodate the communication needs of endusers with disabilities

Supported

OpenText support services provide support for users with hearing impairments via relay services and other means.

Summary of Test Results - Intelligent Capture for Invoices

The following table summarizes the compliance of OpenText Intelligent Capture for Invoices with the relevant sections of Subparts B through D of Section 508 of the U.S. Rehabilitation Act. Compliance details are listed in the detail sections on the following pages.

Criteria Applicable Compliance

Section 1194.21 Software

Applications and…