Skip to main content

Accessibility Conformance Report (VPAT)

This is Manage1to1's Voluntary Product Accessibility Template (VPAT® 2.5, Section 508 edition). It records how the product conforms to WCAG 2.1 Level AA and the Revised Section 508 standards. It is a living record: we maintain it alongside the product and refresh it each release, and we write it honestly — criteria that are not yet fully met are marked Partially Supports with a plain explanation, rather than overstated.

If you need this report for a procurement review, or you would like to report an accessibility barrier, email info@manage1to1.com with "Accessibility" in the subject.

Product and evaluation

Product / VersionManage1to1 — 2026.08 release line
Report date2026-08-24
Applies toThe staff Admin console and the family-facing Parent/User Portal (sign-in and invoice payment).
StandardsWCAG 2.1 Level A and AA; Revised Section 508 (2017), 36 CFR 1194.

How we evaluated: automated accessibility testing with an industry-standard engine (axe-core, WCAG 2.0/2.1 A and AA rules) against signed-in Admin and Portal pages; manual keyboard-only operation and page-structure (landmark and heading) inspection; visual review in both light and dark themes; and a review of the accessibility information exposed to assistive technology — accessible names, roles, landmarks, and heading structure — across the representative pages (dashboard, device list, incident list, warehouse, and the public Parent Portal).

Terms

  • Supports — the product meets the criterion with at least one method and no known defects, or meets it with equivalent facilitation.
  • Partially Supports — some of the product does not meet the criterion.
  • Does Not Support — the majority of the product does not meet the criterion.
  • Not Applicable — the criterion is not relevant to the product.

WCAG 2.1 Report

Level A and AA success criteria, evaluated against the 2026.08 release line.

Table 1 — Level A

CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text ContentPartially SupportsMeaningful images carry alternative text and decorative icons are hidden from assistive technology. Icon-only controls in the standard action-button component, the dashboard widgets, and the warehouse and device-management screens expose accessible names. A small number of icon-only controls on lower-traffic pages do not yet have an accessible name.
1.2.1–1.2.3 Time-based MediaNot ApplicableThe product does not present prerecorded audio-only, video-only, or synchronized media as core functionality.
1.3.1 Info and RelationshipsPartially SupportsPage landmarks (banner, primary navigation, main content, and footer) are present on every Admin and Portal page; forms use programmatic labels; alerts are announced as alerts; tabbed interfaces use the standard tab pattern and lists use list semantics. A small number of lower-traffic pages are not yet fully covered.
1.3.2 Meaningful SequenceSupportsThe reading order matches the visual order across the shell and page content.
1.3.3 Sensory CharacteristicsSupportsInstructions do not rely solely on shape, size, or location.
1.4.1 Use of ColorPartially SupportsStatus is generally conveyed by text or icon in addition to color. A small number of signals still rely on color alone.
2.1.1 KeyboardPartially SupportsThe application shell — navigation, header, forms, standard buttons and links, and the shared dialog — is keyboard-operable, and a "Skip to main content" link is provided. The header menus open and close from the keyboard, and dialogs move focus to their first control when opened. A few custom widgets are not yet fully keyboard-operable.
2.1.2 No Keyboard TrapSupportsNo keyboard traps were identified in the shell or standard dialogs.
2.1.4 Character Key ShortcutsNot ApplicableNo single-character key shortcuts are implemented.
2.4.1 Bypass BlocksSupportsA visible-on-focus "Skip to main content" link is present on all Admin and Portal pages.
2.4.2 Page TitledSupportsEvery page sets a descriptive title.
2.4.3 Focus OrderSupportsFocus order follows a logical, meaningful sequence in the shell and standard forms.
2.4.4 Link Purpose (In Context)Partially SupportsMost links have descriptive text. A small number of icon-only links on lower-traffic pages do not yet have an accessible name (see 1.1.1).
3.1.1 Language of PageSupportsThe page language is set on all pages.
3.2.1 On Focus / 3.2.2 On InputSupportsNo unexpected context changes occur on focus or input.
3.3.1 Error IdentificationSupportsForm validation identifies errors in text; the shared alert component announces them.
3.3.2 Labels or InstructionsSupportsInputs have visible labels or programmatic labels.
4.1.1 ParsingSupportsMarkup is well-formed, with no duplicate identifiers or nesting errors flagged in scans of the shell.
4.1.2 Name, Role, ValuePartially SupportsStandard components (buttons, alerts, and the shared dialog with proper dialog semantics) expose name, role, and value; header menus and tabbed interfaces expose their roles and state; warehouse and device-management controls carry accessible names. The per-column filter dropdowns on filterable list pages, and the icon-only controls noted in 1.1.1, do not yet have an accessible name.

Table 2 — Level AA

CriteriaConformance LevelRemarks and Explanations
1.4.3 Contrast (Minimum)Partially SupportsShared text, link, badge, header, sidebar, footer, and toolbar colors meet AA in both light and dark themes, including the data-table surfaces used on every list page. The shared primary-button color, and a small number of data-table cells and lower-traffic pages, do not yet meet the minimum contrast ratio.
1.4.4 Resize TextSupportsContent and functionality are preserved at 200% browser zoom.
1.4.5 Images of TextSupportsText is rendered as text, not images.
1.4.10 ReflowPartially SupportsThe shell reflows to a single column on small viewports; wide data tables scroll horizontally within their own container rather than reflowing.
1.4.11 Non-text ContrastPartially SupportsThe keyboard focus indicator meets the non-text contrast threshold. A small number of control borders and icons do not yet meet it.
1.4.12 Text SpacingSupportsNo loss of content occurs with adjusted text spacing.
1.4.13 Content on Hover or FocusPartially SupportsMost hover and focus content is dismissible and persistent; a small number of tooltips and dropdowns do not fully meet the criterion.
2.4.5 Multiple WaysSupportsNavigation plus search provide multiple ways to locate content.
2.4.6 Headings and LabelsSupportsHeadings and labels are descriptive.
2.4.7 Focus VisibleSupportsA global keyboard-focus outline is applied to interactive elements across both the Admin and Portal experiences.
3.2.3 Consistent Navigation / 3.2.4 Consistent IdentificationSupportsNavigation and component identification are consistent across pages.
3.3.3 Error SuggestionSupportsValidation messages suggest corrections where known.
3.3.4 Error Prevention (Legal, Financial, Data)SupportsDestructive and financial actions use confirmation dialogs.
4.1.3 Status MessagesPartially SupportsToast notifications and several dynamic areas announce updates through live regions. A small number of asynchronous status updates on lower-traffic pages are not yet announced.

Revised Section 508 Report

Chapter 3 — Functional Performance Criteria

CriteriaConformance LevelRemarks and Explanations
302.1 Without VisionPartially SupportsLandmarks, labels, and the skip link support screen-reader navigation, and the representative pages expose named landmarks, headings, controls, links, images, and form fields (the public Parent Portal returned no findings). The unlabeled filter dropdowns and the contrast items noted above are the current exceptions.
302.2 With Limited VisionPartially SupportsResize and zoom are supported, and text contrast meets AA in both themes apart from the items noted in 1.4.3.
302.3 Without Perception of ColorPartially SupportsMeaning is generally not conveyed by color alone; a small number of signals still rely on color.
302.4 Without Hearing / 302.5 With Limited HearingNot ApplicableNo audio conveys information.
302.6 Without SpeechNot ApplicableNo speech input is required.
302.7 With Limited Manipulation / 302.8 With Limited Reach and StrengthPartially SupportsKeyboard operation is supported across the shell; a few custom controls are not yet fully keyboard-operable (see 2.1.1).
302.9 With Limited Language, Cognitive, and Learning AbilitiesSupportsConsistent navigation, clear labels, and error suggestions.

Chapter 4 — Hardware

Not Applicable — Manage1to1 is a web application and includes no hardware.

Chapter 5 — Software

CriteriaConformance LevelRemarks and Explanations
501.1 Scope / 502 / 503See WCAG 2.1 ReportThe product is web software; conformance is reported in the WCAG 2.1 tables above.
504.2 Content Creation or EditingSee WCAG 2.1 ReportAuthoring surfaces (forms and editors) conform per the WCAG tables above.

Chapter 6 — Support Documentation and Services

CriteriaConformance LevelRemarks and Explanations
602.2 Accessibility and Compatibility FeaturesSupportsA public accessibility statement is available.
602.3 Electronic Support DocumentationSupportsCustomer documentation is provided as accessible HTML.
603.2 / 603.3 Support ServicesSupportsSupport is reachable by email, and accessibility issues are tracked as product defects.

This report is provided for informational purposes and represents the current state of the product's accessibility as of the report date. It is updated each release as remediation progresses. VPAT® is a registered trademark of the Information Technology Industry Council (ITI).

Related articles

Loading…