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.
Note that objects are currently not accessible by keyboard in the layout editor (Bug 3608449). The workaround is to use the object navigator. |
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 Platform defines a set of built-in accessibility features, including: - the ability to enter multi-key keystrokes by pressing only one key at a time (known as “Sticky Keys”)
- the ability to slow the keyboard repeat rate (known as “Slow Keys”)
- the ability to change the platform text size, up to 200% of normal (as part of the define “Large Print” theme setting)
- the ability to set a high contrast theme or screen setting (as part of the define “High Contrast” theme setting)
- the ability to enter text using speech recognition as an alternative to the keyboard
- the ability to magnify portions of the screen
- the ability to narrate portions of the screen
- the ability to provide visual notifications of error sounds
The UI Toolkit components respects these Platform settings, and have been tested for compatibility with them. |
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
|
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 Platform accessibility API defines an accessible name, accessible role, a set of accessible states, accessible value, and alternate accessible text for images. The UI Toolkit components implement the Platform accessibility API, and stock components support exposing the accessible name, role, and states to assistive technologies. Where appropriate, stock components also expose the value and a description of images to assistive technologies via the Platform accessibility API. The product was tested for: - Controls have a programmatically associated name, with attributes including LABEL, TITLE, SUMMARY, CAPTION.
- Additional state information is programmatically exposed, such as whether a field is required.
- All built-in images are purely decorative.
- 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 Platform accessibility API defines an accessible name, and an accessible description that applies to images, including how to indicate that an image is purely decorative. The UI Toolkit components implement the Platform accessibility API, and stock components that can display images support exposing the accessible name, and description to assistive technologies. Applications built with this tool are capable of meeting the standards if the application designer/developer follows the guidelines and applies the accessibility standards appropriately. All built-in images provided by the product are purely decorative. |
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 Platform accessibility API defines an accessible name to be used for short text contents (e.g. the “OK” of a button, the “File” of a menu item), as well as a set of accessible text API calls that provide the text content, the text input caret location, and the attributes of every character of text. Text attributes include the boundary of the text, the font size, and the font style. The UI Toolkit components implement the Platform accessibility API, and stock components support exposing the accessible name to assistive technologies. Furthermore, stock components that support displaying large chunks of text, including editable text components, support the accessible text API calls. |
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 Platform defines several sets of themes, including a high contrast theme where there is a luminosity contrast ratio of at least 4.5:1. The UI Toolkit stock components respect the platform color and contrast settings, including the high contrast theme. |
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 Form Builder product does not contain any moving or blinking items, and the UI Toolkit stock components don't support moving or blinking, so it isn't directly possible to build an application that has moving or blinking items. |
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 UI Toolkit stock components do not use color as the sole means of conveying information by default. |
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, and attributes including LABEL and TITLE.
- Screen elements under magnification retain readability and are recognizable
|