ACR Index Accessibility Conformance Reports for software

Top Hat - Student Web/Browser Application

Accessibility Conformance Report published by Top Hat

Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% coverage). The remainder are missing from our extraction, not necessarily from Top Hat's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.

Conformance by level

Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.

Source: View the original report published by Top Hat.

These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.

All reported criteria (50)

Conformance as stated by Top Hat in its published report.
CriterionNameLevel ConformanceRemarks from vendor
1.1.1 Non-text Content A Supports Most non-text content has text alternatives or a text alternative that serves an equivalent purpose. The following exception exists: ● Top Hat allows uploading of slides or images, and provides alt-text for images and transcript generation. ● If an image is not given a text alternative, people who are blind and/or use a screen reader will not be able to access the information in the image. If it is an active image they may not understand its function. This occurs on: Content, Slides.
1.2.1 Audio-only and Video-only (Prerecorded) A Not Applicable Prerecorded audio-only files are not present.
1.2.2 Captions (Prerecorded) A Not Applicable Prerecorded videos are not present.
1.2.3 Audio Description or Media Alternative (Prerecorded) A Not Applicable Prerecorded videos are not present, so the audio description is not required.
1.3.1 Info and Relationships A Supports Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
1.3.2 Meaningful Sequence A Supports The reading and navigation order is logical and intuitive.
1.3.3 Sensory Characteristics A Partially Supports On most pages, instructions to operate and/or understand content do not rely on sensory characteristics of components such as shape, color, size, and visual location. The following exception exists: Content, Question: Click on Target ● Click on Target is a question type requiring the upload of an image — its operation requires the ability to see shape, color, size, visual location, or orientation, so it will be difficult to understand for people who are blind or have low vision.
1.4.1 Use of Color A Supports Color is not used as the only method to convey information, indicate an action, prompt a response, or distinguish visual elements.
1.4.2 Audio Control A Supports A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays for more than 3 seconds.
2.1.1 Keyboard A Supports Functionality is available using only the keyboard (unless that functionality cannot be accomplished in any known way using a keyboard). If shortcut keys and access keys are present, they do not conflict with existing browser and screen reader shortcuts, and functionality based on custom gestures is available when a screen reader is turned on.
2.1.2 No Keyboard Trap A Supports Keyboard focus is never locked or trapped in a particular area, and the user can navigate to and from all navigable elements using only a keyboard.
2.1.4 Character Key Shortcuts A Supports If a single-character key shortcut exists, then the single-character key shortcut can be turned off or remapped, or it is only active when the relevant user interface component is in focus.
2.2.1 Timing Adjustable A Supports If a time limit exists, the user is given options to turn off, adjust, or extend that time limit.
2.2.2 Pause, Stop, Hide A Supports Moving, blinking, scrolling, or auto-updating information can be paused, stopped, hidden, or otherwise controlled by the user.
2.3.1 Three Flashes or Below Threshold A Not Applicable The tested application does not contain flashing content.
2.4.1 Bypass Blocks A Supports A method is provided to skip navigation and other page elements that are repeated across web pages.
2.4.2 Page Titled A Supports Pages have descriptive and informative titles.
2.4.3 Focus Order A Supports The navigation order of interactive elements (such as links, buttons, or form elements) is logical and preserves meaning and operability.
2.4.4 Link Purpose (In Context) A Supports The purpose of each link can be determined from the link text alone or from the link text and its programmatic context.
2.5.1 Pointer Gestures A Supports All functionality that can be operated with a pointer can be operated with single-point actions.
2.5.2 Pointer Cancellation A Supports For functionality that can be operated using a single pointer, at least one of the following is true: ● The action is not triggered on the down event. ● The action triggers on the up event, and a mechanism is available to abort the function before completion or to undo the function after completion. ● The up-event reverses any outcome of the preceding down-event. ● Completing the function on the down-event is essential.
2.5.3 Label in Name A Supports For each user interface component that includes a visible text label, the accessible name matches (or includes) the visible text in the label.
2.5.4 Motion Actuation A Supports Functionality that can be triggered by device motion or user motion detected by a device can be disabled, and the functionality can be operated without using motion.
3.1.1 Language of Page A Supports The language of each page is correct and can be determined programmatically.
3.2.1 On Focus A Supports When an element receives focus, a change in context (such as a substantial change to the page, the spawning of a pop-up window, or a change in focus) that may disorient the user does not occur.
3.2.2 On Input A Supports When a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user unless the user is informed about the change ahead of time.
3.3.1 Error Identification A Supports For form controls where an input error is automatically detected, a text message or alert is provided that identifies the field/control where the error was detected and describes the error.
3.3.2 Labels or Instructions A Supports For form controls/input fields requiring user input, labels, instructions, and/or error messages are provided to identify the controls/input fields in the form so that users know what input data is expected.
4.1.1 Parsing A Supports For WCAG 2.0 and 2.1 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. This criterion was removed from WCAG 2.2.
4.1.2 Name, Role, Value A Partially Supports The name, role, state, and/or value of most user interface components can be programmatically determined. The following exception exists: Content, Question: Click on Target ● Setting a target on an image (such as "dropping" or "deleting") is not conveyable to screen readers and other assistive technologies. Due to the inherent visual nature of this assessment, it can not be available to people who use those technologies. ● “Assign” and alternative format workarounds exist in Top Hat, but this limitation needs to be made clear.
1.2.4 Captions (Live) AA Not Applicable Live multimedia files with audio are not present, so synchronized captions are not required.
1.2.5 Audio Description (Prerecorded) AA Not Applicable Prerecorded multimedia files are not present, so audio descriptions are not required.
1.3.4 Orientation AA Supports Orientation of the content is not locked to either landscape or portrait unless a specific orientation is essential for the functionality.
1.3.5 Identify Input Purpose AA Supports The purpose for each input field that collects an individual's personal data is programmatically defined based on the WCAG list of Input Purposes for User Interface Components.
1.4.3 Contrast (Minimum) AA Supports Text and images of regular text have the required color contrast ratio with their backgrounds.
1.4.4 Resize text AA Supports Content is readable and functional when browser zoom is set to 200% of its initial size.
1.4.5 Images of Text AA Supports When content can be presented visually using only text, an image of text is not used to present that text.
1.4.10 Reflow AA Supports The content of most pages is viewable without scrolling horizontally when the viewport is set to 320 CSS pixels wide.
1.4.11 Non-text Contrast AA Supports Most of the boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content have a 3:1 color contrast ratio with adjacent color(s) or their background.
1.4.12 Text Spacing AA Supports The spacing between letters, words, lines of text, and paragraphs can be adjusted with no loss of content or functionality.
1.4.13 Content on Hover or Focus AA Supports When additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it.
2.4.5 Multiple Ways AA Supports Multiple ways are available to find other pages on the site.
2.4.6 Headings and Labels AA Supports Most headings and labels for form and interactive controls are informative.
2.4.7 Focus Visible AA Supports It is visually apparent which page element is currently receiving keyboard focus.
3.1.2 Language of Parts AA Supports The language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically.
3.2.3 Consistent Navigation AA Supports Navigation patterns that are repeated on web pages are presented in the same relative order each time they appear and do not change order when navigating through the site.
3.2.4 Consistent Identification AA Supports Labels, names, and/or text alternatives for content that have the same functionality across multiple web pages are consistently identified.
3.3.3 Error Suggestion AA Supports If input errors are automatically detected, suggestions are provided in text for correcting the input in a timely
3.3.4 Error Prevention (Legal, Financial, Data) AA Supports If the user can change or delete legal transactions, financial transactions, student exam responses, or data transactions that are unrecoverable or unintentionally modify or delete data, the changes and/or deletions are reversible, verified, or confirmed.
4.1.3 Status Messages AA Supports Status messages can be programmatically determined and presented by assistive technologies without receiving focus.

Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.

Get told when this changes

This report is dated April 23, 2026. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.

Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.