DEQUE PRODUCTS VAT's
Deque is committed to improving the accessibility of its software products and solutions. We are also proactively educating our partners about Section 508 and the Access Board.s regulations on accessible technology. As accessibility requirements evolve, our customers will continue to receive the most current product in our effort to meet the accessibility needs of individuals with disabilities and users of assistive technologies.
Deque's software products are subject to subsections 1194.21 (Software applications and operating systems) and subsections 1194.22 (Web based internet applications) of The Electronic and Information Technology Accessibility Standards.
The Voluntary Product Accessibility Templates below state whether applicable accessibility requirements (under the EIT Accessibility Standards) are supported by the application and documents specific exceptions if any.
| Section 1194.22 | Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|---|
| (a) | A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | Supported | |
| (b) | Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Not Applicable | |
| (c) | Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Supported | Color has been used to indicate required fields in forms; these have also been marked with an asterisk (*). Structure and meaning conveyed through color are also available in text form through the title attribute used on anchors and images. |
| (d) | Documents shall be organized so they are readable without requiring an associated style sheet. | Supported | Deque-Worldspace uses style sheets to specify color, structure, and other presentation effects. A user may select a suitable style sheet from the Preferences panel. Structure and meaning conveyed through color are also available in text form through the title attribute used on anchors and images. |
| (e) | Redundant text links shall be provided for each active region of a server-side image map. | Not Applicable | |
| (f) | Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. | Not Applicable | |
| (g) | Row and column headers shall be identified for data tables. | Supported | |
| (h) | Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. | Supported | |
| (i) | Frames shall be titled with text that facilitates frame identification and navigation | Supported | |
| (j) | Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Not applicable | |
| (k) | A text-only page, with equivalent information or functionality, shall be provided to make a website comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. | Not applicable | Deque Worldspace is accessible and does not need to use the technique of text-only pages for accessibility. |
| (l) | When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology. | Supported | Deque-Worldspace application uses scripting to conditionally write some content to a page. Content rendered in this manner is written to the screen before the page loads, and can be distinguished from standard content by the status prefixed to the message. Balidation messages inform the user of special conditions (such as missing information in a form being submitted). Scripting is also used to arrange Content of data tables in a user-specified order. The presence of this feature is conveyed in text through the summary attribute of data tables. An accessible non-floating action panel interface may be selected from the Preferences to facilitate keyboard navigation. |
| (m) | When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with .1194.21(a) through (l). | Supported | Deque-Worldspace does not use any plug-ins. An applet is used on the remediation page for image-maps. |
| (n) | When electronic forms are designed to be completed on-line, 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. | Supported | |
| (o) | A method shall be provided that permits users to skip repetitive navigation links. | Supported | |
| (p) | When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Not Applicable |
| Section 1194.21 | Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|---|
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (g) | Applications shall not override user selected contrast and color selections and other individual display attributes. | Supported | |
| (h) | When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Not applicable | |
| (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. | Supported | |
| (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. | Not applicable | |
| (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. | Not applicable | |
| (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. | Supported |
| Section 1194.21 | Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|---|
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (g) | Applications shall not override user selected contrast and color selections and other individual display attributes. | Supported | |
| (h) | When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Not applicable | |
| (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. | Supported | |
| (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. | Not applicable | |
| (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. | Not applicable | |
| (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. | Supported |
| Section 1194.21 | Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|---|
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (g) | Applications shall not override user selected contrast and color selections and other individual display attributes. | Supported | |
| (h) | When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Not applicable | |
| (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. | Supported | |
| (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. | Not applicable | |
| (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. | Not applicable | |
| (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. | Supported |
| Section 1194.21 | Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|---|
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (g) | Applications shall not override user selected contrast and color selections and other individual display attributes. | Supported | |
| (h) | When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Not applicable | |
| (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. | Supported | |
| (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. | Not applicable | |
| (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. | Not applicable | |
| (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. | Supported |
| Section 1194.21 | Criteria | Supporting Feature | Remarks and Explanations |
|---|---|---|---|
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (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. | Supported | |
| (g) | Applications shall not override user selected contrast and color selections and other individual display attributes. | Supported | |
| (h) | When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Not applicable | |
| (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. | Supported | |
| (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. | Not applicable | |
| (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. | Not applicable | |
| (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. | Supported |