Taskstream is committed to making its tools accessible for all users, including people with disabilities. Our tools comply with Federal Section 508 guidelines, Bobby, and W3C WCAG recommendations as described below. Some optional services and third-party plug-ins may not be covered by this document. As new technologies emerge, Taskstream strives to amend its tools to be compliant with the widest audience possible; however, for legacy reasons, some pages may not be updated immediately.
In addition to making technical changes to our websites to provide greater accessibility, we test them with multiple assistive technologies — such as screen readers and screen enlarging software — to analyze and modify our pages. We also engage accessibility experts and people with disabilities to further test and modify our websites for optimal usability.
For more information, contact Mentoring Services at email@example.com.
|Accessibility Criteria||Taskstream Support|
|A text equivalent for every non-text element shall be provided (e.g., via “alt,” “longdesc,” or in element content).||All Taskstream images have descriptive alt tags supplied, allowing screen readers and users who choose to not display graphics to understand the content.When an author adds images to his or her own content, he or she is prompted to include alt text as well.|
|Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.||Taskstream provides alternative meta content for multimedia presentations. At this time, authors are responsible for ensuring any uploaded multimedia content is accessible.|
|Pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.||The Taskstream tools do not use color as the sole method of information. Authors are encouraged to provide alternative context for color-specific images as well.|
|Documents shall be organized so they are readable without requiring an associated style sheet.||Taskstream pages are readable without an associated style sheet.|
|Redundant text links shall be provided for each active region of a server-side image map.||Taskstream does not use server-side image maps in its tools.|
|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.||Taskstream does not use server-side image maps in its tools. Where client-side image maps are employed, a text-only list of links is provided.|
|Row and column headers shall be identified for data tables.||Taskstream provides a descriptive summary in lieu of row and column headers for data tables that may be too complex to associate row columns and headers.|
|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.||Taskstream provides a descriptive summary for data tables that may be too complex to associate row columns and headers.|
|Frames shall be titled with text that facilitates frame identification and navigation.||Taskstream’s frames are named with identifying long titles.|
|Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.||Taskstream’s blinking images do not cause the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.|
|A text-only page, with equivalent information or functionality, shall be provided to make a website 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.||Taskstream does not currently offer a text-only version of functional pages. If a function is added to the tools that cannot be rendered in accordance with the 508 standards, an alternate representation will be added.|
|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.||The Taskstream tools require the enabling of client-side scripting to display some conditional content. The scripted content is rendered in accordance with accessibility guidelines, with the limitations noted in this document.|
|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 of Federal Section 508 guidelines.||Taskstream utilizes the Flash and Acrobat plug-ins to display some content, both of which are compliant with accessibility guidelines. Links to plug-ins are provided. Additionally, author-uploaded files may be launched using applications installed on the users’ individual machines.|
|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.||Taskstream form elements are identified by label and are accessible via keyboard inputs.|
|A method shall be provided that permits users to skip repetitive navigation links.||Because the main Taskstream navigation is contained within a separate frame, users may skip the repetitive menu links and access the main tools content directly. When navigation is repeated on the main content frame, the number of links is kept to a minimum.|
|When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.||Taskstream users are not required to perform any action within a specified time period. In cases where an author’s work is auto-saved after a period of inactivity, a pop-up alert is provided, with the option to extend the working time.|