Preorder Estimated Availability Date. Your credit card will not be charged until the product is shipped. Estimated availability date is subject to change.Preorder Estimated Availability Date. Your credit card will not be charged until the product is ready to download. Estimated availability date is subject to change.

Adobe SiteCatalyst 15 Voluntary Product Accessibility Template

The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding the availability of commercial Electronic and Information Technology products and services with features that support accessibility. It is assumed that offerers will provide additional contact information to facilitate more detailed inquiries.

The first table of the Template provides a summary view of the section 508 Standards. The subsequent tables provide more detailed views of each subsection. There are three columns in each table. Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, "e.g., equivalent facilitation." The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.

(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.

Does not support

Many of the controls in the SiteCatalyst interface are fully operable using a keyboard alone. However, main navigation menus, such as the left hand menu, are not keyboard accessible.

The combo box under the SiteCatalyst logo causes a new page to load when it receives keyboard focus.

Some functions, such as selecting a downloadable report format, are not operable using a keyboard alone.

Some controls, such as the My Dashboards menu, are not included in the tab order.

Complex controls for assembling Dashboards are not keyboard accessible.

(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.

Supports

SiteCatalyst does not interfere with or deactivate accessibility features of the operating system.

(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.

Supports with exceptions

There is a clear visual indication of focus for some controls, such as those in the main Online Marketing Suite menu.

However, other controls such as icons for report controls provide a faint visual indication of focus.

Focus is programmatically exposed for those elements that can receive focus.

(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.

Does not support

Many of the interface elements in SiteCatalyst do not provide sufficient information to assistive technology.

For example, many controls in the Add Metrics dialog box do not include labels.

Controls for assembling Dashboards in the New Dashboard view, such as the content menu or the drop areas, do not provide sufficient information.

Menu items, such as those in the My Dashboards menu, provide incorrect role information.

Information is not available for some content, such as graphs.

Many text elements expose a role of ‘editable text field.’

(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.

Supports

(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.

Supports with exceptions

Textual information in SiteCatalyst is programmatically exposed to assistive technologies in form inputs.

Textual information is not fully exposed in some other cases, such as text in reports. Text in many areas of SiteCatalyst has a role of ‘editable text field’.

The SiteCatalyst interface supports Windows High Contrast Mode with some exceptions, including:

The main Online Marketing Suite menu does not inherit user settings.

Graphs and charts do not inherit user settings.

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

Supports with exceptions

SiteCatalyst provides animation only when loading data. The loading data animation does not have a text equivalent.

(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.

Supports with exceptions

SiteCatalyst includes graphs and charts and these, in some situations, convey information through color alone.

(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

SiteCatalyst does not permit a user to adjust color and contrast settings.

(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.

Supports

SiteCatalyst does not use flashing or blinking text, objects or other such elements in the user interface.

(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.

Does not support

Some form controls in the SiteCatalyst interface do not provide sufficient information to assistive technologies.

For example, many fields in the Add Metrics dialog box do not include labels.

Some controls in on-screen forms, such as the Add Note form, do not include labels.

Some form controls in the SiteCatalyst interface are not reachable using the keyboard alone.

For example, some icons on the reports screens are not reachable using the keyboard alone, such as the ‘Download’ icon.

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt," "longdesc," or in element content).

Supports with exceptions

Some non-text elements in SiteCatalyst do not provide text alternatives. For example:

Dividers in menus do not include empty ‘alt’ attributes.

Reports containing graphs and charts do not include alternate text descriptions.

Some interface widgets, such as the Hide Graph button, do not have labels.

Flash graphs, such as the Mid Level Report graph, do not include labels.

(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.

Supports with exceptions

SiteCatalyst includes graphs and charts and these, in some situations, convey information through color alone.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Does not support

SiteCatalyst does not function without an associated style sheet. Elements are displayed on the screen out of context when stylesheets are not used.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not applicable

SiteCatalyst does not use server-side 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.

Supports

Client-side image maps are used instead of server-side image maps.

(g) Row and column headers shall be identified for data tables.

Does not support

Data tables, such as those used in reports, do not include row and column headers that are available to assistive technology.

(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.

Does not support

Data tables in SiteCatalyst reports, such as the Marketing Channel Overview Report, that include two or more levels of row or column headers, do not include markup to associate data cells with headers.

(i) Frames shall be titled with text that facilitates frame identification and navigation.

Does not support

Hidden IFrames in the SiteCatalyst interface do not have titles.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Supports

SiteCatalyst does not feature flickering content.

(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

SiteCatalyst compliance can be achieved in other ways and does not require a text-only alternative.

(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.

Supports with exceptions

SiteCatalyst utilizes scripting in the application. Many interface elements created by scripts do not include functional text that can be read by assistive technology, including:

Graphs and charts generated in reports.

Some script generated widgets, such as the expand/collapse controls on the Marketing Channel Overview Report, do not provide sufficient information to assistive technology.

(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).

Does not support

SiteCatalyst includes Flash content, which requires the Flash plug-in be present on the client system. No link to the Flash plug-in is provided but users can download the plug-in from the Adobe web site.

Some reports are available for download in PDF format and there is no adjacent link provided to the Acrobat Reader. However, PDF is an alternate format to the data tables and graphs in SiteCatalyst.

(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.

Does not support

Some form controls in the SiteCatalyst interface do not provide sufficient information to assistive technologies.

For example, many fields in the Add Metrics dialog box do not include labels.

Some controls in on-screen forms, such as the Add Note form, do not include labels.

Some form controls in the SiteCatalyst interface are not reachable using the keyboard alone.

For example, some icons on the reports screens are not reachable using the keyboard alone, such as the ‘Download’ icon.

(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.

Does not support

Many of the elements in the SiteCatalyst interface cannot be operated by assistive technologies such as screen readers.

Navigation items, such as menus, are not operable using the keyboard alone.

Many controls in the interface including widgets in the New Dashboard screen, and graphs and charts, do not provide sufficient information to screen readers.

(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.

Supports with exceptions

SiteCatalyst supports the use of Screen Magnifiers. However, there is not a clear visual indication of focus for some interface controls.

(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.

Supports

(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.

Supports

(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.

Supports

(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.

Supports with exceptions

Some operations in the SiteCatalyst interface may require fine motor control, such as selecting options in context menus, including the ‘Breakdown by…’ menu. There is no keyboard equivalent for these options.