| Section 1194.21 Software Applications and Operating Systems |
| Section 508 Criteria |
SyberWorks Supporting Features |
SyberWorks 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. |
Supported |
Accessible using a keyboard as an input device. We use Visual Basic accessibility features for keyboard control in SyberWorks desktop applications (Author, Demonstrator, etc) |
| (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. |
Supported |
Content is developed using HTML and JavaScript for display in a Web Browser. No code has been created to alter the performance of the Web Browser and a Web Browser cannot inherently disrupt or disable activated features of other products. SyberWorks desktop applications do not disrupt or disable features of other programs. |
| (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. |
Supported |
Focus management for online tools and content is handled by the browser (by default). |
| (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. |
Supported |
User interface state information for online tools and content is handled by the browser (by default). We use standard HTML elements (and are moving towards XHTML 1.0 compliance). |
| (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. |
Supported |
When bitmap images are used to identify controls (i.e. a button) they are used consistently. Furthermore, there are text-based alternatives for all buttons. |
| (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. |
Supported |
Text and text display management is handled by the browser (by default). |
| (g) Applications shall not override user selected contrast and color selections and other individual display attributes. |
Supported |
No overriding color, contrast or display attributes are specified by our course content or desktop applications. |
| (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. |
Supported |
Our online tools and desktop applications do not contain any animation nor does content produced by our authoring tools rely upon animation to convey meaning. |
| (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. |
Not Applicable |
Not Applicable-Color coding is NOT used as a means s of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
| (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. |
Not Applicable |
|
| (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 |
|
| (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. |
Supported |
We use standard HTML elements for web content (and are moving towards XHTML 1.0 compliance). We use Visual Basic accessibility features for keyboard control in SyberWorks desktop applications (Author, Demonstrator, etc) We have tested our forms using assistive technology. |
| Section 1194.22 Web-based Internet information and applications |
| Section 508 Criteria |
SyberWorks Supporting Features |
SyberWorks 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 |
SyberWorks provides alternative text and long description tags for all images |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Not Applicable |
|
| (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 |
SyberWorks does not represent meaning with color. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supported |
SyberWorks online content is comprehensible to Freedom Scientific Corporation Assistive Technology tools regardless of the stylesheet. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. |
Supported |
SyberWorks 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. |
Supported |
SyberWorks does not use client-side image maps. |
| (g) Row and column headers shall be identified for data tables. |
Supported |
SyberWorks equips data tables with row and column headers and use clear markup to associate data cells with 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. |
Supported |
Pages containing data tables can still be read effectively and successfully using Freedom Scientific Corporation Assistive technology tools, the JAWS for Windows screen reader, etc. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation |
Frames titling within accessible content is being addressed in future releases. |
|
| (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 |
SyberWorks's online learning Web site pages do not contain flashing or blinking text, objects, or other elements having a flash or blink. |
| (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 |
Applicable Web pages have been made accessible; therefore there is no need for text only versions of the site 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. |
Not Applicable |
|
| (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 |
Our accessible courses were designed to not require the use of applets or plug-ins. |
| (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 |
On applicable pages, directive keywords were added to form fields. This allows people using Freedom Scientific Assistive Technology tools to access the information and complete the form. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. |
Supported |
SyberWorks has implemented an invisible link containing an alternative text tag in the header, which allows users to skip repetitive navigation |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Not Applicable |
SyberWorks does not require timed responses for the majority of pages on the Web site. |
| Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4. |
| Section 1194.31 Information, Documentation, and Support |
| Section 508 Criteria |
SyberWorks Supporting Features |
SyberWorks 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. |
Supported |
|
| (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. |
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 |
Supported |
|
| (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 |
|
| (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 |
|
| (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. |
Supported |
|
| Section 1194.41 Information, Documentation, and Support |
| Section 508 Criteria |
SyberWorks Supporting Features |
SyberWorks Remarks and Explanations |
| (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. |
Supported |
Documentation is provided in digital format and is accessible. |
| (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. |
Supported |
Documentation is provided in digital format and is accessible. |
| (c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supported |
Documentation is provided in digital format and is accessible. |
