Date: February 2, 2017
Product Name: eChalk Public Website
Product Version Number: 8.1
Vendor Company Name: eChalk
Vendor Contact Name: Dave Milne, VP. Product and Technology
Vendor Contact Telephone: (212) 809-8400
Summary Table |
||
Section |
Applicable/ Not Applicable |
Remarks and explanations |
Section 1194.21 Software Applications and Operating Systems |
Applicable |
|
Section 1194.22 Web-based Internet Information and Applications |
Applicable |
|
Section 1194.23 Telecommunications Products |
Not Applicable |
eChalk is not a Telecommunications Product |
Section 1194.24 Video and Multi-media Products |
Not Applicable |
eChalk is not a Multi-media Product |
Section 1194.25 Self-Contained, Closed Products |
Not Applicable |
eChalk is not a Self-Contained, Closed Product |
Section 1194.26 Desktop and Portable Computers |
Not Applicable |
eChalk is not a Desktop or Portable Computer |
Section 1194.31 Functional Performance Criteria |
Applicable |
|
Section 1194.41 Information, Documentation and Support |
Applicable |
|
Section 1194.21 Software Applications and Operating Systems – Detail |
||
---|---|---|
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. |
Supports with Exceptions |
End users can navigate and interact with all functional components of eChalk websites with just a keyboard. Results of interactions are all discernable textually. eChalk supports a number of keyboard shortcuts (e.g. tab, enter, direction keys) to enable the primary functionality of the application.
Keyboard functionality was verified through testing by eChalk’s design team. We tested all system default pages (calendar, profile, directory) and also custom created pages with every block type (e.g. text, image, feed). Tested with JAWS, NVDA, and voiceover. Exceptions: There are still outstanding issues with repetitive instructions through the voice readers (e.g. reading “clickable” on every clickable element in NVDA). |
(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 |
eChalk does not disable or disrupt any operating system, browser shortcuts or other products that are identified as accessibility features. |
(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 with Exceptions |
Focus is well defined with use of the keyboard: a well-defined on-screen indication (a prominent color rectangle around the active control) of the current focus is provided that moves among interactive interface elements as the input focus changes.
Throughout an eChalk website, the focus is programmatically exposed so that Assistive Technology can track focus and focus changes.
Exceptions:
|
(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 with exceptions |
eChalk provides information about most user interface elements including identity, operation and state of the element.
Exceptions:
|
(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 with exceptions |
The meaning assigned to these images is consistent throughout the site.
eChalk utilizes title text for any images (e.g. calendar icon, “more info” down arrow, etc.) that are used to control the application.
Exception: the school logo acts as a control to take user back to the homepage. Currently this control is not identified by title text (currently announces “logo”). |
(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 |
Textual information on eChalk websites is presented as text, not images. Text content, text input caret location, and text attributes are available. |
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. |
Supported |
eChalk does not override contrast or color selections on the local device made by the end user. |
(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 with exceptions |
The limited animation in the eChalk website (e.g. underlining navigation elements in some themes) is decorative; no additional information is conveyed by the animation.
Image gallery, feed, and event blocks include non-animated presentation mode options for the page author. However, if the author chooses an animated mode, animated controls are described in text. An exception is the slide show, where hovering stops the progression of slides, but information is not provided to a screen reader on how to stop the progression. |
(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 with exceptions |
In most instances, eChalk does not use color alone to distinguish visual elements. Exceptions:
|
(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 |
eChalk's color selection tool uses the entire spectrum of perceivable colors. We recognize that choosing high-contrast combinations takes time; we plan to provide help articles on high contrast combinations. |
(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. |
Supports |
eChalk does not use flashing or blinking objects or text with this frequency range. The highest speed on the image autoplay gallery is 1hz (1 image per second). |
(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 with Exceptions |
eChalk forms (e.g. directory filter) 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.
Exception:In directory search field, the “hint text” is used by Assistive Technology to direct the user. |
Section 1194.22 Web-based Intranet and Internet information and Applications – Detail |
||
---|---|---|
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
|
Alt text is provided for all non-text elements, including: Header images, Logo, header scroll down arrow, view monthly calendar link, Close button in popup gallery, etc. |
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Supports with exceptions |
eChalk does not have multimedia presentation tools. There is no player within eChalk; any multimedia presentation on an eChalk site is delivered by a customer-chosen embedded third party tool. Any player with an embed code can be used within eChalk, including YouTube, Vimeo, and JW Player. The only element of eChalk that uses multimedia is in our Help Center. eChalk Help videos are not captioned. Alternative text exists. See 1194.41 (a). |
(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 with exceptions |
In most instances, eChalk does not use color alone to convey information.
Exceptions:
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports with exceptions |
eChalk pages are readable without a style sheet. Exception: Skip navigation does not work without style sheet |
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Not applicable |
eChalk 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 |
eChalk does not use image maps |
(g) Row and column headers shall be identified for data tables. |
Supports |
Customers can create data tables using the RTE with accessible row and column headers. The RTE creates standard table markup (e.g. <Thead>, <TH> and <TD> tags). |
(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 with exceptions. |
eChalk provides the necessary tools to create accessible data tables with two or more logical levels of row or column headers. The RTE tool does not provide a tool for associating id attributes to data and header cells, but this association can be created by hand in the markup. |
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Not Applicable |
eChalk 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 |
eChalk does not use flashing or blinking objects or text with this frequency range. The highest speed on the image autoplay gallery is 1hz (1 image per second). |
(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 |
eChalk does not create equivalent text-only pages. |
(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 |
For all pages utilizing scripting language to display content (e.g. in navigation, the functional text is the link name; on event block controls, the functional text is “next event”; on photo block controls, functional text is “next image,” etc.) the information provided by the script is 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). |
Not Applicable |
eChalk does not require any applets or plug-ins. Customer-created content may require an applet, plug-in, or application; in this case customer can provide the necessary applet, plug-in, or application. |
(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 |
eChalk forms (e.g. directory filter) 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. In directory search field, the “hint text” is used by Assistive Technology to direct the user. |
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports |
eChalk users can skip repetitive navigation links on every page. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Not Applicable |
No timed responses are required. |
Section 1194.31 Functional Performance Criteria – Detail |
||
---|---|---|
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 with Exceptions |
eChalk has been optimized to work with screen readers. See responses to 1194.21 and 1194.22 above. |
(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 |
eChalk pages are responsive and support browser zoom functionality and operating system screen magnification. Because we use responsive design on all pages, all functional elements of all web pages work well under 200% magnification. eChalk’s layout and typography are coded with scalable relative units. |
(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 |
eChalk does not require hearing for operation. All support documentation that is provided in audio format is duplicated in text format. |
(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. |
Supports with exceptions |
eChalk generally does not use audio for its operation. Users can upload their own content and are responsible for that content’s accessibility. One exception is our Help Center, where content is provided in text form and also in Video form. The video, however, is not close captioned. |
(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. |
Supports |
eChalk does not require speech for operation |
(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 with exceptions |
eChalk does not require fine motor control and is navigable via keyboard. However we have not tested eye tracking or voice recognition software. |
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 |
Product support is available at http://help.echalk.com. Text versions of all support documentation are provided. Text versions of support documentation are compatible with screen readers. Video versions of the most frequently used support documents are also provided in the Help Center. Each video includes a text transcription, however videos are not closed captioned or audio captioned. Beyond the above, no further versions of support documentation are available. |
|
(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. |
Does not support |
eChalk does not currently provide a description of the accessibility and compatibility features of our products. |
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supports with exceptions |
eChalk support services are delivered via telephone and via email. We do not currently provide a TTY number. Our support staff is not yet trained in use of Relay Line or in responding to end users with accessibility issues. |
This document describes the extent to which the product conforms to the applicable U.S. Section 508 standards, subject to eChalk’s interpretation of those standards and the remarks in this document. This VPAT does not cover the following product areas:
- eChalk Content Management System
- eChalk Learning Management System
- eChalk Groups Management System
Note: This document is provided for information purposes only and the contents hereof are subject to change without notice. eChalk Inc. does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. eChalk Inc. specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. eChalk further makes no representation concerning the ability of assistive technologies or other products to interoperate with eChalk products. This document addresses the named product(s) only.