Skip to main content
Applies to Gradebot v3.4 · Last Reviewed Jun 16, 2026

Accessibility Statement

Wave AI Solutions, Inc. is committed to making Gradebot™ accessible to everyone, including people with disabilities. We treat accessibility as a core part of how we design, build, and test the product — not an afterthought.

Report a Barrier

WCAG 2.2 Level AA

Gradebot™ substantially conforms to WCAG 2.2 Level AA, documented in our Accessibility Conformance Report (VPAT/ACR), available to institutions on request.

Keyboard-First

Every feature can be operated with a keyboard alone, with a logical focus order, a clear visible focus indicator, and no keyboard traps.

Screen-Reader Tested

You can navigate Gradebot™ with a screen reader; dynamic updates are announced without moving your focus, and text meets contrast minimums.

1. Our Commitment

Wave AI Solutions, Inc. is committed to making Gradebot™ accessible to everyone, including people with disabilities. We treat accessibility as a core part of how we design, build, and test the product — not an afterthought — so that instructors, teaching assistants, and administrators can do their work regardless of how they navigate the web.

This statement applies to the Gradebot™ web application at gradebot.ai (release v3.4) and was last reviewed on June 16, 2026.

2. Conformance Status

WCAG 2.2 Level AA — Substantial Conformance

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities, at three levels: A, AA, and AAA.

Gradebot™ substantially conforms to WCAG 2.2 Level AA. This means the substantial majority of the applicable Level A and Level AA success criteria are met, with a small number of areas noted under Known Limitations below. This assessment is based on our own detailed, criterion-by-criterion review (a vendor self-assessment), documented in our Accessibility Conformance Report (ACR / VPAT 2.5Rev), which we provide to institutions on request. It is not yet an independent third-party audit; commissioning one is a planned step (see How We Assess Accessibility).

In plain terms: you can operate Gradebot™'s features with a keyboard alone, navigate with a screen reader, see a clear focus indicator wherever you are on the page, and read text and controls that meet contrast minimums.

3. Measures We Take to Support Accessibility

Accessibility is part of our process — it is considered during design and code review and tracked through our internal Accessibility Program and Accessibility Roadmap.

Built on accessible foundations

Semantic HTML, ARIA landmarks, and a "Skip to main content" link so keyboard and screen-reader users can bypass navigation.

Keyboard-first

All interactive features are operable by keyboard, with a logical focus order and a clear, consistently visible focus indicator.

Announced changes

Dynamic updates (such as grading progress and upload confirmations) use ARIA status roles so assistive technologies announce them without moving the user's focus.

Readable by design

Text and interface controls are reviewed against WCAG AA contrast minimums.

Tested with assistive technology

Including manual keyboard navigation and manual screen-reader testing.

4. What We Improved in Release v3.4

Our v3.4 release completed and shipped a focused round of accessibility remediation. The following are now fully supported:

Full keyboard operability — every feature can be used with a keyboard, and there are no keyboard traps (WCAG 2.1.1, 2.1.2).
Visible focus — a consistent focus indicator shows keyboard users where they are (WCAG 2.4.7), and focused elements are not hidden behind sticky headers or overlays (WCAG 2.4.11).
Color contrast — a control that previously fell just below the minimum was recolored to comfortably exceed it (WCAG 1.4.3).
Keyboard shortcuts — a setting now lets users turn off single-key shortcuts that can interfere with screen readers and speech input (WCAG 2.1.4).

5. Technical Specifications

Gradebot™'s accessibility relies on the following technologies working with your browser and any assistive technologies:

  • HTML
  • CSS
  • JavaScript
  • WAI-ARIA

These technologies are relied upon for conformance with WCAG 2.2 Level AA.

6. Compatibility with Your Environment

Gradebot™ is designed to work with current versions of major browsers — Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari — together with common assistive technologies, including screen readers. Accessibility may be reduced on significantly older browsers or assistive-technology versions.

7. How We Assess Accessibility

Wave AI Solutions assessed Gradebot™ using a combination of:

  • Manual evaluation — keyboard-only navigation and manual screen-reader testing;
  • Code review against the WCAG 2.2 Level AA success criteria; and
  • Automated tooling (axe-core-class checks).

This is a self-evaluation. An independent third-party accessibility evaluation is a planned item on our Accessibility Roadmap; until it is completed, we do not represent Gradebot™'s conformance as independently audited.

8. Known Limitations

Despite our efforts, some limitations may remain. We work to identify and fix issues as they arise; please tell us if you encounter one (see Feedback & Contact below).

AI-generated feedback text

Grading scores and feedback are produced from instructor rubrics and student work. Gradebot™ is responsible for the accessibility of the interface that presents this content; the wording of generated feedback itself is not author-controlled.

Continuously evolving product

As we ship new features, an occasional component may temporarily fall short of our standard; such issues are tracked and remediated through our Accessibility Program.

9. Applicable Standards and Laws

This statement and our conformance target reference:

  • WCAG 2.2 Level AA (W3C Recommendation) — our primary standard. WCAG 2.2 AA is a superset of WCAG 2.1 AA and WCAG 2.0 AA.
  • Section 508 of the Rehabilitation Act (Revised 508 Standards) and EN 301 549, which incorporate WCAG.
  • ADA Title II and Title III, under which covered institutions have web-accessibility obligations.

10. Preparation of This Statement

This statement was prepared on June 16, 2026, following the structure recommended by the W3C Web Accessibility Initiative (WAI). It is based on our own evaluation of Gradebot™ v3.4 (see How We Assess Accessibility). We review this statement, and the supporting Accessibility Conformance Report, at least annually and upon any material change to the Gradebot™ interface.

11. Feedback & Contact

We welcome your feedback on the accessibility of Gradebot™, and we want to hear from you if you encounter a barrier or need information in an alternative format. We aim to acknowledge accessibility feedback within two business days and will work with you on a resolution.

If you are not satisfied with our response, you may ask for the matter to be escalated to the Wave AI Solutions accessibility owner for review.

Additional Resources

Institutions may request our current Accessibility Conformance Report (VPAT/ACR) through the same contacts.