LEGAL INFORMATION
Wolfram System Modeler® Section 508 Voluntary Product Accessibility Template
Date: 6/29/22
Name of Product: Wolfram System Modeler for Windows, Mac and Linux: Version 13.1
Contact for More
Information: compliance@wolfram.com
| Criteria | Supporting Features | Remarks and Explanations |
| Section 1194.21 Software Applications and Operating Systems | Supports with Exceptions | See Below |
| Section 1194.22 Web-Based Internet Information and Applications | Not Applicable | |
| Section 1194.23 Telecommunications Products | Not Applicable | |
| Section 1194.24 Video and Multimedia 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 | Supports with Exceptions | See Below |
| Section 1194.41 Information, Documentation, and Support | Supports | See Below |
| 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. | Supports | All functionality of System Modeler can be accessed from the keyboard with the exception of drag-and-drop components; however, equivalent functionality is accessible through the keyboard for these elements via the Modelica code editor and keyboard shortcuts. The menu is fully accessible through menu accelerators. Keyboard shortcuts are given in the product documentation, linked from: http://reference.wolfram.com/system-modeler/UserGuide/ModelCenterKeyboardShortcuts.html http://reference.wolfram.com/system-modeler/UserGuide/SimulationCenterKeyboardShortcuts.html |
| (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 | No such disruptions occur. |
| (c) A well-defined onscreen 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 | The caret/selection is only fully painted in the focused window. The product provides operating system support for focused appearance on title bars of windows and keyboard support for focus switching. |
| (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 | All user interface elements are textual or have tooltips. Most UI elements are implemented using standard library components, which should include full accessibility support. Custom widgets likely do not provide such information; these include: plot windows, splash screen, kernel busy screen and 3D animations. |
| (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 | VCR-style bitmaps appear consistently. Other bitmaps in the standard installation are unique to an individual control, status indicator or programmatic element. User-defined libraries may contain arbitrary bitmaps to represent programmatic elements. It is up to users to ensure unique bitmap usage within their libraries. Also, users may include third-party libraries that may contain non-unique bitmaps. |
| (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 with Exceptions | Text is drawn with appropriate attributes by operating system calls, and the caret location is tracked by the operating system. Although drawn through standard operating system calls, full textual information inside of UI components and custom widgets might not be programmatically exposed due to development environment limitations. |
| (g) Applications shall not override user-selected contrast and color selections and other individual display attributes. | Supports | The software offers full support for the operating system's color scheme or theme. The user may explicitly set some colors in the application, including background, text color and syntax highlighting. These program-specific attributes are retained from session to session. |
| (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 | All information-carrying
animations are under full user control and may be slowed down or paused. There is a non-information-carrying animation that is displayed when Simulation Center is opening that is not user controllable, however, it is accompanied by a clear textual indication that Simulation Center is opening. |
| (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 | No interface elements of System Modeler rely solely on color. Shading is used to increase the convenience of identifying parameters that have been changed from their default value inside Simulation Center, but the particular color of the shading is not important for this functionality. |
| (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 | User-selectable colors are fully customizable. |
| (k) Software shall not use objects, flashing or blinking text or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. | Supports | No flashing or blinking elements are present in System Modeler. Real-time graph updates may flicker if the update frequency is too high, but the update frequency is fully customizable. It is up to users to ensure that their models are compliant with this criteria. |
| (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 | Such forms have limited support for Assistive Technology. |
| 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. | Supports with Exceptions | Text uses standard output mechanism, and all functionality of System Modeler can be accessed through the Modelica scripting interface and keyboard shortcuts. However, at this time, System Modeler does not fully support direct operation using Assistive Technology. Extensive import/export support of multiple data formats and native integration with Mathematica might allow a user to create a functional workaround. |
| (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 | The product offers built-in magnification of graphical areas as well as text areas. Drag-and-drop library elements can be enlarged. |
| (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 | No functionality relies on sound. |
| (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 | No functionality relies on sound. |
| (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 | No functionality requires user speech. |
| (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 | Those people with fine motor control problems should be helped by our built-in magnification, which magnifies all graphic and text areas. It does not magnify other UI elements, but those are fully keyboard navigable and can be accessed through the Modelica scripting capabilities or can be enlarged through other means that will make them easier to interact with coarsely. |
| 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 | The online version of the documentation is available at our website: http://reference.wolfram.com/system-modeler |
| (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 | Product documentation includes: Keyboard shortcuts: http://reference.wolfram.com/system-modeler/UserGuide/ModelCenterKeyboardShortcuts.html http://reference.wolfram.com/system-modeler/UserGuide/SimulationCenterKeyboardShortcuts.html Kernel commands: http://reference.wolfram.com/system-modeler/UserGuide/ModelCenterKernelCommands.html |
| (c) Support services for products shall accommodate the communication needs of end users with disabilities. | Supports | Support is available via email. |
Wolfram takes privacy and data protection seriously, and is committed to safeguarding data you share with us. To learn more, please see our Privacy Policy.
Return to the top of the page.