VPAT Version: 1.0
This Voluntary Product Accessibility Template (VPAT) assists Federal officials in assessing the accessibility of Citrix XenApp. The document contains two parts. The first part lists the features of XenApp that comply with Section 508 of the Rehabilitation Act and those features that do not comply. For the compliant features, the second part of the document provides more detail about how the requirements of Section 508 are met and lists any exceptions.
| Date: | 24 March 2010 |
| Name of product: | Citrix XenApp 6 for Windows Server 2008 R2, Citrix Single Sign-On 4.8 |
| Contact for more information: | http://support.citrix.com/ |
Citrix XenApp and Single Sign-On are Section 508 compliant subject to the exceptions detailed in this document.
The first table summarizes Section 508 requirements as defined by subsections in the Act and states in general terms the level of support provided by the compliant features of the product. Subsequent tables state in greater detail the level of support provided by the product for each paragraph in the Act.
Additional remarks and explanations regarding accessibility are given where appropriate in the last column of the table along with descriptions of any exceptions. In communications with Citrix concerning an exception, please reference the integer in brackets.
Note that for this release the following Assistive Technology was used to verify accessibility: JAWS version 11.0.
| Section | Level of support | Remarks and explanations |
|---|---|---|
| 1194.21 Software applications and operating systems | The product is created to meet this requirement subject to the comments in the tables that follow. | |
| 1194.22 Web-based Internet information and applications | The product is created to meet this requirement subject to the comments in the tables that follow. | |
| 1194.23 Telecommunications products | Not applicable | XenApp is not a product of this type. |
| 1194.24 Video and multi-media products | Not applicable | XenApp is not a product of this type. |
| 1194.25 Self-contained, closed products | Not applicable | XenApp is not a product of this type. |
| 1194.26 Desktop and portable computers | Not applicable | XenApp is not a product of this type. |
| 1194.31 Functional performance criteria | The product is created to meet this requirement subject to the comments in the tables that follow. | |
| 1194.41 Information, documentation, and support | The product is created to meet this requirement subject to the comments in the tables that follow. |
| Criterion | Level of support | 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 with exceptions |
Users cannot select certain interface elements or perform certain functions with the keyboard. [169966, 179530, 182148, 187522, 187526, 188832, 188833, 188836, 188838] Pressing ENTER has different effects depending on which row of a table is selected. [#188836] Incorrect default action is specified for certain key strokes. [#188838, 188840] Some controls appear only as images, with no text alternative available on the screen. [#178076, 188843] Pressing ESC does not close the dialog box (3rd party). [212283] Pressing ESC does not trigger Cancel button (3rd party). [214696] Pressing ESC does not close dialog box. [214825] The URL of a newly created site cannot be copied or pasted (with mouse or keyboard). [212297] There is no text equivalent for "rename site." [212304] Cannot rename a site with the keyboard. [212304] In Web Interface, when a tab is active, its label is excluded from the tab order. [212456] Cannot tab into the Secure Client Access pane. [211903] In the Delivery Services Console, when focus is on the Policies node, access keys in the middle pane are not visible or usable until focus is put on a control within the pane. [225558, 225560] An arrow key can be used to move focus to a radio button, but the radio button is not selected (third-party issue). [223355] In the Delivery Services Console, when focus is on the User or Computer tabs that correspond to the Policies node, the buttons associated with policies do not fit in the pane, and there is no alternate way to achieve the same functionality; to make all buttons visible, hide the right-hand pane (From the Action menu, click Other tasks\Set accessibility). [226256] In the XenApp Server Roles window, when the user puts focus on a role with an arrow key, the role is not selected with the spacebar. This is because focus is on the label, the check box, and the icon. To put focus on the label, use the right arrow key, then use the spacebar to select or clear the check box. [223324] A keyboard cannot be used to put focus on a control, even through the use of access keys; a mouse is required. [224934] A keyboard cannot be used to switch focus between tabs; a mouse is required. [225783] A keyboard cannot be used to traverse a list; a mouse is required. [224934] Some links have been excluded from the tab order and are therefore not reachable through the keyboard. [225907] Text in a read-only text box cannot be selected with the keyboard. [225230] The mouse is required for scrolling through a text box. [224273] Some controls are missing labels. [225908] Some list controls are missing labels. [224868] Some text boxes are missing labels. [224886, 224986] Some controls are missing from the tab order. [222660, 222811, 223010, 223115] |
| (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 with exceptions |
Certain interface elements are unclear or invisible when using the High Contrast feature. [#173698, 173806, 173948, 174302] Certain interface elements do not display in high contrast when the High Contrast feature is enabled. [#187523] Some screen elements in the Licensing installer are not clearly visible when the display is set to high contrast. [224992] Some screen elements in the policy-related windows are not clearly visible when the display is set to high contrast. [224936, 224937, 224974] Some screen elements in the Server Configuration wizard are not clearly visible when the display is set to high contrast. [225005] Some screen elements in the Server Role Manager are not clearly visible when the display is set to high contrast. [224997] Some screen elements in the Server Roles wizard are not clearly visible when the display is set to high contrast. [224999] Some screen elements of the group policy editor are not visible when the display is set to high contrast. Users requiring the use of high contrast can set the group policy via the Citrix.Common.GroupPolicy snap-in for PowerShell. [222642] The main installer windows do not change to high contrast when the display is set to high contrast. [224996] |
| (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 with exceptions The product was tested with Assistive Technology and can be used with such technology subject to the exceptions in the next column. |
Focus is lost after using an arrow key or TAB. [174062, 174303] When navigating around the user interface using the keyboard, focus can move to unexpected elements. [174062, 174299, 179530, 187222, 187528, 188833, 182946, 181787] No interface element is in focus when certain dialog boxes are opened. [187529, 188818, 188841] Items do not change color when selected in the Form Definition wizard. [182806, 182815] Arrow keys cannot be used to move focus between buttons in a list (3rd party). [214419] When a selection is made on a drop-down list, the screen is redrawn and focus is no longer on drop-down list. [213316] Inconsistent use of color makes it difficult to determine if a button has been selected or enabled. [212446] A disabled control appears enabled. When the user tries to move focus to this control, focus jumps to the next control in the tab order. [224864] Focus cannot be put on a read-only control. [224933, 225230] Focus disappears as the user tabs around the window. [223115, 223215, 224762, 224855, 225767, 225907] If a child window closes, focus disappears. [223215] If a child window closes, focus returns to a control other than the one used to open it. [223215] In the middle pane of the Delivery Services Console, the standard CTRL+TAB operation does not move focus between tabs. Left and right arrow keys do work, however. [225759] TAB and arrow keys sometimes move focus to unexpected controls. [225215, 225769] Focus does not land on the first item in a list when the user navigates to the list control with the TAB key. [223324] Focus lands on controls that should not receive focus. [222811] When viewing the Licensing Management Console with Internet Explorer 8, focus is not visible when it lands on links and buttons (third party issue). [225915] When a window opens, it receives focus, but the focus is not visible on any control. [222795, 223321, 224780, 224788] All controls are in the TAB order, but the TAB order is incorrect. [224871] SHIFT+TAB order is not the inverse of tab order, so focus lands on an unexpected control. [223115, 224855] The TAB key moves focus within a list in the left pane instead of to the list item's corresponding settings in the right pane. To move focus to the right pane, use the right arrow instead. [223359] There are two tab stops associated with one control, but only one works. [223215] |
| (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 with exceptions The product was tested with Assistive Technology and can be used with such technology subject to the exceptions in the next column. |
Screen reader reads strings in source code that do not describe certain interface elements. [166091, 168424, 171114, 184267, 187529] Screen reader reads additional text as well as the required text. [174004] Screen reader reads the wrong text for certain interface elements. [173945, 173947, 187522] Screen reader reads text in incorrect order. [174294] Screen reader does not read certain interface elements. [170940, 171114, 173945, 173998, 174004, 174033, 174036, 174142, 174294, 174295, 174303, 184267, 184516, 187522, 188390, 188826, 188827, 188831, 188842] In Password Manager’s Configure Control Text dialog box, the field labels of the external application being configured are not available for the screen reader to read. [197354] No, incorrect, or insufficient assistive text is included for certain interface elements. [173694, 174033, 181760, 187522, 187527] Unavailable option appears selectable. [173694] Text identifying the type of unit to enter is placed after a field, not before. [173943] Mouse clicks select or clear options in some dialog boxes from unexpected positions. [188821] JAWS does not read column headers in table (3rd party). [214719] JAWS speaks the internal string identifying screen graphics (3rd party). [214716, 214719] Headers within the Summary pane are not accessible to JAWS. [213439] JAWS reads "graphic heading image" when focus lands on Citrix logo. [213413] JAWS reads title of previous window in a wizard. [213567] In "Add Load Evaluator," the screen reader sometimes calls out information unrelated to the rule being edited. [225771] In the Delivery Services Console, the screen reader speaks "Dialog" when focus lands in a new section or on a ghost tab stop. [225757] In the Server Role Manager, the screen reader does not call out all the links and buttons. [225660] The screen reader says "1 of 1" for each radio button in a list. [225891] The screen reader calls the first radio button "2 of 2" and the second radio button "1 of 2." [225746] The screen reader says an internal string instead of the proper assistive text. [225785, 225891, 225893] The screen reader says internal strings in addition to the proper assistive text. [225656, 225754] The screen reader correctly identifies read-only text as such, but only says "Blank" when the user enters commands to read text (third party). [225774] The screen reader does not call out the assistive text that appears beneath a button. [225751] The screen reader does not call out the visible labels for some buttons and links. [225643] The screen reader sometimes causes Microsoft Management Console to crash when the user navigates to the Citrix Policies pane (third party). [225780] The label indicating units appears after a text box, making units unavailable to the screen reader. [224906] When focus lands on a control, the screen reader only says the control type (such as "link" or "checkbox"), but not the control label. [225917, 225918] When a new window opens, the screen reader does not identify the window title. [225748, 225890] When the user enters a command to read the entire contents of window, the screen reader only identifies two graphics. [225891, 225893] When the user navigates to the splitter bar with the TAB key, the screen reader remains silent. [225890] When a window opens, the screen reader identifies the window title, but not the assistive text that appears before the first control in the window. [225656] When a window opens, the screen reader only identifies the window title. [225908] |
| (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. | Partially Supported | Certain interface elements do not display in high contrast when the High Contrast feature is enabled. [187523] Certain interface elements are unclear or invisible when using the High Contrast feature. [173698, 173806, 173948, 174302] |
| (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 | The product does not use animation. |
| (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 with exceptions | Color is the only distinguishing feature of information represented in charts generated by Power & Capacity Management (3rd party). [212100] Only highlighting is used to indicate that table rows have insufficient disk space; no textual equivalent is provided (3rd party). [214413] If there is an error associated with a text box, it is indicated by outlining the text box with a red line. [225896] The color used for the label of a disabled button makes it appear enabled. [224988] |
| (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. | Supported | |
| (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. | Supported | |
| (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 |
| Criterion | Level of support | 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 with exceptions |
No ALT text is provided in the charts generated by Power & Capacity Management (3rd party). [212100] In Web Interface, ALT tags for some spinner images are missing a meaningful description. [213573] |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Not Applicable | The product does not use multimedia. |
| (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 | The product is designed so that all information conveyed with color is also available without color using context or mark-up. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Supported | The product can be used without the associated style sheet. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Not Applicable | The product does not use image maps. |
| (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 | The product does not use image maps. |
| (g) Row and column headers shall be identified for data tables. | Not Applicable | Tables are used for design purposes only (not for displaying data in tabular form). |
| (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. | Not Applicable | Tables are used for design purposes only (not for displaying data in tabular form). |
| (i) Frames shall be titled with text that facilitates frame identification and navigation | Supported | Frames are titled. |
| (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 | The product does not use multimedia or animation. |
| (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site 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 | Text-only pages are not required because the product is compliant with §1194.22. |
| (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 | The product uses JavaScript and has been tested using assistive technology (JAWS) to ensure the output from scripts is accessible. |
| (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). | Not Applicable | The product does not require the use of plug-in applications. |
| (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 | The product uses appropriate mark-up and has been tested using assistive technology (JAWS) to ensure the forms are accessible. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Not Applicable | The product does not use repetitive navigation links. |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Supported | The product provides appropriate controls when a timed response is required. |
| Criterion | Level of support | Remarks and explanations |
|---|---|---|
| (a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. | Supported | The product was tested with screen-reader technology and can be used by blind or visually impaired users of such technology. |
| (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. | Supported | The product was tested with screen-reader technology and can be used by blind or visually impaired users of such technology. |
| (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided. | Not Applicable | The product does not use audio to convey information. |
| (d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. | Not Applicable | The product does not use audio to convey information. |
| (e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided. | Not Applicable | The product does not require speech input. |
| (f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. | Supported | Features that require fine motor control are also accessible using the keyboard. Additionally, where appropriate (for example, where keyboard shortcuts are provided) the product supports the use of “sticky keys.” Any exceptions are noted in §1194.21(a). |
| Criterion | Level of support | Remarks and explanations |
|---|---|---|
| (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. | Supported | |
| (b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. | Supported | You can find this document and VPATs for additional Citrix releases at http://www.citrix.com/support/security-compliance/section-508.html. |
| (c) Support services for products shall accommodate the communication needs of end-users with disabilities. | Supported |