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 Platform defines a logical keyboard operation specification. UI Toolkit components meet this specification. All aspects of the core product support this behavior, except for the phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specification. |
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 core product was tested for response to the following operating system accessibility features: - Sticky Keys, Slow Keys, Filter Keys, Bounce Keys, and Toggle Keys
- Sound Sentry
- High Contrast and Large Print themes.
Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specification. |
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 core product is composed of components that have a well defined visual focus indicator which is programmatically exposed via the Java Accessibility API. The product's editable text fields have a well defined visual caret indicator displayed, which programmatically exposed via the Java Accessibility API. The core product was tested for: - Visual indication of the position of the cursor within text, and visual indication of the focused component, including with the High Contrast and Large Print themes
- Current focused component and caret location is programmatically exposed via the Java Accessibility API
Partially applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specification (applicable to emulated text editor components). The phone emulated content was tested for: - Visual indication of the position of the cursor within text, and visual indication of the focused component.
|
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 core product is composed of components that expose the AccessibleName, AccessibleRole, AccessibleStateSet, AccessibleValue, and AccessibleIcon interfaces as appropriate via the Java Accessibility API. The core product was tested for: The AccessibleName, AccessibleRole, and AccessibleStateSet of controls is programmatically exposed via the Java Accessibility API The AccessibleValue of controls that display one of a range of values is programmatically exposed via the Java Accessibility API The AccessibleIcon of controls containing an ImageIcon or other image is programmatically exposed via the Java Accessibility API Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specifications. |
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 core product was tested for: - User interface components that display a non-decorative image have an AccessibleName associated with them, and if necessary an AccessibleDescription.
- Decorative images are either not rendered as accessible user interface components, or have a null AccessibleName and a null AccessibleDescription.
- Images are used consistently throughout the product.
Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specifications. |
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 core product was tested for: User interface components that display text either: - expose a copy of their text as the AccessibleName (e.g. the text of a JButton), and/or
- expose their text via the AccessibleText interface.
Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specifications. |
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 core product was tested for: - User interface components respect the platform Look and Feel, OS-level color and contrast settings are honored by the product.
Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specifications. |
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 core product does not contain moving, blinking or scrolling information and does not contain content that is pure decoration. Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specifications. |
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. | In the core product color, or font styles, are not used as the only visual means of conveying information. Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specifications. |
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 core product was tested for: - Text and images of text in non-disabled controls have a luminosity contrast ratio of at least 4.5:1. Large scale text has a minimum ratio of at least 3:1
Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specifications. |
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 was tested for: - No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz, with the exception of the text insertion caret.
|
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 core product was tested for: - User interface component labels are associated with the fields they are labeling.
- Edit text fields have a label associated with them.
- Label associations are exposed via the AccessibleRelation interface to assistive technologies.
- Form controls expose an appropriate AccessibleName to assistive technologies.
Not applicable to phone emulated content, which runs on the CLDC/MIDP reference implementation and must support that specifications. |