Skip to main content

Edugator

Accessibility Statement

Last Updated August 16, 2026 · Version 1.1

Edugator ("Edugator", "we", "us") is a web-based platform for computing education. Learning is not optional for the students who use it, so access to it should not be either. This statement describes how accessible Edugator is today, how we test it, where it still falls short, and how to reach support when something blocks you.

Our Commitment

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We treat accessibility as part of building the product, not as a review that happens afterward:

  • Accessibility defects are tracked in the same backlog as other defects, and blocking defects are prioritized above feature work.
  • We publish an updated Accessibility Conformance Report (VPAT) as the platform changes, and we do not describe a criterion as supported until it has been tested.
  • Where a feature cannot yet be made accessible, we provide an equally effective alternative on request rather than asking the person to work around it.

Conformance Status

Edugator partially conforms to WCAG 2.1 Level AA. "Partially conforms" means that parts of the platform do not fully meet the standard. Every criterion, including the ones we do not yet meet, is listed with its result in the full Accessibility Conformance Report:

Download the Edugator Accessibility Conformance Report (VPAT® 2.5Rev) — Microsoft Word (.docx), approximately 3 MB.

The report covers Edugator v1.0.140 and is dated 16 August 2026, revising the original report of 31 March 2026 after a round of remediation and re-testing. WCAG 2.0 and 2.1 Level A and AA were evaluated. WCAG 2.2-only success criteria were not evaluated and are reported as "Not Evaluated" rather than as passes.

If you need this report in a different format — PDF, HTML, plain text, or a completed copy of your institution's own accessibility questionnaire — email marc@edugator.app and we will provide it.

How We Test

Testing was performed by testers familiar with the product, using a combination of manual and automated methods:

  • Screen reader testing with NVDA (v2025.3.3), checking that headings, links, and buttons are announced correctly, that no content is skipped or invisibly announced, and that content is announced in a logical order.
  • Manual audits of focus order, dynamic content, and keyboard-only navigation.
  • Automated audits with axe DevTools (v4.125.0) and Google Lighthouse (v13.0.3). Text spacing (1.4.12) was checked with an external bookmarklet tool.
  • Platform tested: Google Chrome on Windows and macOS.

Criteria repaired since the March 2026 report were manually re-tested against Edugator v1.0.140 on 16 August 2026, using the same screen reader, focus order, and keyboard-only methods, before their results were changed in the report.

Known scope limit: Edugator has not been evaluated on mobile devices; the workflows and interface are designed for standard screen sizes.

Content Created by Instructors

Much of what students see in Edugator — lesson text, images, uploaded media, and problem statements — is authored by instructors and teaching staff, not by us. Edugator provides the tools to make that content accessible, and course staff are responsible for using them:

  • Add meaningful alt text to every image in a lesson or problem statement.
  • Provide captions for any video you link, and a transcript or audio description where the visuals carry information the audio does not.
  • Avoid conveying meaning through color alone, and avoid animated GIFs that run longer than five seconds.
  • Write descriptive link text rather than "click here", and use headings in order rather than for visual sizing.

If you are an instructor and a student in your course needs content in an alternative format, contact us at support@edugator.app and we can take a look to find a solution.

Report an Accessibility Problem

If any part of Edugator blocks you, tell us — you do not need to identify the WCAG criterion or diagnose the cause.

  • Email: support@edugator.app — put "Accessibility" in the subject line so it is routed correctly.
  • Accessibility contact for institutions, procurement, and conformance questions: Marc Diaz, marc@edugator.app.

It helps us reproduce the problem if you can include:

  1. What you were trying to do and what happened instead.
  2. The page or URL where it happened.
  3. Your browser, operating system, and any assistive technology and version (for example, "Chrome 141 on Windows 11 with NVDA 2025.3").
  4. Whether this blocks you entirely or has a workaround.

What happens next: we aim to acknowledge accessibility reports within 7 business days, and to respond with either a fix, a remediation timeline, or an equally effective alternative within 15 business days. If a report concerns graded work or an exam with a deadline, say so — we treat those as urgent.

If you are a student or employee at a university, you may also contact your institution's disability resource or student accessibility office, which can request accommodations on your behalf. We will work directly with those offices.

Feedback on This Statement

This statement was prepared on 16 August 2026 based on the self-evaluation described above. We review it whenever a new conformance report is published or a significant part of the platform changes. Questions, corrections, or disagreements about anything stated here are welcome at support@edugator.app.