Pilot kit for universities
A 12-week accessibility pilot, next to your LMS
This kit is what we bring to the first conversation with a university. It sets out a 12-week plan with owners and success metrics, the technical checklist your IT team will ask about, the documents we provide for review, and what we ask of your institution. Nothing here is aspirational: every item is either live today or marked as in progress.
Suggested pilot scope
- One department or unit runs the seed course "Digital accessibility for faculty" as mandatory training with completion reporting.
- One accessible non-credit program (existing or new) is published on your branded Eduspera subdomain with SSO for campus accounts.
- Disability Services co-designs two features with us and validates the player with students who use assistive technology.
Timeline
The 12-week plan
Six phases of two weeks. Each phase has a named owner on both sides and a metric we can actually read from the platform at the end of the pilot.
| Weeks | Activities | Owner | Metric |
|---|---|---|---|
| Weeks 1–2 | Kickoff, pilot charter, success metrics agreed. Choose the department and the 50–200 learners. Security and legal documents shared for review (ACR, HECVAT Lite, DPA). | Eduspera pilot lead + institution sponsor | Charter signed; document review started |
| Weeks 3–4 | Technical setup: SAML SSO with your IdP, branded subdomain or custom domain, email sender, org units and roles, seed course imported and localised to your policies. | Institution IdP admin + Eduspera engineering | SSO login works for a test group; course published internally |
| Weeks 5–6 | Faculty cohort launched as mandatory training with a due date. Weekly nudges. Office hours with the accessibility office for questions on real course material. | Department lead + accessibility office | Enrolment ≥ 90% of the cohort; first completions |
| Weeks 7–8 | Non-credit program or co-design track: publish one accessible program, or run two feedback sessions with students who use assistive technology, prioritised with Disability Services. | Disability Services + Eduspera product | Program live, or two co-design sessions completed with logged findings |
| Weeks 9–10 | Measurement: completion report per department, reading-aid adoption, accessibility complaints log, learner satisfaction survey (5 questions, anonymous). | Eduspera pilot lead + institution sponsor | All four pilot metrics reported |
| Weeks 11–12 | Review with stakeholders, findings and remediation list, decision on continuation, data export or handover, and a written case study if the institution agrees. | Both sponsors | Go / no-go decision and next-step plan |
Success metrics
How we know the pilot worked
Four metrics, agreed in week 1, all readable from the platform or from a short survey. We report them exactly as measured, including when a target is missed.
Completion rate
Share of assigned learners who complete the course by the due date, reported per department from the mandatory-training dashboard. Target: 80% or more.
Zero accessibility complaints
No accessibility barrier reported by learners or by Disability Services that is caused by the platform. Content issues are logged and remediated within the pilot.
Reading-aid adoption
Share of learners who use at least one aid (read-aloud, captions, alternative formats, text and spacing adjustments). Reported from anonymised usage, never per person.
Learner satisfaction
Anonymous five-question survey at the end of the course. Target: an average of 4 out of 5 or better, with free-text answers shared in full in the review.
Technical checklist
What your IT team will ask about
The items your identity, network and data teams will want to confirm before a single learner signs in. Status reflects what is live today.
- Single sign-on (SAML 2.0, InCommon)
- Your IdP (Shibboleth, Entra ID, Okta, Google Workspace) is connected by email domain with just-in-time provisioning. InCommon metadata is supported. A test group signs in before the cohort.
- Status: Live
- Domain
- A branded subdomain (yourname.eduspera.com) is immediate; a custom domain such as learn.youruniversity.edu needs one CNAME record and is issued a certificate automatically.
- Status: Live
- Email sender
- Course emails can be sent from an institutional address after SPF and DKIM records are added, so notifications do not land in spam. Until then they are sent from an Eduspera address.
- Status: Live
- LTI 1.3 (optional)
- Launching a course from Canvas with grade passback is built on contract for institutional deployments. It is not required for the pilot: learners sign in with SSO and are linked from Canvas.
- Status: On contract
- Data export
- A full tenant export (courses, learners, enrolments, progress, certificates) and per-learner personal data export are available to your administrators at any time, including at the end of the pilot.
- Status: Live
Documents
What we provide
Accessibility Conformance Report (ACR)
WCAG 2.2 AA, EN 301 549 and Section 508. Self-assessed today; an independent third-party audit is in progress and the report will be updated with its findings.
HECVAT Lite
The higher-education security questionnaire, completed and available under NDA. A public summary of the answers is on our Trust Center.
Data processing agreement with FERPA clause
GDPR Article 28 DPA including a FERPA "school official" clause for student records, sub-processor list and EU Standard Contractual Clauses.
Security one-pager
Hosting, encryption, tenant isolation, backups, incident response and access controls on one page for your security reviewer.
Seed course and pilot support
The course "Digital accessibility for faculty" (6 modules, about 2.5 hours, quizzes and certificate) ready to adapt, plus a named pilot lead and weekly check-ins.
Your side
What the institution provides
A department
One school, department or unit with a sponsor who can make the training mandatory and attend the review.
50–200 learners
Faculty and staff for the training cohort, or learners for the non-credit program. Large enough to measure, small enough to support well.
An accessibility office contact
Someone from Disability Services or the digital accessibility office who can co-design, review content and route any complaint.
An IdP administrator
A person who can configure the SAML connection and confirm the metadata, typically two hours of work in weeks 3–4.
Related pages
Start a pilot
Bring this kit to your next accessibility meeting
Tell us the department, the rough number of learners and when you would like to start. We reply within one business day with a proposed charter.