Skip to main content

ManagedMethods Accessibility Conformance Report - (Content Filter/Classroom Manager)

ManagedMethods Accessibility Conformance Report

WCAG Edition

(Based on VPAT® Version 2.5Rev)

Name of Product:

Content Filter / Classroom Manager

Report Date:

April 27, 2026


Product Description:

ManagedMethods Content Filter (CF) / Classroom Manager (CM) is a web-based application enabling K–12 school administrators to monitor, filter, and manage student activity across Chromebook environments. The application provides dashboards, reporting, device management, group policy controls, content filtering, Google Classroom integration, class session monitoring, and administrative configuration.

Contact Information:


Notes:

This Accessibility Conformance Report (ACR) evaluates ManagedMethods Cloud Filtering against the Web Content Accessibility Guidelines (WCAG) 2.1, Levels A and AA. Level AAA conformance is not claimed and is not required for this product category.

Evaluation was conducted using automated testing (axe-core 4.9.1) across all static and dynamic routes in the application, supplemented by manual DOM inspection, ARIA attribute review, keyboard interaction spot-checks, and color-contrast assessment.

A third-party Intercom live chat widget is embedded on all pages via a cross-origin iframe. That widget is excluded from this evaluation as it is not under ManagedMethods’ direct control; its accessibility is the responsibility of Intercom, Inc.

All WCAG A and AA violations identified during testing have been remediated prior to this report. No outstanding conformance failures remain.


Evaluation Methods Used:

Automated testing: axe-core 4.9.1 (browser-injected via CDN), run against all static and accessible dynamic routes in the application.

Static routes tested (29 total):

  • Summary (/)

  • Devices (/devices), Accounts (/accounts), Groups (/groups)

  • Activities (/activities), Classes (/classes), Scenes (/scenes)

  • Google Classroom (/googleClassroom)

  • Policy: Allow List (/policy/allowList), Block List (/policy/blockList), Risks (/policy/risks), YouTube (/policy/youTube), Schedules (/policy/schedules), Settings (/policy/settings)

  • Scheduled Reports (/scheduledReports)

  • Admin: Settings (/admin/settings), Console Users (/admin/consoleUsers), Console User Activity (/admin/consoleUserActivity), IP Ranges (/admin/ip-ranges)

Dynamic routes tested with live data (7 total):

  • Device Details (/devices/:deviceId)

  • Account Details (/accounts/:accountId)

  • Class Session History (/classes/:educationClassId/history)

  • Class Meet (/meet/:educationClassId)

  • Session Audit (/sessions/:sessionId/audit)

  • Google Course Details (/googleCourseDetails/:courseId)


Manual testing: DOM inspection, ARIA attribute review, keyboard navigation spot-checks, color-contrast assessment, and screen-reader behavior verification performed in Google Chrome on macOS.

Tools: axe-core 4.9.1, Chrome DevTools, browser zoom testing (up to 400%).


Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline

Included In Report

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Level A (Yes)

Level AA (Yes)

Level AAA (No)


Terms

The terms used in the Conformance Level information are defined as follows:

  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.

  • Partially Supports: Some functionality of the product does not meet the criterion.

  • Does Not Support: The majority of product functionality does not meet the criterion.

  • Not Applicable: The criterion is not relevant to the product.

  • Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

WCAG 2.x ReportTable 1: Success Criteria, Level A

Criteria

Conformance Level

Remarks and Explanations

Supports

All meaningful images and SVG chart elements include appropriate alternative text or are marked aria-hidden="true" when decorative. Recharts Pie chart segments are wrapped in a role="img" container with a descriptive aria-label; inner SVG paths are hidden from assistive technology. Icon-only buttons include descriptive aria-label attributes. Ant Design icons use role="img" with aria-label throughout. The .ant-table-measure-row internal measurement row (rendered by Ant Design for column sizing in tables with rowSelection) has its duplicate checkbox patched with tabindex="-1" and aria-hidden="true" to prevent it appearing in the accessibility tree.

Not Applicable

The product does not contain prerecorded audio-only or video-only content.

Not Applicable

The product does not contain prerecorded synchronized media.

Not Applicable

The product does not contain prerecorded video content.

Supports

Page structure is conveyed through semantic HTML. Data tables use <th> elements with scope="col". Form fields are associated with labels via Ant Design Form.Item. ARIA landmarks are present. Previously empty table header cells (on Accounts and Devices pages) have been corrected with descriptive labels. The Ant Design Descriptions component renders label/value pairs in a semantic table structure.

Supports

Content is presented in a logical reading order matching the visual layout. No CSS techniques create a misleading reading sequence.

Supports

Instructions and UI labels do not rely solely on shape, color, size, or spatial position. All interactive controls have text or programmatic labels.

Supports

Color is not the sole means of conveying information. Status indicators combine color with text labels or icons. Chart legends include text labels alongside color indicators.

Not Applicable

The product does not play audio automatically.

2.1.1 Keyboard (Level A)

Supports

All interactive elements are keyboard-accessible. Ant Design components follow standard keyboard patterns. Scrollable table regions include tabindex="0" and role="region". Ant Design Collapse panels on the Meet page use collapsible="icon" for independent operation of header buttons.

Supports

No keyboard traps were observed. Modal dialogs return focus to the triggering element. Focus is not locked within any component.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Not Applicable

The product does not implement single-character key shortcuts.

Not Applicable

The product does not impose time limits on user interactions.

Not Applicable

The product does not contain moving, blinking, or auto-updating content beyond data tables that refresh on user-initiated filter changes.

Supports

The product does not contain content that flashes more than three times per second.

Supports

Repeated navigation blocks can be bypassed via keyboard by tabbing past the persistent sidebar. Shallow navigation depth minimizes the burden.

Supports

Each page has a meaningful <title> element describing the current view.

Supports

Focus order follows logical DOM sequence. Modal focus management is handled by Ant Design’s built-in focus trap.

Supports

Links and buttons have descriptive accessible names conveying purpose in context.

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

Supports

All functionality is operable with single-pointer actions. No multi-point or path-based gestures required.

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

Supports

Click actions triggered on up-event. Accidental activations can be cancelled by moving pointer off element.

2.5.3 Label in Name (Level A 2.1 and 2.2)

Supports

Accessible name contains visible label text. icon-only controls use aria-labels describing visible action.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

Not Applicable

Product does not use device motion or user motion for functionality.

Supports

HTML lang="en" attribute is set on all pages.

3.2.1 On Focus (Level A)

Supports

No context changes occur when receiving focus. State changes triggered by explicit user actions.

3.2.2 On Input (Level A)

Supports

Context changes not triggered automatically on input. Form submissions require explicit action.

3.2.6 Consistent Help (Level A 2.2 only)

Not Applicable

Only applies to WCAG 2.2.

Supports

Form validation errors displayed as inline text adjacent to field via Ant Design rendering.

Supports

All form fields have visible labels. Required fields/formats indicated via label and placeholder text.

3.3.7 Redundant Entry (Level A 2.2 only)

Not Applicable

Only applies to WCAG 2.2.

4.1.1 Parsing (Level A)

WCAG 2.0 and 2.1 – Always answer ‘Supports’

WCAG 2.2 (obsolete and removed) - Does not apply

Supports

For WCAG 2.0 and 2.1, 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.

Supports

All interactive components have ARIA roles/names. Switches include aria-label attributes. icon-only buttons have descriptive labels. State changes conveyed via ARIA.


Table 2: Success Criteria, Level AA

Criteria

Conformance Level

Remarks and Explanations

Not Applicable

The product does not contain live audio content.

Not Applicable

The product does not contain prerecorded video with audio.

1.3.4 Orientation (Level AA 2.1 and 2.2)

Supports

Content does not restrict display to a single orientation. Renders in both portrait and landscape.

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

Supports

Fields collecting personal info use appropriate autocomplete attributes where applicable.

Supports

Primary text and UI elements meet 4.5:1 ratio. Descriptions component label color updated to pass (7.0:1).

Supports

Text can be resized up to 200% without loss of content. Uses relative units and responsive layout.

Supports

Product does not use images of text. Content rendered as live DOM text.

1.4.10 Reflow (Level AA 2.1 and 2.2)

Supports

Content reflows at 320px width without horizontal scrolling for primary content. Data table regions are keyboard-scrollable.

1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

Supports

UI component boundaries meet 3:1 contrast ratio. Chart elements use distinct colors with adequate contrast.

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

Supports

No loss of functionality occurs when overriding text spacing to WCAG specified values.

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

Supports

Tooltip content is dismissible, hoverable, and persistent.

Supports

Direct access to major sections from consistent sidebar navigation.

Supports

Form fields have descriptive labels. Section headings use <h2>-<h3> within content.

Supports

Visible focus indicators on all interactive elements via Ant Design and browser defaults.

Not Applicable

Only applies to WCAG 2.2.

2.5.7 Dragging Movements (Level AA 2.2 only)

Not Applicable

Only applies to WCAG 2.2.

2.5.8 Target Size (Minimum) (Level AA 2.2 only)

Not Applicable

Only applies to WCAG 2.2.

Supports

English-only application. Content matches page lang attribute.

Supports

Navigation presented consistently. Sidebar order and location persist throughout.

Supports

Components with same function identified consistently (search, pagination, filters).

Supports

Form validation provides descriptive error messages with specific correction guidance.

Supports

Significant actions use confirmation dialogs. Users can review and cancel before submission.

Not Applicable

Only applies to WCAG 2.2.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Supports

Success, error, and loading status messages announced via ARIA live regions.


Table 3: Success Criteria, Level AAA

Criteria

Conformance Level

Remarks and Explanations

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

1.3.6 Identify Purpose (Level AAA 2.1 and 2.2)

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

2.2.3 No Timing (Level AAA)

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

2.2.6 Timeouts (Level AAA 2.1 and 2.2)

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

2.3.3 Animation from Interactions (Level AAA 2.1 and 2.2)

Not Applicable

Not Evaluated

2.4.8 Location (Level AAA)

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

2.4.13 Focus Appearance (Level AAA 2.2 only)

Not Applicable

Not Evaluated

2.5.5 Target Size (Level AAA 2.1 and 2.2)

Not Applicable

Not Evaluated

2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2)

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

3.3.5 Help (Level AAA)

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated

Not Applicable

Not Evaluated


Known Limitations and Third-Party Exclusions

Intercom chat widget: An Intercom live chat widget is embedded on all pages via a cross-origin <iframe>. This widget is not under ManagedMethods’ control and is excluded from this evaluation. Intercom publishes its own accessibility conformance information.

Ant Design library internals: Two patterns in the Ant Design component library produce incomplete axe-core flags that do not represent real accessibility barriers:

  • The .ant-picker-separator span (date range picker arrow) uses aria-label="to" on a plain <span>. This is an Ant Design internal implementation and does not create an assistive technology barrier.

  • The rc-menu overflow item uses aria-controls referencing a popup menu that exists in the DOM but may be hidden at audit time. Manual verification confirms the referenced element exists and the control functions correctly.

Ant Design split-table header pattern: Ant Design’s scrollable table implementation renders the header and body as separate <table> elements for sticky header support. axe-core flags this as th-has-data-cells (incomplete, needs manual review). Manual inspection confirms column alignment is correct and data relationships are conveyed through consistent column ordering. No assistive technology barrier was identified.


Legal Disclaimer

This document is provided for informational purposes only. The information represents ManagedMethods’ good-faith assessment of the product’s accessibility conformance as of the report date. Accessibility is an ongoing effort and this report will be updated as the product evolves. ManagedMethods makes no warranties, express or implied, regarding the completeness or accuracy of this report.

VPAT® is a registered trademark of the Information Technology Industry Council (ITI). This report was prepared using the VPAT 2.5Rev WCAG template published by ITI in April 2025.

Did this answer your question?