Criteria | Supporting Features | Remarks (e.g., definition, equivalent facilitation, scope of support provided) |
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product is composed of components that were tested for: - Tab order through the product controls and selectable elements
- Use of keyboard to perform selection and actions
- Buttons have additional shortcut keys to enable quicker navigation.
Exceptions: - Bug# 12539308 Cannot tab through Audit Log window tool bar.
- Bug# 16850239 When using either the "go to java types" or "go to files" ghost windows, once a desired file is selected in the list, it is not possible to dismiss the window and display the selected file using just the keyboard.
- Bug# 13771034/17622151 The web.xml flat editor is not accessible using just the keyboard.
- Bug# 13734304 The gutter and many of its icons/indicators are presently not accessible using just the keyboard.
- Bug# 8205925 When using the 'Create Variables Dialog', if there are no variables, one cannot tab from the 'Clear' icon to the 'Help' button using the keyboard.
- Bug# 12395657 When working in a Java Desktop application we cannot drag'n'drop a data control onto the structure pane using just the keyboard. A workaround is to use ctrl+v to paste the control into the actual UI editor.
- Bug# 8210737 Java Exception is encountered if we use the keyboard to add VIEW CRITERIA to filter the rows shown.
- Bug# 14692675 Not able to navigate to the "Included Classes" hierarchical tree in "Edit Filter" dialog using the 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 documented by the manufacturer of the operating system and is available to the product developer. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for response to the following operating system accessibility features: - Sticky Keys, Filter Keys and Toggle Keys
- Sound Sentry
- High Contrast
Note: these feature names are the terms used on Windows; other platforms have their own unique terminology. |
1194.21(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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Visual cue or feedback to the position of the cursor within the product
- Cursor focus is programmatically exposed.
Exceptions: - Bug# 17629354 In the tools->preferences->audit dialog->rules pane, it is not clear whether a given rule is selected or deselected. Screen Reader does not read the rule name while arrowing down to the rule.
- Bug# 17551047 Screen Reader does not recognize when code insight is invoked on some code elements while opening any kind of file in the code editor.
- Bug# 17207210 On the faces-config flat editor, when the add button is clicked on any of the pages within the overview tab to add a new converter , the Screen Reader gets stuck at that position.
- Bug# 8219340 The Screen Reader does not recognize elements in the Component Gallery dialog for the Gauge
- Bug# 14707615 In the "Edit Filter" dialog, the Screen Reader does not read the items in tree view. Instead, it just says which level it is on. Eg. it just says "level 1, 1 of 3"
- Bug# 14572299 When working in an unbounded adf taskflow, if we select insert inside task-flow -> adf taskflow -> view, the resulting dialog is inaccessible. The Screen Reader does not track the focus and does not speak the next focused control.
- Bug# 14646817 While arrowing down through the list of choices using code insight, the Screen Reader reads one row off of what is actually selected.
- Bug# 14588873 The screen reader is not reading the context menu when activated.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images that convey information can have meaningful alternative text supplied.
Exceptions: - Bug# 14565916 Screen reader does not announce the tabbed position correctly in the Oracle Diagnostic Log Analyzer.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images that convey information can have meaningful alternative text supplied.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Text is supplied in a way that is usable by assistive technology on the platform.
|
1194.21(g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Windows or other OS-level color settings not over-ruled by the product
|
1194.21(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Product has been developed to conform to this standard subject to the remarks on the right. | The product contains the following instances of animation: - Status indicator - The status indicator supports alternate text to indicate the state as busy or idle.
- Loading indicator - The loading indicator is a decorative animation image that also has text explaining that the application is loading.
- Other decorative animation effects, such as animation during the opening of popups and menus, can be turned off via a development parameter.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Alternative means used for conveying color-related information
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Product offers color contrast setting (high contrast)
- Contrast setting is consistent through the user session
- Windows or other OS-level color settings not over-ruled by the product
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product does not use flashing or blinking text, objects or other 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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Controls have a programmatically associated name
- Screen elements under magnification retain readability and are recognizable
Exceptions: - Bug# 14707530 The Profiler page is missing labels.
|