ACR Index Accessibility Conformance Reports for software

Top Hat - Instructor Web/Browser Application and Content Authoring Suite

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 Partially Supports Most non-text content has text alternatives or a text alternative that serves an equivalent purpose. The following exceptions exist: ● Some images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs in the following component: Header and following pages: Screens Advancing through Presentation; Add & Invite Students To Your Course Modal; Create a Discussion Modal; Create Account; Add to Course Menu - Question Modal; Signup; Image Attachment and following pages: Content Tree - Questions; File Submission Question Modal; Add to course Menu - Sorting Question. ● An image has a text alternative that is different from what the image represents, so people who are blind and/or use a screen reader will be given different information than sighted
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 Does Not Support Most, if not all, information, structure, and relationships conveyed through presentation cannot be programmatically determined or are not available in text. The following issues exist: ● Some text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs in the following components: Sub header; Header; Grading Options; Left nav and following pages: Content - Private; Content Tree - Questions; Question Start Screen; Gradebook Main Grid; Add & Invite Students To Your Course Modal; Content Preview - Folder; Long Answer Question Modal; Fill in the Blank Question Modal; Gradebook Content - Page; Graded Discussion Report; Content Creation - Empty State; Create Account; Course Layout; File Submission Question Modal; Matching Question Modal; Chemistry; Signup; Create
1.3.2 Meaningful Sequence A Partially Supports The reading and navigation order of most content is logical and intuitive. The following exceptions exist: ● The screen reader skips and does not announce informative static content (text or images), so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs in the following component: Header and following pages: Content Tree - Questions; Students; Add to course Menu - Sorting Question; Add to Course Menu - Question Modal; Signup; File Submission Question Modal. ● Screen reader focus is lost or misplaced due to user interaction or content update, making navigation difficult or impossible for people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Gradebook Main Grid - Open Group. ● The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs in the following component: Question Description filed and toolbar and following pages: Content Creation - Empty State; Content Preview - Folder; Graded Discussion Report; Folder Preview Action: Rename.
1.3.3 Sensory Characteristics A Supports Instructions to operate and/or understand content do not rely on sensory characteristics of components such as shape, color, size, and visual location.
1.4.1 Use of Color A Partially Supports For most content, color is not used as the only method to convey information, indicate an action, prompt a response, or distinguish visual elements. The following exceptions exist: ● Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of some controls, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following pages: Create Question Editor; Attendance Report. ● Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify the link. This occurs on the following pages: Organic Course - Timers; Add to Course Menu - Question Modal; Create Account; Gradebook Main Grid; Create Question Editor.
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 Partially Supports On most pages, all 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, some may conflict with existing browser and screen reader shortcuts, and some functionality based on custom gestures may not be available when a screen reader is turned on. The following exceptions exist: ● Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs in the following components: Course Content Panel(Tree view section); Sub header and following pages: Students; File Submission Question Modal; Gradebook Main Grid; Add to course Menu - Create Page; Create Question Editor; Content - Landing Page; Add to Course Menu - Question Modal; Organic Course - General Settings; Course Layout. ● The content in a scrollable region cannot be accessed using a keyboard, so people who use a keyboard to navigate will not be able to view this content. This occurs in the following component: Course Content Panel(Tree view section) and following page: Exporting Grades & Responses Modal.
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 Partially Supports In most cases, when a time limit exists, the user is given an option to turn off, adjust, or extend the time limit. The following exception exists: ● Some content visually appears and disappears with no ability to adjust how long the content is visible, potentially preventing people who are blind, have low vision, or have mobility or cognitive disabilities from locating or reading the content. This occurs on the following pages: Advance Settings; Generate AI Question; Create Custom Role Modal; Content Preview - Question and Discussion.
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 Partially Supports Most pages have descriptive and informative titles. The following exception exists: ● The page's programmatic title does not identify the purpose of the page, so people who use a screen reader will not know the purpose of the page without reading its content. This occurs on the following pages: Organic Course - People & Roles; Chemistry; Create Account; Content - Landing Page; Attendance Report; Content Tree - Questions; Organic Course - Timers; Question Report; Organic Course - Grading; Personal information; Organic Course - General Settings; Folder Preview Action: Rename; Change Password; Gradebook Content - Page.
2.4.3 Focus Order A Partially Supports The navigation order of most interactive elements (such as links, buttons, or form elements) is logical and preserves meaning and operability. The following exceptions exist: ● Keyboard focus is lost or misplaced as a result of user interaction or content update, or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs on the following pages: Gradebook Main Grid - Open Group; Graded Discussion Report; Generate AI Question; Word Question Modal; Matching Question Modal; Multiple Choice Question Modal; Fill in the Blank Question Modal.
2.4.4 Link Purpose (In Context) A Partially Supports The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. The following exception exists: ● Multiple links have identical link text but different destinations, and the context provided by the content that immediately surrounds each link does not provide any clarification, so people who are blind and/or use a screen reader will not know or may be confused about where each link goes. This occurs on the following pages: Assign Flyout; Multiple Choice Question Modal; Word Question Modal.
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:
2.5.3 Label in Name A Partially Supports For most user interface components that include visible text labels, the accessible name matches (or includes) the visible text in the label. The following exceptions exist: ● Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: Course Layout; Fill in the Blank Question Modal; Matching Question Modal; Sorting Question Modal; Create a Discussion Modal. ● The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs in the following components: Image Attachment; Question
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 Partially Supports In most cases, 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. The following exception exists: ● When an element receives keyboard focus, focus is automatically removed or redirected, so people who use a keyboard to navigate content (including screen reader users) may become confused or disoriented. This occurs
3.2.2 On Input A Partially Supports In most cases, 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, or the user is informed about the change ahead of time. The following exception exists: ● When a user changes the setting of a user interface control (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disoriented. This occurs on the following page: Add to Course Menu - Question Modal.
3.3.1 Error Identification A Partially Supports For most 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. The following exception exists: ● Some form fields with an error are not identified in the text error message or a text alternative for an image, and the error message with the field name is not programmatically associated with the form field (so it is announced when a screen reader user navigates to the field), so people who are blind and/or use a screen reader will not be able to identify in which form field an error occurred.
3.3.2 Labels or Instructions A Partially Supports For most 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. The following exceptions exist: ● The labels for some form fields are missing, so each field's purpose is not clear. This occurs on the following pages: Select Student Modal; Attendance Report; Create Question Editor. ● The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following page: Chat Widget. ● A group of elements is missing a visible group label, so the purpose of the elements in the group cannot be understood. This occurs on the following page: Add to course Menu - Create Page. ● Select or dropdown control missing a visible label. People who are blind cannot use the visual presentation of a form to determine the label for a form element.
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 exceptions exist: ● An element that appears and functions like a set of tabs with their associated tab panels does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the element's name, purpose, content, structure, or current state or how to interact with the tabs and their associated content. This occurs on the following page: Create Question Editor. ● An iframe does not have a programmatic title that is conveyed to assistive technology, so
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 Partially Supports The purpose of most input fields that collect an individual's personal data is programmatically defined based on the WCAG list of Input Purposes for User Interface Components. The following exception exists: ● No programmatic purpose is provided for some input elements (like text input fields), so browsers or assistive technology are not able to automatically suggest information to fill in the inputs. This occurs on the following pages: Change Password; Create Account.
1.4.3 Contrast (Minimum) AA Partially Supports Most text and images of regular text have the required color contrast ratio with their backgrounds. The following exceptions exist: ● The color contrast ratio between text and its background is less than 4.5:1 (or less than 3:1 for large text), so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: Gradebook Main Grid; Chemistry; LMS Sync Modal.
1.4.4 Resize text AA Partially Supports Most content is readable and functional when browser zoom is set to 200% of its initial size. The following exceptions exist: ● Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs in the following component: Sub header and following pages: Content Tree - Questions; Content - Landing Page; Gradebook Main Grid - Open Group;
1.4.5 Images of Text AA Partially Supports On most pages, when content can be presented visually using only text, an image of text is not used to present that text. The following exception exists: ● Text on the page is text embedded in an image instead of actual text. An image of text is difficult to zoom or otherwise modify, so people who have low vision and need to enlarge text to read it may not be able to read the text. People with other disabilities that need to otherwise modify text to read it also may not
1.4.10 Reflow AA Does Not Support The content of most, if not all, pages is not viewable without scrolling horizontally when the viewport is set to 320 CSS pixels wide. The following issues exist: ● When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs in the following component: Course Content Panel(Tree view section) and following pages: Select Student Modal; Multiple Choice Question Modal; Create Question Editor; Present Mode Launch Screen; Take Attendance Modal; Add to course Menu - Slide Upload; Create a Discussion Modal; Content Preview - Folder; Folder Preview Action: Rename; Add Manual Entry Flyout and Grade Tab; Word Question Modal. ● When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs in the
1.4.11 Non-text Contrast AA Partially 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. The following exceptions exist: ● The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs on the following pages: Students; Question Report; Create a
1.4.12 Text Spacing AA Partially Supports For most content, the spacing between letters, words, lines of text, and paragraphs can be adjusted with no loss of content or functionality. The following exceptions exist: ● When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: LMS Sync Modal; Create Custom Role Modal; Take Attendance Modal. ● When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some or all of the content cannot be read because it overlaps with other content. This occurs on the following pages: Students; Content Preview - Folder.
1.4.13 Content on Hover or Focus AA Partially Supports In most cases, 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. The following exceptions exist: ● Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs in the following components: Question Description filed and toolbar; Image Attachment and following pages: Word Question Modal; Gradebook Main Grid; Assign Flyout; Create Custom Role Modal; Create Question Editor. ● Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs on the following pages: Create Question Editor; Create Custom Role Modal.
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 Partially Supports Most headings and labels for form and interactive controls are informative. The following exceptions exist:
2.4.7 Focus Visible AA Partially Supports In most cases, it is visually apparent which page element is currently receiving keyboard focus. The following exception exists: ● Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs in the following component: Calendar widget and following pages: Add Manual Entry Flyout and Grade Tab; Create Question Editor.
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 and accessible manner before the data is submitted to the server.
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
4.1.3 Status Messages AA Partially Supports In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. The following exception exists: ● Some status messages are not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status messages, or they may not hear them in a timely fashion. This occurs in the following components: Question Description filed and toolbar; Grading Options; Course Content Panel(Tree view section) and following pages: Multiple Choice Question Modal; Content Tree - Questions; Generate AI Question; Content Preview - Question and Discussion; Sorting Question Modal; Gradebook Content - Page; Fill in the Blank Question Modal; Matching Question Modal; Attendance Report; Take Attendance Modal; File Submission Question Modal; Organic Course - General Settings; Content Preview - Folder; Add to Course Menu - Question Modal; Personal information; Question Report; Students; Organic Course - Timers; Assign Flyout; Folder Preview Action: Rename; Create a Discussion Modal; Word Question Modal; Add & Invite Students To Your Course

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.