Integrify meets with the 508 Compliance guidelines for Product Accessibility. You can see the detailed criteria and explanations below.
Integrify Summary Table
|
|
|
Criteria |
Level of Support & Supporting Features |
Remarks and explanations |
|
Section 1194.21 Software Applications and Operating Systems |
NOT APPLICABLE |
|
|
Section 1194.22 Web-based Internet Information and Applications |
SUPPORTS WITH EXCEPTIOnS
|
Integrify support keyboard shortcuts and screen readers for all end-user features. Drag and drop administrative features do not support keyboard shortcuts or screen readers. |
|
Section 1194.23 Telecommunications Products |
NOT APPLICABLE |
|
|
Section 1194.24 Video and Multi-media 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 |
Supports |
|
|
Section 1194.41 Information, Documentation and Support |
Supports |
|
|
|
|
Criteria |
Level of Support & 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 |
|
|
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Supports |
|
|
(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 |
|
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports |
|
|
(e) Redundant text links shall be provided for each active region of a server-side image map. |
NOT APPLICABLE |
No image maps are used |
|
(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 |
No image maps are used
|
|
(g) Row and column headers shall be identified for data tables. |
Supports |
|
|
(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 |
|
|
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Supports |
|
|
(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 |
|
|
(k) A text-only page, with equivalent information or functionality, shall be provided to make a website 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 |
|
|
(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
|
End-user features are fully supported. Drag and drop process and form designer are not accessible 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 |
No applets, plugins, or other applications are required to use the software |
|
(n) When electronic forms are designed to be completed online, 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 |
|
|
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports |
|
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supports |
|
|
|
|
Criteria |
Level of Support & 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. |
Supports through Equivalent Facilitation |
Through the use of Windows accessibility wizard - the functional needs of users who are blind and needs of users who have usable low vision. |
|
(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 through Equivalent Facilitation |
Through the use of Windows accessibility wizard - wizard the functional needs of users who are blind and needs of users who have usable low vision. |
|
(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 |
No Audio information or operation required – No information retrieval requires hearing. |
|
(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 |
|
|
(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 |
|
|
(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 |
No fine motor control or simultaneous actions required. |
Section 1194.41 Information, Documentation and Support‚ Detail
|
|
|
Criteria |
Level of Support & 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 |
Large Text copies by request. |
|
(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 |
Available by request. |
|
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supports |
Internet and Email support available. |