Community Funded Voluntary Product Accessibility Template

This Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate Community Funded’s efforts to conform with the accessibility standards under Section 508 of the Rehabilitation Act.

SECTION 1194.21 SOFTWARE APPLICATIONS AND OPERATING SYSTEMS – DETAIL VPAT™ 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. Partially supports Community Funded strives to develop accessible tools, and is working to ensure all elements of our products can be navigated with only a 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. Supports Applications that are identified as accessibility features obeying industry standards won’t be disrupted by our technology.
(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 Fields where information is to be input (like the campaign creation area) provide clear indication of current focus. This should be more than sufficient for assistive technology to function.
(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. Partially supports Community Funded develops features and tools to this standard. Some retrofitting of text to interface elements may be needed, and a full site audit is scheduled, to ensure ADA standards are met for user interface elements and text for images.
(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 Community Funded standardizes all bitmap images across our platforms for consistency.
(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 Provided by the browser.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supports Community Funded’s software does not prevent users from selecting their own color selections or other 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. Supports Community Funded does not rely on animation alone to display information.
(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 Community Funded does not rely on color coding as the only means of conveying information of any kind.
(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 See the answer to (i)
(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. N/A Community Funded does not design using any flashing or blinking text, objects or elements with a frequency greater than 2 Hz or 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. Supports Our forms work sufficiently with screen readers.

 

SECTION 1194.22 WEB-BASED INTERNET INFORMATION AND APPLICATIONS – DETAIL
VPAT™
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). Supports Meaningful images have alt text. Please note that non-meaningful images may contain alt text as well.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Supports Community Funded does not contain built in multimedia. Users upload their own content, and are responsible for the accessibility of their content. Please note that most multimedia used on our platforms are hosted by YouTube, and are most often accessible via YouTube’s accessibility standards.
(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 Community Funded does not use color alone to distinguish the importance of any visual element.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports Users or a screen reader can read and understand pages with associated style sheets disabled.
(e) Redundant text links shall be provided for each active region of a server-side image map. Supports Community Funded does not use server-side image maps.
(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 See answer to (e), above.
(g) Row and column headers shall be identified for data tables. Supports Data tables, such as those shown in supporter reporting, have clearly defined row and column headers.
(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 Community Funded has no 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 Supports Where frames are used, text accompanies to facilitate 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. Supports Community Funded does not cause the screen to flicker at a frequency greater than 2 Hz or 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. Supports Community Funded believes we comply with all provisions of this part. If a text-only version of a page is needed, we are happy to provide it.
(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. Partially supports Community Funded practices industry standard coding. Some retrofitting may be required, but to the best of our knowledge, assistive technology should be able to function properly.
(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 Community Funded does not require any applet or plugin to work with its default functionality.
(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 All forms on Community Funded’s sites work with screen readers. Please note that some forms associated with our platform may not be optimized for screen readers.
(o) A method shall be provided that permits users to skip repetitive navigation links. Partially supports Community Funded has standard landmark roles through most of its features. Please note some features may not be fully compatible, but improvements are always being made.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. N/A There are no timed features offered by Community Funded.

Note to 1194.22: Community Funded interprets items of this section as consistent with the Web Content Accessibility Guidelines 2.0 (WCAG 2.0) (December 8, 2008) published by the Web Accessibility Initiative of the World Wide Web Consortium: (a) 1.1, (b) 1.2, (c) 1.4, (d) 1.3 (g) 1.3, (l) 4.1, and (o) 2.4.

 

SECTION 1194.31 FUNCTIONAL PERFORMANCE CRITERIA – DETAIL
VPAT™
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. Supports
(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 Assistive technology should not be prevented from working.
(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. N/A No portion of Community Funded’s tools require hearing. Please note campaign and program videos are typically hosted at YouTube or Vimeo, so their assistive technology may provide additional support for deaf or hard of hearing users.
(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. N/A Please see the answer in (c), above.
(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. N/A User speech is not required to use Community Funded tools.
(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 Assistive technology and clean design should prevent any requirement of fine motor control. No simultaneous actions or actions requiring reach or strength are required.