Oracle Accessibility Conformance Report

1. Images that convey information have meaningful alternative text using ALT
2. Images that are decorative are marked up using ALT=”” or CSS background images
3. Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
4. Titles for Objects and Applets are provided
5. Controls have an associated name
6. Non-text characters are not used or have meaningful alternative text
7. CAPTCHAs are not used

The TT EM plugin product was tested for the following cases:

1. User interface component labels are associated with the fields they are labeling
2. Headings are encoded with HTML heading tags
3. Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
4. Data tables specify SUMMARY or CAPTION
5. Groups of components are marked up with their description
6. Style sheets are used only to change the layout and presentation on the screen

The TT EM documentation was tested for:

• 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

Both the TT EM plugin product  and documentation were tested for the following cases:

1. The sequence of elements in the DOM matches a logical reading sequence

The TT EM plugin product was tested for:

•  Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

The documentation 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

Both the TT EM plugin product  and documentation were tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.
• Mobile testing was done using the Chrome simulator.  See bug 32159333 on orientation of the Replication and Performance page for mobile devices.  Both the Replication and Performance pages have multiple tabs under those page. When using mobile devices to view those pages, only one tab is displayed and other tabs are displayed as drop down. The page displayed for the one tab is not stretched or not 100% covering the page.  Users can workaround this by going to All Metrics page and select either Replication or Performange metrics to get the same data.
• See bug 32011632 on orientation of the Replication Monitor page being overlapping for the 3 status panel.  This happens for users navigating directly to the Replicaton Monitor page. Users can workaround this by going to All Metrics page and click on Replication Status to get the same 3 status panel data without it being overlapping.

Both the TT EM plugin product  and documentation were tested for:

• There are no text fields that collect information about the user.
• The TT EM plugin product doesn't provide input field to collect user information.

The TT EM Plugin product was tested for the following cases:

1. Information conveyed by color is available in alternative formats, such as shape, text, font weight

The  documentation was tested for:

• Information is not conveyed using color

Both the TT EM plugin product and the documentation were tested for the following cases:

1. Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
2. Other text and images of text have a contrast ratio of at least 4.5:1

Both the TT EM Plugin product and documentation were tested for the following cases:

1. Text can be resized up to 200% without loss of content or functionality

The TT EM Plugin product was tested for the following cases:

1. Images of text are not used

The documentation 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

Both the TT EM plugin product  and documentation were tested for:

• Content that requires two-dimensional layout only presents scroll bars in the component used 
  to present the two-dimensional content.
• See bug 32011615 on the issue where horizontal scroll not showing up on the replication track table under the Replication Monitor page when the page is zoomed to 400%. Users can workaround to get to the same data in the replicaton track table by going to All Metrics page and click on Replication Tracks.
• Mobile testing was done using Chrome Simulator. See bug 32159333 on the issue with scrolling not showing up on the Replication and Performance page because of the multiple tabs on these pages. To worarkound the issue, users can switch to alternative user interface like desktop browser or display the same data using the All Metrics page.

Both the TT EM plugin product  and documentation were tested for:

• There isn't any non-text contrast available to test.

Both the TT EM plugin product  and documentation were tested  for:

• Line height (line spacing) to at least 1.5 times the font size;
• Spacing following paragraphs to at least 2 times the font size;
• Letter spacing (tracking) to at least 0.12 times the font size;
• Word spacing to at least 0.16 times the font size.

Both the TT EM Plugin and Documentation were tested for:

• Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

The TT EM Plugin product was tested for the following cases:

1. Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes

The documentation was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

Both TT EM Plugin product and documentation were tested for the following cases:

1. Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

Both the TT EM Plugin and Documentation were tested for:

• There are no single character keyboard shortcuts in the TT EM plugin product available to test.

The TT EM Plugin product was tested for the following cases:

1. Time limits in the product can be turned off before they are encountered
2. Time limits in the product can be adjusted to at least 10 times longer before encountered

The documentation was tested for:

• Time limits are not used

The TT EM Plugin product was tested for the following cases:

1. The product does not have moving, blinking or scrolling which starts automatically.
2. The product does not have any auto-updating information which starts automatically.

The  documentation was tested for:

• There is no moving, blinking or scrolling content

Both the TT EM Plugin product and documentation were tested for the following cases:

1. No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

The TT EM Plugin product does not have blocks of content that are repeated on multiple Web pages

The documentation was tested for:

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.

Both the TT EM Plugin product and documentation were tested for the following cases:

1. Pages have a meaningful title specified in the TITLE element

Both the TT EM Plugin product and documentation were tested for the following cases:

1. Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence

Both the TT EM Plugin product and documentation were tested for the following cases:

1. The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose

Both the TT EM plugin product  and documentation were tested for the following cases:

1. Pages can be found using the provided "search" function
2. Pages are in a site table of contents
3. Pages are fully inter-linked to each other
4. Page contains controls that enable reaching all pages

Both the TT EM Plugin product and documentation were tested for the following cases:

1. Headers describe the topic or purpose of the content below them
2. Labels describe the purpose of the associated field

Both the TT EM Plugin product and documentation were tested for the following cases:

1. Visual indication of the location of the focus

Both the TT EM Plugin and Documentation were tested for:

• There are no multipoint or path-based gesture actions in the TT EM plugin product to test.

Both the TT EM Plugin and Documentation were tested for:

• There are no single pointer operations in the TT EM plugin product to test.

Both the TT EM Plugin and Documentation were tested for:

• User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.

Both the TT EM Plugin and Documentation were tested for:

• There are no functions that require motion of the device.

Both the TT EM plugin product  and documentation were tested for the following cases:

• Properly set lang attribute for each page

Both the TT EM plugin product and the documentation do not contain any passages in a language different from that of the page.

Both the TT EM plugin product and the documentation were tested for the following cases:

1. 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

1. 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 documentation is readonly and has no user input, thus not applicable in this case.

1. 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

Both the TT EM plugin product and the documentation were tested for the following cases

• Images and controls are used and identified consistently throughout the product

1. When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

The documentation is readonly and has no user input, thus not applicable for input error.

1. Labels or instructions are provided when the product requires user input

The documentation is readonly and has no user input, thus not applicable in label or instructions for user input.

1. Where suggestions for fixing an input error are known, they are provided to the user

The documentation is readonly and has no user input, thus not applicable in input error.

Both the TT EM plugin product and documentation do not have web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses.

1. Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs

The documentation was tested for:

• Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
• Pages validate to the HTML specification

1. HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
2. Frames have a meaningful title specified in the title attribute

The documentation was tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.

Both the TT EM Plugin and Documentation were tested for:

• Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

The product documentation describes:

• Accessibility features that are built-in and are compatible with screen readers

Accessibility-related documentation can be found in Accessibility Guide.

Product documentation is in electronic format.