Tacklebox Features
Accessibility & Section 508 Compliance
In 1998, Congress amended Section 508 of the Rehabilitation Act.
The mandate requires Federal agencies to make their electronic and information technology accessible to people with disabilities, to eliminate barriers in information technology, to make available new opportunities for people with disabilities, and to encourage development of technologies that will help achieve these goals.
Brook Group is committed to making Tacklebox fully Section 508 compliant. The following table describes how we ensure that the Tacklebox CMS meets the government’s accessibility requirements.
|
| Criteria | Supporting Features | Remarks and Explanations |
|---|---|---|
| Section 1194.21 Software Applications and Operating Systems | Not Applicable. | |
| Section 1194.22 Web-based internet information and applications | Tacklebox is a Web-based application. The application supports the accessibility criteria in Section 1194.22. See Detail, below. | The Tacklebox interface supports Section 1194.22. Tacklebox CMS can be used to create content on customer Web sites; however, it is the responsibility of the Web site owners and developers to ensure that this content is accessible. |
| 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 | Not Applicable. |
Section 1194.22 Web-based Internet information and applications — Detail 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). | Supported.
All images in the interface have appropriate alt attributes. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. Tacklebox CMS requires authors to assign alt tags to images they upload. The CMS also gives them the capability to upload text files to use as long descriptions, alternatives to PDF files, etc. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Not Applicable.
The interface does not include multimedia elements. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. Tacklebox CMS gives authors the ability to upload multimedia files; it’s up to authors to make sure they are properly captioned. |
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Supported.
The interface does not rely on color alone to convey information. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Supported.
The interface is readable and navigable when user chooses not to use the associated style sheets. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Not Applicable.
The interface does not include any server-side image maps. |
Tacklebox CMS does not offer authors an ability to create 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.
The interface does not include any client-side image maps. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. Tacklebox CMS gives authors the ability to upload images and manipulate the HTML code to create accessible image maps. |
| (g) Row and column headers shall be identified for data tables. | Supported.
The interface has several data tables with one level of row or column headers; the headers are identified. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. Tacklebox CMS includes a Section 508 table tool for authors to mark up headers of 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. | Not Applicable.
The interface does not include tables with two or more logical levels of row or column headers. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. Tacklebox CMS includes a Section 508 table tool that marks up headers of data tables with multiple logical levels. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation. | Not Applicable.
The interface does not contain 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. | Not Applicable.
The interface only containes one animation; this animation is slower than 2 Hz. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. |
| (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.
The interface complies with Section 508 guidelines, so a text equivalent is not needed. |
The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. Tacklebox CMS includes a capability to upload text files, if needed. |
| (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. | Supported.
All functionality and information is accessible to assistive technologies that support JavaScript. |
User-triggered events are labeled. Events are accessible via keyboard; they do not require use of mouse. Decorative (non-informational) rollover effects are the only exception; they are mouse-driven. The Tacklebox interface is compliant with this guideline; however, site authors are responsible for the content that they create. |
| (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). | Supported.
Tacklebox uses a third party plug-in (ActiveX Control); this plug-in is Section 508 compliant. The interface supplies a link to the plug-in if user does not already have it installed. The plug-in is not required, to use Tacklebox. |
The Tacklebox interface is compliant with this guideline; however, authors are responsible for the content on the pages; they are responsible for including a link to a plug-in, wherever needed. Tacklebox CMS also includes a preprogrammed “quicklink” to Adobe’s download page for Acrobat, so that authors can easily include a link to this page with their content. |
| (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. | Supported.
All form elements are marked up. All functionality and information is accessible to assistive technologies that support JavaScript. |
Form elements are associated with their labels using the “label for” tag. Form elements that don’t have a label are described with “title” attributes. All functionality is accessible by keyboard; mouse is not required. The Tacklebox interface is compliant with this guideline; however, authors are responsible for the content on the pages. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Supported.
Each set of repetitive navigation links has a feature to allow users to skip the links. |
|
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Not Applicable.
The application does not require a timed response. |
There is a session time-out period; this time period is configurable by the customer. |