Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle WebCenter Enterprise Capture updated3 12.2.1.3.0

Product Description:

This VPAT is for the Oracle WebCenter Enterprise Capture product. Oracle WebCenter Enterprise Capture streamlines the capture process for paper and electronic documents focused on process-oriented imaging applications and enterprise capture for content management.

Image based documents can be output in the following formats: Multiple page TIFF (Tagged Image File Format), PDF (Portable Document Format) and Searchable PDF, which cannot be edited by users. Non-image based documents (e.g., Word, Excel, Text, EML (Electronic Mail), etc...) remain in their native formats and cannot be edited within the product.

Date:

24-Jul-2017

Archive Note:

This VPAT applies to only version 12.2.1.3.0. It does not apply to any versions of Oracle WebCenter Enterprise Capture after this. This VPAT has been superseded by Oracle WebCenter Enterprise Capture 12.2.1.4.0.

Contact Information:

accessible_ww@oracle.com

Notes:

WebCenter Enterprise Capture Client

For high contrast and/or large font support, configure Windows within the Ease of Access Center, accordingly. Then, login to the Enterprise Capture Client, click the Preferences link from the drop-down in the upper right corner of the window, and select the "I use Windows accessibility features" option. If using Windows large fonts, you need to also enable the Font Size for Client and the Font Size for Metadata Fields in the Preferences dialog.

To support assistive technologies, the Java Access Bridge must be enabled. In the Windows Ease of Access Center, click "Use the computer without a display". Then, select the "Enable Java Access Bridge" setting.

WebCenter Enterprise Capture Workspace Console

To activate screen reader support, login to the Enterprise Capture Workspace Console and click the Preferences link from the drop-down in the upper right corner of the window. Then, select "I use a screen reader".

Oracle Enterprise Manager

To activate accessibility mode when using the Oracle WebCenter Enterprise Capture Enterprise Manager plug-in, login to Enterprise Manager and click the Accessibility option from the drop-down in the upper right corner of the window. Then, select the My Preferences sub-menu and then the Accessibility menu item. The following accessibility options are available:

I use a screen reader
I use high contrast settings
I use large fonts
Show me the Accessibility Preference options after I log in

Dependent Products

This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/Guideline	Included In Report
Web Content Accessibility Guidelines 2.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/	Level A - Yes Level AA - Yes Level AAA - No
Section 508 as published in 2017, at https://www.Section508.gov	Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports: The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Supports with Exceptions: Some functionality of the product does not meet the criteria.
Does Not Support: Majority of functionality of the product does not meet the criteria.
Not Applicable: The criteria are not relevant to the product.

WCAG 2.0 Report

Table 1 also documents conformance with:

Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports	The Workspace Console was tested for: Images that convey information have meaningful alternative text using ALT Images that are decorative are marked up using ALT=”” or CSS background images Titles for Objects and Applets are provided Controls have an associated name Time-based media is not used Image maps are not used Non-text characters have meaningful alternative text CAPTCHAs are not used The Client was tested for: Images that convey information are embedded within standard user interface components and have a meaningful AccessibleName and/or AccessibleDescription Images that are decorative are embedded within standard user interface components and have neither an AccessibleName nor an AccessibleDescription Data tables include a summary or caption, programmatically connected with the table as the AccessibleTable's AccessibleSummary Controls have an AccessibleName, or a label control with an AccessibleName has been programmatically associated with it Time-based media is not used Non-text characters have meaningful alternative text CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	No pre-recorded audio-only or video-only content is being used.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	No pre-recorded video content is being used.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	No pre-recorded video is being used.
1.2.4 Captions (Live) (Level AA)	Not Applicable	No live audio content in video is being used.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	No pre-recorded video is being used.
1.3.1 Info and Relationships (Level A)	Supports with Exceptions	The Workspace Console was tested for: User interface component labels are associated with the fields they are labeling Headings are encoded with HTML heading tags List markup is used for marking up lists Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate Data tables specify SUMMARY or CAPTION Layout tables use appropriate markup Groups of components are marked up with their description Style sheets are used only to change the layout and presentation on the screen The Client was tested for: User interface component labels are associated with the fields they are labeling via the LabelFor and LabeledBy relations Headings are marked as such with a Group relation from the header to the items beneath the header Groups of components are marked as such, with a Group relation from the header of the group to the members of the group Style sheets are used only to change the layout and presentation on the screen Lists are contained within a List component Tables are contained within a Table component, implement the AccessibleTable interface, provide an AccessibleSummary, and contain include row and column headers where appropriate Exceptions found: Bug 16501929: In the metadata field area, date field captions and the drop-down calendar fail to be read by a screen reader. In addition, inclusion of date metadata fields may cause other metadata fields to fail reading. Bug 16501947: On the batch search dialog in the Client, a screen reader fails to read the From and To date field captions as well as the drop-down calendar. Bug 18205088: In the Client, choice list fields are not read correctly when you navigate through the items. Bug 20634888: In the Commit Profile "Edit Execution Order" dialog, a screen reader may encounter an empty list item. Bug 23540755, 23540819: Information displayed in layout format in some tables in product documentation and help does not have any indication of relationship Bug 25302207: In the "Add/Edit Conversion job" dialog of Workspace Console, a screen reader may encounter an empty list item.
1.3.2 Meaningful Sequence(Level A)	Supports	The product was tested for: The accessibility hierarchy is logical The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)	Supports	The product was tested for: Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound Instructions provided which refer to graphics included a reference to the text alternative of the graphic
1.4.1 Use of Color(Level A)	Supports	The product was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)	Supports	The product was tested for: No automatically playing audio is used
1.4.3 Contrast (Minimum) (Level AA)	Supports	The product was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1
1.4.4 Resize text(Level AA)	Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality Text (and application) resizes up to 200% using the platform's built-in magnifier or zoom feature
1.4.5 Images of Text(Level AA)	Supports	The product was tested for: Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential
2.1.1 Keyboard(Level A)	Supports	The Workspace Console was tested for: Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes Proper operation of unique keystrokes and access keys, including those listed in the product documentation The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms) The Client is composed of components that have full keyboard operation implemented as documented in the Appendix A Keyboard Shortcuts, Mnemonics, and Other Keyboard Operations of the Java Look and Feel Design Guidelines. Where the product uses components developed after this document was published, those components use the WAI-ARIA Keyboard Bindings and Behaviors, or other keyboard operation as documented in the product documentation. The Client was tested for: ability to perform functions from the keyboard only logical movement of focus through the controls proper operation of unique keystrokes, including those listed in the product documentation
2.1.2 No Keyboard Trap (Level A)	Supports	The product was tested for: Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for: Time limits in the product can be extended with at least 20 seconds warning up to 10 times.
2.2.2 Pause, Stop, Hide (Level A)	Supports	There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The product was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
2.4.1 Bypass Blocks(Level A)	Supports	The product was tested for: A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page. Structure and hierarchy is marked up with Header elements outside of repetitive navigation links WAI-ARIA Landmark elements are used outside of repetitive navigation links
2.4.2 Page Titled(Level A)	Supports	The product was tested for: Web pages have a meaningful title specified in the TITLE element. Client application: The name of the software application is meaningful.
2.4.3 Focus Order(Level A)	Supports	The Workspace Console was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence The Client was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence, as per the Appendix A Keyboard Shortcuts, Mnemonics, and Other Keyboard Operations section of the Java Look and Feel Design Guidelines, or where appropriate the WAI-ARIA Keyboard Bindings and Behaviors, or other keyboard operation as documented in the product documentation.
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product was tested for: The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)	Supports	The product was tested for: Pages are fully inter-linked to each other Page contains controls that enable reaching all pages
2.4.6 Headings and Labels(Level AA)	Supports	The product was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field
2.4.7 Focus Visible(Level AA)	Supports	The product was tested for: Visual indication of the location of the focus
3.1.1 Language of Page(Level A)	Supports	The Workspace Console was tested for: Properly set lang attribute for each page The Client was tested for: Properly set locale/language
3.1.2 Language of Parts(Level AA)	Supports	The Workspace Console was tested for: Proper use of lang attribute for text passages that are in a different language than that of the page The Client was tested for: Properly set locale/language for text passages that are in a different language than that of the software
3.2.1 On Focus(Level A)	Supports	The Workspace Console was tested for: When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window The Client was tested for: When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window
3.2.2 On Input(Level A)	Supports	The Workspace Console was tested for: Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window The Client was test for: Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window
3.2.3 Consistent Navigation(Level AA)	Supports	The Workspace Console was tested for: Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time Regarding the Client: Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.
3.2.4 Consistent Identification(Level AA)	Supports	The product was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Supports	The product was tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
3.3.2 Labels or Instructions (Level A)	Supports	The product was tested for: Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)	Supports	The product was tested for: Where suggestions for fixing an input error are known, they are provided to the user
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The product was tested for: Data is checked for input errors with an opportunity for the user to correct them Data can be reviewed, corrected, and confirmed by the user before they are finalized
4.1.1 Parsing(Level A)	Supports	The Workspace Console was tested for: Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs Regarding the Client: Markup languages aren't used to generate the user interface
4.1.2 Name, Role, Value (Level A)	Supports with Exceptions	The Workspace Console was tested for: HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc. Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’. Custom controls have appropriate roles specified using the role attribute Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes Custom controls have a meaningful programmatically exposed name Frames have a meaningful title specified in the title attribute The Client was tested for: User interface components have a programmatically associated AccessibleName and AccessibleRole as defined by the Java Accessibility API State information, properties, and values are programmatically exposed for user interface components Event notification of changes to names, states, properties, and values is available to assistive technologies Exceptions found: Bug 16501929: In the metadata field area, date field captions and the drop-down calendar fail to be read by a screen reader. In addition, inclusion of date metadata fields may cause other metadata fields to fail reading. Bug 16501947: On the batch search dialog in the Client, a screen reader fails to read the From and To date field captions as well as the drop-down calendar. Bug 18205088: In the Client, choice list fields are not read correctly when you navigate through the items. Bug 20634888: In the Commit Profile "Edit Execution Order" dialog, a screen reader may encounter an empty list item. Bug 25302207: In the "Add/Edit Conversion job" dialog of Workspace Console, a screen reader may encounter an empty list item.

2017 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria	Conformance Level	Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Supports	Product was tested for: Software does not disrupt platform features that are defined in the platform documentation as accessibility features.
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Supported	Bug 26184220 - Product does not permit user preferences
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Not Applicable	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Not Supported	BUG 26175494 Product does not have Accessibility Features documentation
602.3 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support Documentation	Not Applicable	Product documentation is in electronic format.
603 Support Services	Heading cell - no response required	Heading cell - no response required
603.2 Information on Accessibility and Compatibility Features	Supports	Oracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication Needs	Supports	Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.