Date: 3/1/2021
Name of Product: Wolfram|Alpha
Contact for More
Information: compliance@wolfram.com
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). | Supports | Wolfram|Alpha relies on the built-in accessibility features of modern markup languages. Where necessary, these are augmented with ARIA (Accessible Rich Internet Applications) attributes. |
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Supports | No such presentations exist. |
(c) Webpages shall be designed so that all information conveyed with color is also available without color, for example, from context or markup. | Supports | Users can access color adjustments provided by their operating system or browser. |
(d) Documents shall be organized so they are readable without requiring an associated stylesheet. | Supports | Documents with static text elements can be accessed by viewing the page source. |
(e) Redundant text links shall be provided for each active region of a server-side image map. | Supports | All textual information in query results, served as images, can be accessed as plain text from a keyboard-accessible footer button. |
(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. | Supports | Not applicable. |
(g) Row and column headers shall be identified for data tables. | Supports where appropriate | Not all rows are labeled, but generally they are distinguished from one another by their first entry. Plain-text versions of table-style query results retain their row and column headers wherever these exist. |
(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. | Data tables are images but are supplemented with plain-text alternatives that can be accessed with other assistive technology as needed. | |
(i) Frames shall be titled with text that facilitates frame identification and navigation. | Supports | All frames have meaningful labels. |
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Supports | Such flickering is avoided. |
(k) 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. | Supports | A text-only page is not necessary. |
(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. | Supports | Screen readers can see and interpret all dynamically generated text content to the best of our knowledge. |
(m) When a webpage 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). | Supports | No such applet, plug-in or other application is needed. |
(n) 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. | Supports | Forms are HTML based, and Wolfram|Alpha relies on the built-in accessibility features of modern markup languages for these forms. Where necessary, these features are augmented with ARIA (Accessible Rich Internet Applications) attributes. |
(o) A method shall be provided that permits users to skip repetitive navigation links. | Does not support | The website currently is not designed to include "skip links." However, repetitive navigation is seldom necessary during day-to-day use of the site. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Supports | Timed responses are not required at any point. |
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.