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.
Date: April 23, 2012
Name of product: Adobe® Business Catalyst® Dreamweaver® extension v1.03
Contact for more information: access@adobe.com
Summary Table
| Guideline | Applicable | Compliance |
|---|---|---|
Section 1194.21 Software Applications and Operating Systems |
Applicable |
Does not support |
Section 1194.22 Web-Based Intranet and Internet Information and Applications |
Applicable |
Supports |
Section 1194.23 Telecommunications Products |
Not applicable |
— |
Section 1194.24 Video and Multimedia Products |
Not applicable |
— |
Section 1194.25 Self-Contained, Closed Products |
Not applicable |
— |
Section 1194.26 Desktop and Portable Computers |
Not applicable |
— |
Section 1194.31 Functional Performance Criteria |
Applicable |
Does not support |
Section 1194.41 Information, Documentation, and Support |
Applicable |
Supports |
| Criteria | Supporting features | 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. |
Supports with exceptions |
Most features and controls in the panel and dialogs provided by the Business Catalyst extension are can be operated by keyboard. However, the items in the Module tree control cannot be expanded or activated using a keyboard. |
(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 |
The Business Catalyst extension does not interfere with operating system accessibility features. |
(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. |
Does not support |
All interactive controls in the panel and dialogs provided by the Business Catalyst extension provide a visual indication of focus. However, none of the controls in the Business Catalyst panel or dialog boxes expose focus programmatically. |
(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 |
None of the interface elements provided by the Business Catalyst extension expose any information about role, identity, state, or operation to assistive technology. |
(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 |
Bitmap images are used consistently in the Business Catalyst extension. |
(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. |
Does not support |
The textual information provided by the Business Catalyst extension UI is not provided through operating system functions for displaying text. |
(g) Applications shall not override user-selected contrast and color selections and other individual display attributes. |
Does not support |
The Business Catalyst extension panel and dialogs do not inherit Windows High Contrast mode. |
(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 Business Catalyst extension interface 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. |
Supports |
The Business Catalyst extension interface does not use color as the only means of conveying information, indicating an action, prompting a response with the exception of highlights for elements like Editable Regions. However, the colors used can be edited and there are alternative ways of conveying this information, such as Code View. |
(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 |
The Business Catalyst extension does not permit the user to adjust color and contrast settings of the product with the exception of code coloring and Highlights. |
(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 |
The Business Catalyst extension does not use flashing or blinking text, objects, or other elements in the software's 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 |
None of the form controls in the Business Catalyst extension panel and dialogs are exposed to assistive technology. |
| Criteria | Supporting features | Remarks and explanations |
|---|---|---|
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt," "longdesc," or in element content). |
Supports |
The Business Catalyst extension allows users to insert images through the Dreamweaver interface, which prompts users to enter image equivalents. |
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Supports |
The Business Catalyst extension supports the inclusion of multimedia content created with other tools. Authors can add accessibility features to their multimedia utilizing the features of third party tools. |
(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 |
The Business Catalyst extension allows authors to convey meaning with alternatives or with additional text. |
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports |
The Business Catalyst extension allows authors to create pages that meet this requirement. |
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Supports |
The Business Catalyst extension allows authors to create pages that meet this requirement and does not use image maps in its templates. |
(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 |
The Business Catalyst extension allows authors to create pages that meet this requirement and does not use image maps in its templates. |
(g) Row and column headers shall be identified for data tables. |
Supports |
The Business Catalyst extension supports the creation of row and column headers for tables through the Dreamweaver user interface. |
(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. |
Supports |
The Business Catalyst extension supports the association of multiple row and column headers with related data cells through the Dreamweaver user interface. |
(i) Frames shall be titled with text that facilitates frame identification and navigation. |
Supports |
The Business Catalyst extension prompts authors to provide frame titles through the Dreamweaver user interface. |
(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 |
The Business Catalyst extension supports the creation of content that meets this requirement. |
(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. |
Supports |
The Business Catalyst extension allows authors to create pages that meet this requirement. However, some features require JavaScript to be enabled on browser because they rely on system-generated scripts that cannot be edited by authors. The list of features that require JavaScript on browser includes – add to cart, check out and post new forum comments. |
(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 |
Authors can create their own scripts or use scripts generated by The Business Catalyst. Authors can edit their own scripts within Dreamweaver to ensure compliance with this standard. Scripts generated by Adobe Business Catalyst cannot be edited by authors but are compliant with this requirement. |
(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). |
Supports |
The Business Catalyst extension allows authors to create pages that meet this requirement. |
(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. |
Supports |
The Business Catalyst extension automatically generates accessible labels when creating web forms, and allows users to modify labels in the HTML code view. |
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports |
The Business Catalyst extension supports the inclusion of skip navigation links as well as headings and other structural elements that can help users skip repetitive elements. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supports |
The Business Catalyst extension does not create time-based content by default. Authors need to verify compliance in content created in Business Catalyst. |
Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following Priority 1 checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5, 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) – 1.1, (b) – 1.4, (c) – 2.1, (d) – 6.1, (e) – 1.2, (f) – 9.1, (g) – 5.1, (h) – 5.2, (i) – 12.1, (j) – 7.1, (k) – 11.4.
| Criteria | Supporting features | 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. |
Does not support |
None of the panel and dialog content provided by the Business Catalyst extension expose information to technology for users who are blind. |
(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. |
Does not support |
None of the controls provided by the Business Catalyst extension track focus programmatically. |
(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 |
|
| Criteria | Supporting features | Remarks and explanations |
|---|---|---|
(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. |
Supports |
Adobe provides electronic versions of all product support documentation. |
(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. |
Supports |
Adobe provides information on accessibility features in the documentation. Electronic versions of all product support documentation are provided. |
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supports |
Product support for Adobe products is available in a variety of formats and from a number of online sources available from Adobe Systems. |
