Authoring tool
Criteria | Conformance level | Passed? | Criteria description | Notes |
WCAG 2.1 | ||||
Perceivable | ||||
Text alternatives | ||||
Level A | Yes | non-text content that is presented to the user has a text alternative that serves the equivalent purpose | Alternative texts are used to provide descriptions for images (HTML alt attribute) and aria labels are provided as descriptions for other graphical controls. decorative images are given an empty alt text so that they are ignored by assistive technologies. Any control which is visually represented by an icon has an aria-label with a textual description | |
Time-based Media | ||||
Level A | N/A | For prerecorded audio and video, there exist alternative methods to visualize the content. | No prerecorded media is used in this application. | |
Level A | N/A | Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | There is no need to provide captions because there is no prerecorded media being used. | |
Level A | N/A | An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | There is no video content in this app. | |
Level AA | N/A | Captions are provided for all live audio content in synchronized media. | The application does not contain any live audio. | |
Level AA | N/A | Audio description is provided for all prerecorded video content in synchronized media. | No prerecorded video is available in this application. | |
Adaptable | ||||
Level A | Yes | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | Grouping roles are used to identify related form controls with fieldset and legend HTML elements. Regions, tables and landmarks are not necessary for this application since it is small and relies mostly on the system focus. Form controls have correctly associated labels using either aria labels or <label> tags. | |
Level A | Yes | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | The content is correctly positioned on the DOM to ensure proper focus order and screen reader interaction, and CSS does not change the visual order of the content. Focus order is determined by HTML positioning alone. | |
Level A | Yes | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. NOTE For requirements related to color, refer to | Enough information is provided so as not to rely on a specific sensory characteristic. | |
Level AA | Yes | Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. | The orientation does not depend on the application, but on Google Docs. | |
Level AA | Yes | The purpose of each input field collecting information about the user can be programmatically determined when: • The input field serves a purpose identified in the Input Purposes for User Interface Components section; and • The content is implemented using technologies with support for identifying the expected meaning for form input data. | All inputs have correct labels associated with them. | |
Distinguishable | ||||
Level A | Yes | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Any information which uses color for highlighting can also be identified via other means. visual content which relies on color has other cues which make it easily distinguishable. | |
Level A | N/A | If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. | There is no audio in this application. | |
Level AA | No | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. • Logotypes: Text that is part of a logo or brand name has no contrast requirement. | Contrast requirements are not met by the alerts used for licensing and OLE conversion. All other controls use CSS to to ensure an adequate contrast ratio between the background and the text and icons. | |
Level AA | Yes | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | Partial support. The user can resize the text if necessary using the dialog controls, accessible via mouse input. No text is clipped or obscured if it is resized. However, the sidebar is small and on some screens it might not be possible to resize to 200%. | |
Level AA | Yes | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: • Customizable: The image of text can be visually customized to the user's requirements; • Essential: A particular presentation of text is essential to the information being conveyed. NOTE Logotypes (text that is part of a logo or brand name) are considered essential. | CSS is used to control the visual presentation. All images have accompanying text or have text alternatives. Logos are properly described, including the trial version logo, which has its own alternative text. | |
Level AA | Yes | Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: • Vertical scrolling content at a width equivalent to 320 CSS pixels; • Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning. NOTE Note: 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px at 400% zoom. NOTE Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content. | CSS reflow is applied using flexbox, width, max width... to fit labels and inputs; the size and position are calculated according the text size. | |
Level AA | Yes | The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): • User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; • Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. | Icons, images of texts and background have a contrast of at least 3:1. We can use tools like Lighthouse, which include a color contrast checker, to check that these requirements are met. | |
Level AA | Yes | In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: • Line height (line spacing) to at least 1.5 times the font size; • Spacing following paragraphs to at least 2 times the font size; • Letter spacing (tracking) to at least 0.12 times the font size; • Word spacing to at least 0.16 times the font size. Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script. | Partial support. Text can be spaced without wrapping and the text spacing can be changed by the user if necessary. However, some screens might be too small to display all the text appropriately if it is resized. | |
Level AA | Yes | Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: • Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; • Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; • Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author. NOTE Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute. NOTE Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion. | This aplication does not use this type of content except for the PowerPoint equation editor, which has an alternative accessible view for screen readers for the first time user badge. | |
Operable | ||||
Keyboard Accessible | ||||
Level A | Yes | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. NOTE This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. | The application uses HTML forms, links and focusable elements. Elements which are not typically focusable have been provided with the tabindex attribute. | |
Level A | Yes | If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. | User can dismiss all dialog windows and modals without difficulty and using the keyboard by pressing the escape key or by closing the dialog with the mouse or Alt F4. | |
Level A | N/A | If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: • Turn off: A mechanism is available to turn the shortcut off; • Remap: A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc); • Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus. | No single letter shortcuts are used. all other shortcuts (including ctrl + alt + letters) are given by the host application. | |
Enough time | ||||
Level A | N/A | For each time limit that is set by the content, at least one of the following is true: • Turn off: The user is allowed to turn off the time limit before encountering it; or • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or • Essential Exception: The time limit is essential and extending it would invalidate the activity; or • 20 Hour Exception: The time limit is longer than 20 hours. NOTE This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with | No time limits are used in the application. | |
Level A | N/A | For moving, blinking, scrolling, or auto-updating information, all of the following are true: • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. | No media or moving info is used. | |
Seizures and Physical Reactions | ||||
Level A | N/A | Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. | Content in this application does not flash. | |
Navigable | ||||
Level A | Yes | A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | This app does not require any regions, headings or landmarks to separate text. However, expandable and collapsible menus are used when necessary and they have the correct accessibility aria-expanded attribute. | |
Level A | N/A | Web pages have titles that describe topic or purpose. | The html attribute in the MathType editor does not have a title. However, host applications provide their own window name for the MathType window. This window is properly named. | |
Level A | Yes | If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. | DOM elements are placed in the order they are presented. Where this is not possible, the tabindex attribute is used to give it the correct focus order. When additional elements are inserted into the DOM, they are inserted at the proper place in the DOM and never at the bottom, which would impact focus and screen reader reliability. | |
Level A | Yes | The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. | The text of all links keep the context correctly. | |
Level AA | N/A | More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. | Since our web application has a simple enough flow and is not a complex webpage, there is no need to support this as the simplicity of MathType only requires a few actions. | |
Level AA | Yes | Headings and labels describe topic or purpose. | No headings are necessary in this application. Descriptive labels are always provided. | |
Level AA | Yes | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | Every component shows the focus when it receives it via the keyboard, and it is highly visible. The MathType editor tabs do not show the focus when they are focused via the keyboard. | |
Input Modalities | ||||
2.5.1 Pointer Gestures (for content) | Level A | Yes | All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. NOTE This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology). | Every component uses standard controls and no path or multipoint gestures are necessary. |
Level A | Yes | For functionality that can be operated using a single pointer, at least one of the following is true: • No Down-Event: The down-event of the pointer is not used to execute any part of the function; • Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; • Up Reversal: The up-event reverses any outcome of the preceding down-event; • Essential: Completing the function on the down-event is essential. NOTE Functions that emulate a keyboard or numeric keypad key press are considered essential. NOTE This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology). | This app does not use drag and drop. events are triggered when touch is removed, not started, except for handwriting mode, which is optional. | |
Level A | Yes | For user interface components with labels that include text or images of text, the name contains the text that is presented visually. NOTE A best practice is to have the text of the label at the start of the name. | Every component which includes an icon has a matching accessibility label, and the visible text matches and is included in the accessibility label. | |
Level A | N/A | Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: • Supported Interface: The motion is used to operate functionality through an accessibility supported interface; • Essential: The motion is essential for the function and doing so would invalidate the activity. | The application doesn't read any motion sensors. | |
Understandable | ||||
Readable | ||||
Level A | No | The default human language of each Web page can be programmatically determined. | The language should be specified in the HTML lang attribute and match the localization if the language is changed. | |
Level AA | N/A | The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. | The language of the page stays consistent throughout the app. | |
Predictable | ||||
Level A | Yes | When any user interface component receives focus, it does not initiate a change of context. | Focus change alone (with focus method) does not modify the page. Changes of context occur on activate() or click(). | |
Level A | Yes | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. | A common accessibility problem with this criteria are dropdowns which automatically trigger events when they are changed such as country dropdowns which reload the page. Dropdowns and edit fields in this app must be submitted before any changes occur. | |
Level AA | Yes | Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. | The application is not complex enough to present a navigation bar; whenever navigational links are presented they are always in the same order. | |
Level AA | Yes | Components that have the same functionality within a set of Web pages are identified consistently. | Components stay the same through their lifecycle and they do not change, except for becomming dimmed when content is being loaded. | |
Input Assistance | ||||
Level A | Yes | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. | In our input fields, the user is notified if an error exists and this error has proper screen reader live region attributes. | |
Level A | Yes | Labels or instructions are provided when content requires user input. | All input fields have their associated label and they are distinguishable from each other. <label> tags are used to associate labels with their corresponding controls. | |
Level AA | Yes | Every field has suggestions in case of errors, except for our product key introduction field which, due to the nature of this field, cannot have suggestions. | Only one input field exists in the app, the product key introduction field. Due to the nature of this content, suggestions cannot be provided. | |
Level AA | N/A | For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: • Reversible: Submissions are reversible. • Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. • Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | No legal information is submitted by the user through the application. Any information submitted via the application is obtained via third-party login mechanisms and is stored privately in a database. | |
Robust | ||||
Compatible | ||||
4.1.1 Parsing (for markup content) | Level A | Yes | In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. NOTE Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete. | The application properly uses HTML according to the current specifications. |
Level A | Yes | For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. NOTE This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. | All components have the correct name, role, value and state and follow the correct ARIA specifications. all divs and spans have a proper aria-role when they are interactible. All changes in non text content, such as aria-labels, are correctly updated when the visual information changes. Links which only contain images have an accessible alternative text, such as the fancy notification gifs. | |
Level AA | No | In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. | Important messages use role="alert" or live regions to be announced by screen readers. | |