Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees without disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities seeking information or services from a Federal agency have access to and use of information and data that is comparable to that provided to the general public, unless an undue burden would be imposed on the agency.
| Guideline | Applicable | ActiveReports Area | |
|---|---|---|---|
| Section 1194.21 | Software Applications and Operating Systems | Applicable | End User Designer, Windows Viewer, WPF Viewer, Web controls (HTML5 Viewer, HTML Viewer). |
| Section 1194.22 | Web-Based Intranet and Internet Information and Applications | Applicable | Web controls (HTML5 Viewer, HTML Viewer). |
| Section 1194.23 | Telecommunications Products | Not applicable | none |
| Section 1194.24 | Video and Multimedia Products | Not applicable | none |
| Section 1194.25 | Self-Contained, Closed Products | Not applicable | none |
| Section 1194.26 | Desktop and Portable Computers | Not applicable | none |
| Section 1194.31 | Functional Performance Criteria | Applicable | End User Designer, Windows Viewer, WPF Viewer, Web controls (HTML5 Viewer, HTML Viewer). |
| Section 1194.41 | Information, Documentation and Support | Applicable | Documentation and Support. |
All major features of ActiveReports software are accessible via keyboard navigation.
GRAPECITY MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. The following information reflects the general accessibility features of GrapeCity software components as related to the Section 508 standards. If you find that the information is not accurate, or if you have specific accessibility needs that our products do not meet, please contact us and we will attempt to rectify the problem, although we cannot guarantee that we will be able to do so in every case.
Section 1194.21
| Criteria | Status | Remarks |
|---|---|---|
| (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 | ActiveReports partially supports keyboard navigation. Users cannot execute report functions completely using the 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. | Supported | The controls do not disrupt or disable industry standard accessibility features of other products. |
| (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 | Some elements in ActiveReports cannot track focus. Focus is not exposed to screen readers like NVDA. |
| (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 images representing program elements do not support alternative text. Partial support for Assistive Technology is provided for some interface elements. |
| (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 | Any image used to identify a programmatic element has a consistent meaning throughout an application's performance. |
| (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 | Textual information such as text content, caret location, and any text attribute (i.e. bold, italic, size, color, etc.) is available for all the viewer elements. |
| (g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Supported with exceptions | User selected contrast and color settings are not overridden, except for some minor exceptions in End User Designer. |
| (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | Supported | Animated image is only used when a report is being loaded in the viewer. The users can provide a static text for the animation using the loadCompleted event of the Viewer. |
| (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 | Any interface element that uses color to indicate an action, prompt a response, or distinguish a visual element also provides a textual cue. |
| (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 | ActiveReports supports a variety of colors, themes and styles that can be applied to controls in a report. |
| (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 | The controls do not use flashing or blinking text or objects. |
| (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 | Any form-type dialogs or windows associated with the controls provide Assistive Technology with access to information on all directions, cues, field elements, and functionality required for completion. |
Section 1194.22
| Criteria | Status | Remarks |
|---|---|---|
| (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | Supported | Each non-text element has a text equivalent. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Not applicable | ActiveReports web controls do not include 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. | Not applicable | ActiveReports web controls do not provide any information using color. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Supported with exceptions | Toolbar icons in some web controls are not visible when the associated styles are disabled. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Not applicable | There are no server-side image maps in ActiveReports web controls. |
| (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 | ActiveReports does not use client-side image maps in ActiveReports web controls. |
| (g) Row and column headers shall be identified for data tables. | Not applicable | By default, there are no data tables associated with the ActiveReports web controls. |
| (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 | By default, there are no data tables associated with the ActiveReports web controls. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation. | Not applicable | By default, there are no frames associated with ActiveReports web controls. |
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Supported | ActiveReports Web controls do not contain any feature that causes page flickering. |
| (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 page is not available in ActiveReports Web Viewer or Web controls. |
| (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 ActiveReports HTML5 Viewer control uses scripting that is supported by 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). | Not applicable | Not applicable |
| (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 with exceptions | The components used in ActiveReports have been configured for maximum compliance. Some form controls may not support Assistive Technology. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Not applicable | ActiveReports does not support 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. | Not applicable | Timed response is not required. |
Section 1194.31
| Criteria | Status | Remarks |
|---|---|---|
| (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 with exceptions | Partial support is provided for assistive technologies like 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. | Supported | ActiveReports does not require visual acuity greater than 20/70. It is exposed to magnification tools like the Screen Magnifier that can be used for magnifying the screen. |
| (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 | ActiveReports does not use any sound output. Hearing is not necessary to use the product. |
| (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 | ActiveReports does not provide functionalities that require audio or video aids. |
| (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 | ActiveReports does not provide any functionality that make use of user speech. |
| (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 | ActiveReports does not provide any functionality that requires fine motor control or simultaneous action. |
Section 1194.41
| Criteria | Status | Remarks |
|---|---|---|
| (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. | Supported | Documentation is available in four formats: HTML(Web), *.chm, *.PDF, and Help3(Visual Studio help content) |
| (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 | ActiveReports provides information about accessibility and compatibility features in the documentation. The documentation is exposed to screen readers. |
| (c) Support services for products shall accommodate the communication needs of end-users with disabilities. | Supported | Support services such as telephone, email and forum support are provided to the customers. |