Logo for The Department of Better Technology.

Screendoor Voluntary Product Accessibility Template

The Voluntary Product Accessibility Template (VPAT) is a standardized form developed in partnership by the Information Technology Industry Council (ITI) and the U.S. General Services Administration (GSA) to document a product’s compliance with key regulations of Section 508 of the Rehabilitation Act.

The following VPAT document serves to help Federal contracting officials and other buyers make preliminary assessments about Screendoor’s accessibility support.

The first table of the Template 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, e.g., “equivalent facilitation.” 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.

Date: March 9, 2016

Name of product: Screendoor

Contact for more information: Joshua Goldstein, 1 (877) 294-DOBT, hello@dobt.co

Summary Table

Criteria Supporting Features Remarks and explanations
Section 1194.21 Software Applications and Operating Systems Supports
Section 1194.22 Web-based Internet Information and Applications Supports with exceptions See specific exceptions noted below.
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

Section 1194.21 Software Applications and Operating Systems – Detail

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. Supports Each function in Screendoor can be performed using the keyboard alone.
(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 Screendoor does not affect accessibility features of the underlying operating system or browser.
(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 Screendoor provides a visible indication of the focus state.
(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. Supports Screendoor uses best-practices such as alt and aria attributes to convey information to AT.
(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. Not applicable
(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 Screendoor makes available text content, caret location, and text attributes.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. Supports Screendoor does not override user selected contrast and color selections.
(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 Screendoor displays some JavaScript/CSS animations, but they are purely cosmetic.
(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 Screendoor provides text descriptions of color-coded content.
(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 Screendoor allows for customizing the color combinations on its forms, but all of the color combinations are checked for contrast guidelines at the WCAG AA level.
(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. Not applicable No Screendoor feature uses flashing or blinking elements.
(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 All forms on Screendoor are accessible to people using AT.

Section 1194.22 Web-based Internet information and applications – Detail

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 with exceptions For most non-text elements, Screendoor provides a text equivalent that is spelled and spaced correctly. A small percentage of elements (i.e. icon links) lack a text equivalent.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Not applicable Screendoor does not provide multimedia content.
(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 Screendoor does not require color for any of its features.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Supports Screendoor organizes all web pages with semantic HTML tags that are readable without CSS.
(e) Redundant text links shall be provided for each active region of a server-side image map. Not applicable Screendoor 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. Not applicable Screendoor does not use client-side image maps.
(g) Row and column headers shall be identified for data tables. Supports All data tables use 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 Screendoor includes semantic markup to associate data cells and header cells for all data tables.
(i) Frames shall be titled with text that facilitates frame identification and navigation Supports Screendoor does 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. Supports Screendoor features do not cause any screen flicker.
(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 Screendoor complies with the provisions without requiring a text-only page.
(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 Screendoor uses JavaScript in a manner that is accessible to users of AT.
(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 No applets or plug-ins are necessary to view content on Screendoor.
(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. Supports Screendoor’s forms are fully usable for users of AT.
(o) A method shall be provided that permits users to skip repetitive navigation links. Supports Screendoor provides a “Skip navigation” link at the top of the page, visible for users navigating by keyboard alone.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Supports Screendoor does not require timed responses.

Section 1194.31 Functional Performance Criteria – Detail

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 Screendoor can be used with a screen reader such as NVDA or JAWS.
(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 Screendoor’s font sizes can be increased with the web browser’s native functionality.
(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 Screendoor does not require user 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 Screendoor does not require user hearing.
(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 Screendoor does not require 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. Not applicable Screendoor does not require fine motor controls to use.

Section 1194.41 Information, Documentation and Support – Detail

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 Supports Screendoor documentation is available at http://help.dobt.co. End-users can request alternate formats of support documentation by emailing support@dobt.co.
(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 End-users can request documentation regarding accessibility by emailing support@dobt.co.
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. Supports through equivalent facilitation While DOBT does not offer phone support with TTY relay services, end-users with disabilities can email support@dobt.co or refer to our support documentation at http://help.dobt.co.