VPAT Certification of www.NeuroScript.net and MovAlyzeR (Forthcoming)

[Hans-Leo]

Section 1194.21 Software Applications and Operating Systems - Detail
Voluntary Product Accessibility Template

Criteria -- Level of Support & 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.

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

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

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

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

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

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

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

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

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

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

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

APPENDIX A (of the DoS GPAT Checklist)

SUGGESTED LANGUAGE FOR FILLING OUT THE GPAT
In order to simplify the task of conducting market research assessments for procurement officials or customers, ITIC (Information Technology Industry Council) has developed suggested language for use when filling out a V PAT/G PAT. You may choose to employ all or some of the language below. Once you determine what language you intend to use, we recommend that use is consistent throughout all of your GPATs.

SUPPORTING FEATURES (COLUMN 2 ON GPAT)
o Supports -- Use this language when you determine the product fully meets the letter and intent of the Criteria.
o Supports with Exceptions -- Use this language when you determine the product does not fully meet the letter and intent of the Criteria, but provides some level of access relative to the Criteria.
o Supports through Equivalent Facilitation -- Use this language when you have identified an alternate way to meet the intent of the Criteria or when the product does not fully meet the intent of the Criteria.
o Supports when combined with Compatible AT -- Use this language when you determine the product fully meets the letter and intent of the Criteria when used in combination with Compatible AT. For example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind).
o Does not Support -- Use this language when you determine the product does not meet the letter or intent of the Criteria.
o Not Applicable -- Use this language when you determine that the Criteria do not apply to the specific product.
o Not Applicable - Fundamental Alteration Exception Applies -- Use this language when you determine a Fundamental Alteration of the product would be required to meet the Criteria (see the access board standards for the definition of "fundamental alteration").

From: http://www.state.gov/m/irm/impact/126343.htm
IMPACT Outreach Center
IRM Program for Accessible Computer/Communication Technology (IMPACT)
(IRM/BPC/BC/SAS)
2121 Virginia Ave, N.W. (SA-3), Suite 4170
Washington, DC 20520
Email: SECTION508@state.gov
Voice: (202) 663-0221
TTY: (202) 663-0084
Internet: http://www.state.gov/m/irm/impact/index.htm
Intranet: http://impact.state.gov
** ITIC V PAT Best Practices (http://www.itic.org/reports/508/Sec508.html)

[Hans-Leo]

Section 1194.22 Web-based Internet information and applications - Detail
Voluntary Product Accessibility Template

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

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

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

(d) Documents shall be organized so they 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.

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

(g) Row and column headers shall be identified for 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.

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

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

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

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

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

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

(o) A method shall be provided that permits users to skip 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.

APPENDIX A (of the DoS GPAT Checklist)

SUGGESTED LANGUAGE FOR FILLING OUT THE GPAT
In order to simplify the task of conducting market research assessments for procurement officials or customers, ITIC (Information Technology Industry Council) has developed suggested language for use when filling out a V PAT/G PAT. You may choose to employ all or some of the language below. Once you determine what language you intend to use, we recommend that use is consistent throughout all of your GPATs.

SUPPORTING FEATURES (COLUMN 2 ON GPAT)
o Supports -- Use this language when you determine the product fully meets the letter and intent of the Criteria.
o Supports with Exceptions -- Use this language when you determine the product does not fully meet the letter and intent of the Criteria, but provides some level of access relative to the Criteria.
o Supports through Equivalent Facilitation -- Use this language when you have identified an alternate way to meet the intent of the Criteria or when the product does not fully meet the intent of the Criteria.
o Supports when combined with Compatible AT -- Use this language when you determine the product fully meets the letter and intent of the Criteria when used in combination with Compatible AT. For example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind).
o Does not Support -- Use this language when you determine the product does not meet the letter or intent of the Criteria.
o Not Applicable -- Use this language when you determine that the Criteria do not apply to the specific product.
o Not Applicable - Fundamental Alteration Exception Applies -- Use this language when you determine a Fundamental Alteration of the product would be required to meet the Criteria (see the access board standards for the definition of "fundamental alteration").

From: http://www.state.gov/m/irm/impact/126343.htm
IMPACT Outreach Center
IRM Program for Accessible Computer/Communication Technology (IMPACT)
(IRM/BPC/BC/SAS)
2121 Virginia Ave, N.W. (SA-3), Suite 4170
Washington, DC 20520
Email: SECTION508@state.gov
Voice: (202) 663-0221
TTY: (202) 663-0084
Internet: http://www.state.gov/m/irm/impact/index.htm
Intranet: http://impact.state.gov
** ITIC V PAT Best Practices (http://www.itic.org/reports/508/Sec508.html)

[Hans-Leo]

Section 1194.31 Functional Performance Criteria - Detail Voluntary Product Accessibility Template

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.

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

(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

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

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

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

APPENDIX A (of the DoS GPAT Checklist)

SUGGESTED LANGUAGE FOR FILLING OUT THE GPAT
In order to simplify the task of conducting market research assessments for procurement officials or customers, ITIC (Information Technology Industry Council) has developed suggested language for use when filling out a V PAT/G PAT. You may choose to employ all or some of the language below. Once you determine what language you intend to use, we recommend that use is consistent throughout all of your GPATs.

SUPPORTING FEATURES (COLUMN 2 ON GPAT)
o Supports -- Use this language when you determine the product fully meets the letter and intent of the Criteria.
o Supports with Exceptions -- Use this language when you determine the product does not fully meet the letter and intent of the Criteria, but provides some level of access relative to the Criteria.
o Supports through Equivalent Facilitation -- Use this language when you have identified an alternate way to meet the intent of the Criteria or when the product does not fully meet the intent of the Criteria.
o Supports when combined with Compatible AT -- Use this language when you determine the product fully meets the letter and intent of the Criteria when used in combination with Compatible AT. For example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind).
o Does not Support -- Use this language when you determine the product does not meet the letter or intent of the Criteria.
o Not Applicable -- Use this language when you determine that the Criteria do not apply to the specific product.
o Not Applicable - Fundamental Alteration Exception Applies -- Use this language when you determine a Fundamental Alteration of the product would be required to meet the Criteria (see the access board standards for the definition of "fundamental alteration").

From: http://www.state.gov/m/irm/impact/126343.htm
IMPACT Outreach Center
IRM Program for Accessible Computer/Communication Technology (IMPACT)
(IRM/BPC/BC/SAS)
2121 Virginia Ave, N.W. (SA-3), Suite 4170
Washington, DC 20520
Email: SECTION508@state.gov
Voice: (202) 663-0221
TTY: (202) 663-0084
Internet: http://www.state.gov/m/irm/impact/index.htm
Intranet: http://impact.state.gov
** ITIC V PAT Best Practices (http://www.itic.org/reports/508/Sec508.html)

[Hans-Leo]

Section 1194.41 Information, Documentation and Support - Detail Voluntary Product Accessibility Template

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

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

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

APPENDIX A (of the DoS GPAT Checklist)

SUGGESTED LANGUAGE FOR FILLING OUT THE GPAT
In order to simplify the task of conducting market research assessments for procurement officials or customers, ITIC (Information Technology Industry Council) has developed suggested language for use when filling out a V PAT/G PAT. You may choose to employ all or some of the language below. Once you determine what language you intend to use, we recommend that use is consistent throughout all of your GPATs.

SUPPORTING FEATURES (COLUMN 2 ON GPAT)
o Supports -- Use this language when you determine the product fully meets the letter and intent of the Criteria.
o Supports with Exceptions -- Use this language when you determine the product does not fully meet the letter and intent of the Criteria, but provides some level of access relative to the Criteria.
o Supports through Equivalent Facilitation -- Use this language when you have identified an alternate way to meet the intent of the Criteria or when the product does not fully meet the intent of the Criteria.
o Supports when combined with Compatible AT -- Use this language when you determine the product fully meets the letter and intent of the Criteria when used in combination with Compatible AT. For example, many software programs can provide speech output when combined with a compatible screen reader (commonly used assistive technology for people who are blind).
o Does not Support -- Use this language when you determine the product does not meet the letter or intent of the Criteria.
o Not Applicable -- Use this language when you determine that the Criteria do not apply to the specific product.
o Not Applicable - Fundamental Alteration Exception Applies -- Use this language when you determine a Fundamental Alteration of the product would be required to meet the Criteria (see the access board standards for the definition of "fundamental alteration").

From: http://www.state.gov/m/irm/impact/126343.htm
IMPACT Outreach Center
IRM Program for Accessible Computer/Communication Technology (IMPACT)
(IRM/BPC/BC/SAS)
2121 Virginia Ave, N.W. (SA-3), Suite 4170
Washington, DC 20520
Email: SECTION508@state.gov
Voice: (202) 663-0221
TTY: (202) 663-0084
Internet: http://www.state.gov/m/irm/impact/index.htm
Intranet: http://impact.state.gov
** ITIC V PAT Best Practices (http://www.itic.org/reports/508/Sec508.html)