Accessibility Statement

Effective Date: March 10, 2026 | Last Updated: March 14, 2026

1. Our Commitment to Accessibility

Groupimize LLC is committed to ensuring that our Canvas-integrated instructional tool is accessible to all users, including people with disabilities. We recognize that accessibility is essential in educational technology and are actively working to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

Groupimize is a web-based application accessed through Canvas LTI. We aim to ensure that all students and instructors can effectively use the tool regardless of ability.

2. Current Accessibility Features

Groupimize currently incorporates the following accessibility practices:

2.1 Perceivable

Semantic HTML is used throughout the application, with proper heading hierarchy (h1, h2, h3) for screen reader navigation.
All form inputs include associated labels for screen reader identification.
Text content meets WCAG minimum contrast ratios (4.5:1 for normal text, 3:1 for large text and non-text UI components). Form input borders and focus indicators meet the 3:1 non-text contrast ratio.
The interface does not rely solely on color to convey information.
Page titles are descriptive and unique for each view. Decorative content is hidden from assistive technology using aria-hidden.

2.2 Operable

All interactive elements are accessible via keyboard navigation. Interactive elements previously using <span> have been converted to semantic <button> elements. All core workflows (survey completion, peer review submission, instructor dashboard navigation, group management) are fully keyboard accessible.
The application does not use time limits that would prevent users from completing tasks.
Modal dialogs implement ARIA modal patterns (role="dialog", aria-modal="true", aria-labelledby) with focus traps and Escape-to-close. Focus is restored to the triggering element when modals close.
Skip navigation links allow keyboard users to bypass repetitive navigation. Visible focus indicators (2px solid with box-shadow) are present on all interactive elements. Drag-and-drop student movement in group preview has a keyboard-accessible alternative.
No content flashes at rates that could cause seizures.

2.3 Understandable

The language of each page is identified in the HTML lang attribute.
Form validation provides clear error messages describing what needs to be corrected.
Navigation is consistent across pages.
The interface uses clear, plain language appropriate for an educational context.

2.4 Robust

The application uses valid, standards-compliant HTML with semantic landmarks (<nav>, <main>), proper ARIA roles/states/properties, and role="alert" with aria-live for dynamic error messages and aria-busy for async form submissions.
Content is rendered consistently across modern browsers (Chrome, Firefox, Safari, Edge).
The application is responsive and functions on mobile devices and tablets.

3. Known Limitations and Roadmap

We are transparent about the current state of accessibility. Following a comprehensive WCAG 2.1 AA remediation effort completed in March 2026, the following areas remain identified for improvement:

Self-Assessed VPAT/ACR: A self-assessed Accessibility Conformance Report (ACR) using the ITI VPAT 2.5 template for WCAG 2.1 Level AA was completed in March 2026 through systematic code-level review of all templates, CSS, and JavaScript. A formal third-party accessibility audit to produce an independently verified ACR is planned for Q3 2026.
Third-Party Audit: A formal third-party accessibility audit has not yet been conducted. Chrome Lighthouse audits and systematic code-level review have been completed as interim measures. A third-party audit is planned for Q3 2026.
Pie Chart Visualizations: Pie charts used in the group formation preview are generated as images. We plan to add text-based data tables as alternatives for screen reader users. Target: Q2 2026.
Continued ARIA Enhancement: ARIA roles, states, and properties have been implemented on modals, live regions, error messages, and form submissions. Additional ARIA enhancements for complex interactive components are reviewed and implemented incrementally with each release.
Screen Reader Testing: Formal testing with screen readers (VoiceOver on macOS, NVDA on Windows) is planned for Q3 2026 alongside the third-party audit.

4. Conformance Goal

Groupimize targets conformance with WCAG 2.1 Level AA. A comprehensive self-assessment and remediation was completed in March 2026 covering all application templates. A self-assessed ACR using the ITI VPAT 2.5 template documents current conformance status. A formal third-party audit is planned for Q3 2026 to independently verify conformance.

We are committed to addressing any accessibility barriers identified through testing, user feedback, or institutional review. Our goal is to achieve and maintain substantial conformance with WCAG 2.1 AA standards.

5. Testing Approach

Groupimize accessibility is evaluated through the following methods:

Manual Testing: All core workflows (survey completion, peer review submission, instructor dashboard navigation, group management) are tested with keyboard-only navigation, including focus trap behavior in modals, focus restoration, and skip navigation functionality.
Browser Developer Tools: Chrome Lighthouse accessibility audits are run against key pages to identify common issues.
Semantic Validation: HTML output is reviewed for proper heading structure, label associations, landmark regions, ARIA roles/states/properties, and color contrast compliance (4.5:1 text, 3:1 non-text).

Planned: Formal testing with screen readers (VoiceOver on macOS, NVDA on Windows) and engagement of a third-party accessibility auditor are planned for Q3 2026.

6. Feedback and Issue Reporting

We welcome feedback on the accessibility of Groupimize. If you encounter any accessibility barriers or have suggestions for improvement, please contact us:

Email: support@groupimize.com
Subject Line: Accessibility Feedback

We aim to respond to accessibility feedback within 5 business days and to implement fixes for critical accessibility issues within 30 days.

7. Compatibility

Groupimize is designed to be compatible with:

Modern web browsers: Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge (latest two major versions).
Desktop and mobile devices.
Screen readers and other assistive technologies that support standard web technologies (HTML, CSS, JavaScript).

Groupimize is accessed through Canvas LTI and relies on the institution's Canvas environment for initial authentication. The accessibility of the Canvas LTI launch process is governed by Canvas (Instructure) and the institution's Canvas configuration.

8. Institutional Accommodations

If a student requires accommodations to use Groupimize that go beyond what the application currently supports, we encourage the student to contact their institution's disability services office. Groupimize LLC will work with the institution to provide reasonable accommodations, which may include alternative formats for survey completion or peer review submission.

9. Contact Information

Accessibility Contact: Groupimize LLC
Email: support@groupimize.com
Website: https://groupimize.com