Back to Home

Accessibility

Last updated: August 10, 2026

CourseKeel is built for the people who design and deliver courses — and that includes designers, instructors, and reviewers who use assistive technology. We target WCAG 2.2 Level AA, which encompasses the WCAG 2.1 AA baseline referenced by the ADA Title II web rule and the WCAG 2.0 AA baseline referenced by Section 508.

How accessibility is engineered and tested

We treat accessibility as an engineering requirement with automated enforcement, not a statement of intent:

  • Automated WCAG testing in CI. Every change runs axe-core scans against the public site and the authenticated application — including contrast checks, 320px reflow checks, and our prepared dark-mode color tokens. A change that introduces a detectable WCAG A/AA violation does not ship.
  • Accessibility linting. All interface code is checked with accessibility lint rules (eslint-plugin-jsx-a11y) for keyboard handlers, label associations, and valid ARIA.
  • Keyboard operability. The interface is designed to be operable with a keyboard alone, including keyboard alternatives for drag-and-drop reordering, a skip-to-content link in the application shell, and visible focus indicators.
  • Screen-reader-compatible semantics. The interface uses semantic HTML and established WAI-ARIA patterns, with landmark structure, labeled controls, and announced notifications.
  • Contrast-audited palette. Interface colors have been audited and remediated against WCAG contrast thresholds, and the audit is enforced by the automated scans on an ongoing basis.

Conformance status

We do not publish conformance claims we have not verified. A formal criterion-by-criterion evaluation against all 55 WCAG 2.2 Level A and AA success criteria is in progress: the automated portion is complete and runs continuously in CI; the manual portion — keyboard-only walkthroughs, screen-reader testing, and zoom and reflow verification — is underway.

When the manual evaluation completes, we will publish an Accessibility Conformance Report (VPAT® 2.5) on this page. Procurement teams that need our current in-progress assessment before then can request it through our contact form.

Accessibility of authored content

Course content authored in CourseKeel is exported as semantic HTML, with support for image alt text and accessible math notation. Final accessibility of published content depends on what authors create; CourseKeel sits upstream of LMS-side content checkers such as Canvas Ally, which evaluate content where it is delivered.

Known limitations

The manual evaluation is not yet complete, and we expect it to surface refinements. One known item we are actively addressing: some in-application form errors are not yet announced to screen readers as status messages, though they are always shown in text.

Report a barrier

If you encounter an accessibility barrier in CourseKeel, tell us through our contact form. Please include the page you were on and the browser and assistive technology you were using. Accessibility reports are triaged with the same priority as functional defects.