Good-Faith Accessibility Remediation Plan
Last updated: August 27, 2026
This plan describes, in the "good-faith effort" terms used by many states' digital accessibility laws and often referenced in the contractor-accountability provisions of school district and state-agency contracts, how Transition Curriculum, Inc. finds, prioritizes, fixes, and verifies accessibility barriers in NextUp, and how we govern that work over time. It complements our Accessibility Statement, which describes the standard we target and what's already in place.
Governance and ownership
- Accessibility work is owned by the NextUp engineering team and sponsored by Chad Logsdon.
- We review this plan and its backlog quarterly, and triage newly reported barriers as they come in.
- Accessibility findings are tracked in the same engineering backlog as other defect work, tagged "accessibility" and prioritized using the severity scale below rather than set aside in a separate, lower-priority queue.
How we find issues
- Independent third-party audit. We completed a comprehensive accessibility audit with Accessible.org within the past year, and we repeat an independent audit on a periodic basis.
- Ongoing automated monitoring. accessiBe, our accessibility widget provider, runs a monthly automated compliance scan of the site; findings feed directly into this backlog.
- Manual testing. Keyboard-only walkthroughs and screen-reader spot checks (NVDA/VoiceOver) of key workflows: sign-in, lesson delivery, assessments, job-portfolio and IEP goal-bank tools, and the admin console.
- Code review. Accessibility is part of our review checklist for new UI: semantic elements, labeled form fields, accessible names for icon-only controls, and focus management in dialogs.
- User feedback. Barriers reported through the channel in our Accessibility Statement feed directly into this backlog.
How findings get resolved
Every issue we identify — whether from our independent Accessible.org audit, accessiBe's monthly automated scan, manual testing, or a user report — is logged in our engineering backlog, assigned one of the severities below, and worked on that timeline. We don't maintain a separate public list of open findings, since that list changes continuously as items are fixed; district customers can request our current audit results and open-issue status directly from their Transition Curriculum account representative.
Severity and timelines
We triage every confirmed accessibility issue into one of three severities:
| Severity | Definition | Target fix time |
|---|---|---|
| Blocking | Prevents a user from completing a core task with assistive technology (e.g. an unlabeled required field, a keyboard trap). | 10 business days from confirmation |
| Serious | Workable, but with significant friction (e.g. a missing landmark, insufficient color contrast). | One release cycle, or 30 days |
| Minor | Cosmetic or an edge case with a reasonable workaround. | Scheduled into the normal backlog, within 90 days |
Plan phases
- Completed: independent accessibility audit with Accessible.org, and monthly automated compliance scanning turned on site-wide through accessiBe.
- Ongoing: triaging and remediating findings from both sources per the severity table above, with accessibility folded into our normal code-review checklist for new UI.
- Upcoming: extending automated accessibility checks into our own continuous-integration test suite as a complement to the external monthly scan, and scheduling our next independent third-party audit.
Third-party verification
Consistent with the contractor-accountability provisions found in many state and district technology contracts, we will cooperate with a qualified third-party accessibility auditor selected by a contracting district or state agency, and we will share that audit's findings and our remediation timeline with the contracting entity.
Reporting a barrier
Report accessibility barriers to NextUp@TransitionCurriculum.com with the subject line "Accessibility." When we confirm an issue, we'll tell you which severity we assigned it and the target timeframe above. See our Accessibility Statement for our acknowledgment commitment.
Document history
- August 27, 2026 — Initial publication.