The file's text, extracted by GovTribe without its formatting.
Proposed Section 508 Solutions for TTB Electronic Media Products
Summary Table Voluntary Product Accessibility Template
| Criteria |
| Supporting Features |
| Remarks and explanations |
| Section 1194.21 Software Applications and Operating Systems |
| Supports. |
| See details below. |
| Section 1194.22 Web-based internet information and applications |
| Supports. |
| See details below. |
| Section 1194.23 Telecommunications Products |
| Not Applicable. |
| Not Applicable. |
| Section 1194.24 Video and Multi-media Products |
| Supports. |
| See details below. |
| Section 1194.25 Self-Contained, Closed Products |
| Not Applicable. |
| Not Applicable. |
| Section 1194.26 Desktop and Portable Computers |
| Not Applicable. |
| Not Applicable. |
| Section 1194.31 Functional Performance Criteria |
| Supports. |
| See details below. |
| Section 1194.41 Information, Documentation, and Support |
| Supports. |
| See details below. |
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. |
| ALT Text is available for product functions. |
| Product functions will be displayed through ALT Text. |
| (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. |
| The product will be compatible with industry standard accessibility features. |
The product will be compatible with existing Windows operating system accessibility features.
The product will follow industry standard accessibility features and will be compatible with Windows operating system 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. |
| When appropriate, highlights and textual cues will be used to indicate current focus. |
| The product will programmatically highlight and/ort textually cue Assistive Technology of any focus changes. |
| (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. |
| Alt Text and textual cues will be used to identify the operation and state of interface elements. |
| The Alt text and textual cues will describe to assistive technologies the operation and current state of interface elements. |
| (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. |
| Consistent use of bitmap images to identify controls and status indicators will be used. |
| If a bitmap image is used to identify control or status indicators, it will consistently be used to convey the same meaning. |
| (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. |
| When appropriate, textual information will be provided through native operating system functions for displaying text. |
| When appropriate, the identified standards for displaying text will be used. No controls or Xtras will be used to display textual content. |
| (g) Applications shall not override user selected contrast and color selections and other individual display attributes. |
| The product will not override user-selected attributes. |
| The product will not override user-selected 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. |
| A text-alternative page is provided when necessary. In the case of a Flash application independent of the web, Flash accessibility features will be provided in the form of a text description of the animation. |
| D-Links are used to provide a text-only alternative to animations. In the case of a browser independent Flash application, no D-Links are necessary and the text description will be embedded within the page containing the animation. The screen reader will read the a description of the animation as it is played. |
| (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. |
| Color is not used exclusively to convey meaning. |
| As a style, the use of color to convey information is not used exclusively. Alternatives such as text and audio prompts are also used. |
| (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. |
| Color adjustments are not used. |
| As a style, the WBT interface will use a high contrast between the text and background. Color adjustment will not be available. |
| (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. |
| No flashing animations are used. |
| As a style, the use of flicker to gain attention is not used. |
| (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. |
| Standard TAB, shift TAB functions are used for keyboard navigation. ALT Text is used for form fields. |
| Keyboard functionality has been provided to allow forms to be completed without using the mouse. ALT Text in conjunction with Assistive Technologies provides directions and cues. |
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). |
| ALT Text and D-Links are used for all instructional media. |
| ALT Text is used for all appropriate graphics and media. ALT Text may be read by the student or the screen reader. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
| For flash captioning is provided in real time by Hi-Caption Software which can either be read by the student or the screen reader. |
| Using Flash scripting capabilities, the multimedia presentation can synchronize ALT tag information. |
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. |
| Color is not used exclusively to convey meaning. |
| As a style, the use of color to convey information is not used exclusively. Alternatives such as text and audio prompts are also used. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. |
| Pages are designed in a logical presentational order. |
| Pages will be presented in a way that Flash reads logically |
| (e) Redundant text links shall be provided for each active region of a server-side image map. |
| Server-side image maps will not be utilized. |
| Only client-side image maps will be utilized. |
| (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. |
| Flash does not use image maps. Hotspots are identified the same way as text links that can be accessed with the Tab key. Only client-side maps shall be used in the web. |
| Flash buttons are used instead of image maps, therefore this does not apply to Flash applications. For standard HTML, only client-side maps will be used |
| (g) Row and column headers shall be identified for data tables. |
| HTML they will be identified, we will use no tables in Flash. If we use a Table like structure the information will be presented in a logical manner for the screen reader. |
| Row and column headers shall be identified/marked up as needed in HTML. In Flash a logical order will be presented for the sake of screen readers. |
| (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. |
| If necessary, markup is utilized. |
| Markup is used in HTML. Data cells and tables are not used in Flash so this is a non-issue |
| (i) Frames shall be titled with text that facilitates frame identification and navigation |
| Frames are not used in either applications or web. |
| Not currently using 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. |
| No flashing animations are used. |
| As a style, the use of flicker to gain attention is not used. |
| (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. |
| A text-alternative page is provided when necessary. |
| With Flash scripting, the use of text-only pages is not necessary as 508 accessibility can be provided in a manner that gives the same interactive experience for all users. HTML a text only page can be provided |
| (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. |
| ALT tags and D-links are utilized. |
| Flash scripting is used to enable Assistive Technologies to read functional text. HTML will use ALT tags and D-links |
| (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). |
| Appropriate links are utilized when necessary. |
| Learners are provided a link to download the appropriate plug-ins if necessary. |
Section 1194.22 Web-based Internet information and applications - Detail
| Criteria |
| Supporting Features |
| Remarks and explanations |
| (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. |
| Standard TAB, shift TAB functions are used for keyboard navigation. ALT Text is used for form fields. |
| Keyboard functionality has been provided to allow forms to be completed without using the mouse. ALT Text in conjunction with Assistive Technologies provides directions and cues. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. |
| Navigation is presented after appropriate content. |
| Instructional content is displayed and presented before navigational features are read by Assistive Technologies. |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
| No timed responses are utilized. |
| As a style, timed responses are avoided. If used, learners are provided with audio and visual prompts. |
Section 1194.24 Video and multimedia products
| Criteria |
| Supporting Features |
| Remarks and explanations |
| (c) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned. |
| Flash video/multimedia will be captioned using Hi-Caption, or with use of on screen text that can be read by a screen reader |
| Video will be close-captioned using Hi-Caption, and animations will be described with the Flash Description and Comments which can be read by the screen reader. |
| (d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described. |
| There are no videos. Mutimedia/audio will be close captioned |
| Hi-Caption can be used or text descriptions on screen depending on the need of the application/user |
| (e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent. |
| Accessible menu items can be placed to identify the users desire for a text only page if needed |
| A D-link can be provided so the user has an alternate text presention or audio presentation as needed. |
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. |
| JAWS support will be provided. For flash we will verify with AC- Repair for 508 compliancy |
| The JAWS screen reader will be used. And verification for Flash will be accomplished using AC-Repair |
| (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. |
| If applicable, Flash can be programmed to provide enlarged screen content to individuals with visual impairments. |
| For visual acuity needs, native enlarged print output will be supported. |
| (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 |
| All non-text information will be conveyed in a textual format. |
| As a style, all audio narration is represented textually on the screen. Where necessary, audio narration not represented on the screen will be available through closed captioning. |
| (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. |
| Courseware will provide volume control capability. |
| For enhanced auditory capability, native volume controls will be supported. |
| (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. |
| User speech will not be required. |
| None of the courseware functionality will require user interaction through speaking. |
| (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. |
| Mouse and keyboard functionality are supported. |
| When applicable, mouse and keyboard navigation are available with limited reach and strength. |
Section 1194.41 Information, Documentation, and Support - Detail Voluntary Product Accessibility Template
| 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 |
| If necessary, documentation provided in Print Format will be made available electronically. |
| (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 |
| If necessary, documentation provided in Print Format will be made available electronically. |
| (c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
| Not applicable |
| Support services beyond product delivery are not a requirement of the contract. |
