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# 14646817: When using code insight, and arrowing down through the list of available choices, the screen reader reads the previously selected item and not the current selection.
- Bug# 14572299: In an unbounded adf taskflow, when we select insert inside task-flow -> adf taskflow -> view, the resulting dialog is inaccessible.
- Bug# 13771034: The web.xml flat editor is not accessible using just the keyboard.
- Bug# 12539308: Cannot navigate through the Audit Log window tool bar using just the keyboard.
- Bug# 12396896: In the Fusion Web ADF application, we cannot navigate to the find option in the Page Definition page using the keyboard.
- Bug# 19970090: The Monitors window opened using the keyboard for debugging any test program cannot be closed using the keyboard.
- Bug# 19970098: The Inspect window opened using the keyboard for debugging any test program cannot be closed using the keyboard.
- Bug# 19970129: In the Stacks window opened using the keyboard for debugging any test program, the thread dropdown cannot be accessed using the keyboard.
- Bug# 19970141: The search field and the terminate button in any Debugger Log window cannot be accessed 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# 6196889 : The Application Navigator Display Options and associated menu dropdowns do not show keyboard focus.
- Bug# 12394629 : When creating a servlet listener, if the finish button is clicked before the listener context is selected, an error dialog is displayed. However, focus is on the OK button and cannot move from that button, and the text of the error is not ready.
- Bug# 14572299 : In an unbounded ADF taskflow, when we enter a value in the resulting view and press tab to move to the next field, the screen reader does not track the focus and does not announce the next focussed control.
- Bug# 18597816: Screen reader does not read the data in the message pane.
- Bug# 17629354: In the tools->prefferences->audit dialog, once we tab into the rules pane, there is no way to tell which rules are selected or deselected.
- Bug# 17207210: In the faces-config flat editor, in the overview -> converters tab, if the add button is clicked to add a new converter, the screen reader gets stuck and does not read anything.
- Bug# 16808835: In the Fusion Provisioning Wizard, when the focus is on the LHS, and the up/down arrow keys are used, it automatically moves to the previous/next page. The expected behavior is that, using the up/down arrow keys should allow the user to navigate to the previous/next page selection, and when the user confirms by pressing Enter, then it should move to the selected page.
- Bug# 19970109: While debugging any test program by opening the Stacks window using the keyboard, and when the focus is set on the drop down, the Screen reader does not read out the selected item in the Stacks window, instead it only reads-out the key that is pressed.
- Bug# 19970115: While debugging any test program by opening the Threads window using the keyboard, and when the focus is set on the drop down, the Screen reader does not read out the selected item in the Threads window, instead it only reads-out the key that is pressed.
|
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.
|
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# 6788671 : The Tasks window, opened by selecting the menu item 'Tasks' from the main menu 'View', allows the user to add filters to narrow the number of tasks displayed. The construction of such a filter is done in the 'Filter Tasks' dialog. However, if using the keyboard only it is only possible to add a new filter but not to modify its configuration.
- Bug# 8728885 : When working in a facelet and attempting to drop a JSF html message component onto the page, a dialog dropdownlist is displayed; the text in this list is not recognized by AT. The workaround is to use the Property Inspector to change the 'for' property of h:message.
|