Investor Fact Sheet | GROV $0.067

GroveWare

about-groveware-technologies

eXFORMA – Product Accessibility

The first table 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. 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.

Summary Table

Voluntary Product Accessibility Template
Criteria Supporting Features Remarks and Explanations
Section 1194.21 Software Applications and Operating Systems Supported with minor exception eXFORMA is comprised of the eXFORMA System Console, Forms Studio and the Workflow Studio. The Workflow Studio is a Software Application that generates XML text files for use within the eXFORMA system. Users can use either the workflow studio or a plain text editor to create and modify these XML text files. Documentation is available that assists users to use both the studio and/or a text editor to generate these XML text files.eXFORMA optionally generates information in PDF, Microsoft Excel, Microsoft Word, CSV and XML file formats. The information available in these files is also available in HTML, viewable within the eXFORMA environment. Users are advised to use 508 compliant software for reading non-HTML information. eXFORMA does not provide these external software packages and they must be licensed separately.
Section 1194.22 Web-based Internet Information and Applications Supported with minor limitations 508 Compliance for eXFORMA has two components:1. The eXFORMA System Console – This is the system where users login and navigate through the areas containing forms, workflow tasks, searches, reporting, etc. including the design editors. It is the main interface to the software.
2. Forms/Interfaces developed by users – These interfaces are served by the system to users to enter/review data. Designers can create their own web pages and forms for users to use.eXFORMA is a tool to develop web-based user interfaces. It is up to the user of the system to design screens that are fully 508 compliant. For example, it is possible to include arbitrary, user developed scripts into the pages. These scripts may contravene 508 standards.eXFORMA users are responsible for ensuring that their own Web pages conform to the standards. These conditions apply to certain features within eXFORMA that should not be used if forms/interfaces are developed to be 508 compliant. See Section 1194.22 below for details.
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 Supported
Section 1194.41 Information, Documentation and Support Supported.

1194.21 Software Application and Operating Systems

Voluntary Product Accessibility Template
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. Supported with minor exception. Many features of the eXFORMA Workflow Studio are accessible via the keyboard. Some features are not accessible since they are pure mouse-driven “drag-and-drop” features requiring a mouse.However, where features are not accessible through the software application, they can be accessed via the direct modification the XML text file output. The creation and modification of XML text files for the purpose of workflow definitions is fully-supported. For visually impaired people that require only keyboard control, the editing and manipulation of the data in the XML file via a text editor is recommended and preferred.
(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. No accessibility features are disrupted or disabled.
(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. Focus changes are well-indicated on screen.
(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. All image interface elements have associated text or tooltips allowing for Assistive technology to be used to identify the image meaning.
(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. All interface images are consistent within the application.
(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 is provided through the operating system including using “I-Beam” for insertion/replacement.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supported. The software does not override user appearance operating system 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. Supported. No animation is used.
(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. All color-coded elements also have other shading identification information for distinguishing the element.
(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. A full color template is provided when color changes are selected.
(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. No flashing text or objects are used.
(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. All data input forms can be completed using the keyboard controls. Consistent text information is displayed to cue the user on the field they are completing.

1194.22 Web-based Internet Information and Applications

Voluntary Product Accessibility Template
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). Supported with minor limitation. eXFORMA System Console:All non-text elements have an “alt” text value.Forms: The form studio allows the form designer to define the “alt” text for any image. N.B. The “Rich Text Area” element should not be used since there are graphical controls that are not 508 compliant. Designers should use a regular text area element.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Supported. eXFORMA System Console:There are no multimedia objects used.Forms: Users can link and refer to multimedia. Compliance will be subject to the user.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Supported. eXFORMA System Console:There are no color-coded objects.Forms: The form designer can define colors used in the forms. Compliance will be subject to the user.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supported. eXFORMA System Console and the forms it generates use Cascading Style Sheets but the pages are readable without them.
(e) Redundant text links shall be provided for each active region of a server-side image map. Supported. eXFORMA System Console:There are no server-side image maps used.Forms: Form Designers can define image maps for use in the forms. Compliance will be subject to the user.
(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. Supported. eXFORMA System Console:Only client-side image maps are used.Forms: From Designers can define image maps for use in the forms. Compliance will be subject to the user.
(g) Row and column headers shall be identified for data tables. Supported with row headers in alternate columns. eXFORMA System Console:All data tables have column and row information that allows for easy identification of the information. Columns have headers. Row headers are available in more than one column.Forms: Designers can define data tables in the forms. Compliance will be subject to the user.
(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. Supported. eXFORMA uses only one-level of table data.
(i) Frames shall be titled with text that facilitates frame identification and navigation Supported. eXFORMA System Console:All frames used in the system are identified.Forms: They do not use 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. Supported. eXFORMA System Console:There are no flickering objects used.Forms: Forms Designers can define scripts for use in the forms that may flicker out of compliance. Compliance will be subject to the user.
(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. Supported.
(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. eXFORMA System Console:eXFORMA uses scripting language only in the Navigation Tab and is identified with functional text. Navigation can also be performed with the e-Forms Tab that is equivalent to the Navigation section. This would not require Assistive Technology.Forms: Form Designers can define scripts for use in the forms which may or may not be in compliance, but the onus is on the designer.
(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). Supported. No web pages require applets, plug-ins or other applications to be present. However, eXFORMA optionally generates information in PDF, Microsoft Excel, Microsoft Word, CSV and XML format. The information available in these files is also available in HTML, viewable within the eXFORMA environment. Users are advised to use 508 compliant software when reading non HTML information. eXFORMA does not provide these external software packages and hence must be chosen and licensed separately.
(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 minor limitation. eXFORMA System Console:All forms used within the system, including notably, the form designer, incorporate standard HTML form elements, with appropriate cues and directions.Forms: Forms developed within eXFORMA use standard HTML form elements and are fully W3C Accessible, except for the Rich Text Area element which is not 508 Compliant and should not be included in forms that are to be 508 compliant.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supported. No functions use 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. Supported. eXFORMA System Console:eXFORMA will “time-out” when a user logs in and does not interact with the system after 120 minutes. A warning is displayed.Forms: Users can define timing scripts for use in the forms. Compliance will be subject to the user.

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.

1194.31 Functional Performance Criteria

Voluntary Product Accessibility Template
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. Supported. All functions may be performed from the keyboard and all information is displayed in web pages. Accessibility features of web browser together with the use of Assistive Technology designed for web browsers may be used by people who are blind or visually impaired.
(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. All functions may be performed from the keyboard and all information is displayed in web pages. Accessibility features of web browser together with the use of Assistive Technology designed for web browsers may be used by people who are blind or visually impaired.
(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 Supported. No audio or sound is used.
(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. Supported. No audio or sound is used.
(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. Supported. No speech enabled features are used.
(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. No fine motor control or simultaneous actions are required for our software.

1194.41 Information, Documentation and Support

Voluntary Product Accessibility Template
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 Supported. A variety of electronic and hard copy formats are available upon 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. Supported. Available upon request.
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Supported.
Contact Form Powered By : XYZScripts.com