Adobe ColdFusion Builder - Section 508 Voluntary Product Accessibility Template

Section 1194.21 Software Applications and Operating Systems

Applicable

Supports with Exceptions

Section 1194.22 Web-Based Intranet and Internet Information and Applications

Applicable

(Authoring only)

Supports with Exceptions

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

Supports with Exceptions

Section 1194.41 Information, Documentation, and Support

Applicable

Supports

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

Supports with exceptions
(Authoring)

Most controls in the ColdFusion Builder interface are fully operable using a keyboard alone with some exceptions including:

It is difficult to move focus between panels and between the Code Editor and other panels using the keyboard alone, especially in complex perspective layouts.

Error messages in the Code Editor are not keyboard accessible.

ColdFusion Builder allows authors to generate keyboard executable HTML/XHTML code.

However, some elements in ColdFusion may not fully support keyboard accessibility, such as the cftextarea tag (using the rich text attribute) and the cfgrid header controls.

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

Supports
(Authoring)

The ColdFusion Builder interface does not interfere with or deactivate accessibility features of any operating system.

Applications built using ColdFusion Builder do not interfere with or deactivate accessibility features of any 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
(Interface)

Supports with exceptions
(Authoring)

There is a visual indication of focus for most controls in the ColdFusion Builder interface but the indication is weak in some cases, such as the Perspective buttons on the main toolbar.

Current focus is programmatically exposed.

There is a clear indication of focus for most focusable elements generated with ColdFusion Builder.

Authors can add CSS styles to provide additional, visual indications of focus.

Exceptions include tables created using the cfgrid tag.

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

Supports with exceptions
(Interface)

Supports with exceptions
(Authoring)

Interface elements in ColdFusion Builder provide identity, role and state information to Assistive Technology with some exceptions, including:

Information is not available for controls in the ColdFusion Builder installer.

Color picker controls do not provide information to Assistive Technology.

ColdFusion Builder enables authors to generate code that correctly provides identity, role and state information to Assistive Technology with the exception of some more complex controls, for example:

Identity information is not available for the controls generated by the rich text editor option of cftextinput.

Identity or state information is unavailable for cfcalendar.

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

Supports
(Authoring)

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

Supports with exceptions
(Authoring)

Text information in the ColdFusion Builder interface is available to Assistive Technology.

ColdFusion Builder allows authors to create text and text input controls that meet this requirement.

Exceptions include the complex controls included in the cftextarea tag (using the rich text attribute). 

(g) Applications shall not override user-selected contrast and color selections and other individual display attributes.

Supports with exceptions
(Interface)

Supports with exceptions
(Authoring)

The ColdFusion interface inherits user settings selected in Windows High Contrast mode and has a specific ‘reduced palette’ option in the software Preferences to inherit system colors and other display settings. However, there are some exceptions, including:

Text in Tree Menus does not fully support user settings.

ColdFusion Builder allows authors to create pages that meet this requirement.

Exceptions include tags that generate complex controls such as cfcalendar and cftree.

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

Supports
(Authoring)

ColdFusion Builder does not use animation in the user interface.

ColdFusion Builder allows authors to provide an alternative to animated content.

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

Supports with exceptions
(Authoring)

The ColdFusion Builder interface does not use color as the only means of conveying information.

Sections of code can be highlighted using color but these colors can be edited in the software Preferences and other indications can be added, such as bold and italic formatting.

ColdFusion Builder allows authors to avoid using color as the only means of conveying information.

Exceptions include the cfcalendar tag’s use of highlighting for specific days.

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

Supports with exceptions
(Interface)

Supports
(Authoring)

The ColdFusion Builder interface is customizable with a range of color and contrast options, but this does not cover all elements of the interface.

ColdFusion Builder allows authors to provide this functionality in their ColdFusion sites and applications. Code can be provided to enable users to set color and contrast based on a range of options provided by the ColdFusion author

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

Supports
(Authoring)

ColdFusion Builder does not use flashing or blinking text, objects, or other elements in the software's user interface.

ColdFusion Builder allows authors to generate code that does not use flashing or blinking text.

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

Supports with exceptions
(Interface)

Supports with exceptions
(Authoring)

With some exceptions, including the controls in the installer and color pickers, forms in the ColdFusion Builder interface provide sufficient information to Assistive Technology.

Forms in ColdFusion Builder are fully operable using the keyboard alone.

ColdFusion Builder enables authors to generate keyboard executable form controls that provide sufficient information to Assistive Technology.

Exceptions are limited to that of the cfml language and the installed version of ColdFusion Server.

Exceptions include the cfgrid controls generated using the richtext attribute of cftextarea.

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

Supports with exceptions
(Authoring)

ColdFusion Builder allows authors to assign equivalents to all relevant html and xhtml tags.

Use of the Code Assist feature and built-in code generation short-cuts will auto-generate the alternate text attribute for some tags.

Exceptions are limited to that of the CFML language and the installed version of ColdFusion Server.

Exceptions include some images generated using cfmap and cfchart.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Supports with exceptions
(Authoring)

ColdFusion Builder supports the inclusion of multimedia content created with other tools.  Authors can add accessibility features to their multimedia utilizing the features of 3rd party tools.

Exceptions are limited to that of the cfml language and the installed version of ColdFusion Server.

Exceptions include the built-in media player, which does not support captioning.

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

ColdFusion Builder 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
(Authoring)

ColdFusion Builder allows authors to create pages that are readable without requiring an associated style sheet.

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

Supports
(Authoring)

ColdFusion Builder allows authors to create code that meets this requirement.

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

ColdFusion Builder allows authors to create client-side image maps that meet this requirement.

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

Supports (Authoring)

ColdFusion Builder allows authors to assign headers to data tables.

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

ColdFusion Builder allows authors to associate data headers with table cells for complex tables.

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

Supports
(Authoring)

ColdFusion Builder allows authors to add descriptive titles to frames.

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

ColdFusion Builder allows authors to create pages that meet 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
(Authoring)

ColdFusion Builder allows authors to create text-only pages.

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

ColdFusion Builder allows authors to create pages that meet this requirement.

Exceptions are limited to that of the cfml language and the installed version of ColdFusion Server.

Exceptions include the richtext editor attribute of the cftextarea control. Functional text is not available in that instance.

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

ColdFusion Builder allows authors to create links to plug-ins or other applications in their ColdFusion projects.

(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 with exceptions
(Authoring)

ColdFusion Builder allows authors to generate keyboard executable form controls that provide sufficient information to Assistive Technology.

Exceptions are limited to that of the cfml language and the installed version of ColdFusion Server.

Exceptions include cfgrid header controls and controls generated with the richtext attribute of the cftextarea input.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Supports
(Authoring)

ColdFusion Builder allows authors to implement a variety of methods to skip repetitive navigation links, including a visible link to page content and the inclusion of structural HTML elements, such as headings.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Supports
(Authoring)

ColdFusion Builder allows authors to implement accessible notifications that meet this requirement.

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

Supports with exceptions
(Interface)

Supports with exceptions
(Authoring)

Most commands and form controls in the ColdFusion Builder interface are accessible to screen readers with some exceptions including:

Controls in the installer do not provide sufficient information to screen readers.

Error messages in the Code Editor are not keyboard accessible.

ColdFusion Builder allows authors to generate keyboard executable html/xhtml code.

Some complex controls are not fully keyboard accessible.

ColdFusion Builder authors can add identity, role and state information to interface elements with the exception of some complex controls.

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

Supports with exceptions
(Authoring)

There is a visual indication of focus for most controls in the ColdFusion Builder interface but the indication is weak in some cases, such as the Perspective buttons on the main toolbar.

Current focus is programmatically exposed.

There is a clear indication of focus for most ColdFusion focusable elements generated with ColdFusion Builder. However, in some cases focus events are not programmatically exposed such as in the tables created by cfgrid.

Authors can add CSS styles to provide additional, visual indications of focus.

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

Supports
(Authoring)

ColdFusion Builder allows authors to create content that meets this requirement.

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

Supports
(Authoring)

ColdFusion Builder allows authors to create content that meets this requirement.

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

Supports
(Authoring)

ColdFusion Builder allows authors to create content that meets this requirement.

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

Supports
(Authoring)

ColdFusion Builder allows authors to create content that meets this requirement.

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