CampusCredit's WCAG 2.1 AA Accessibility Report, Explained
CampusCredit's accessibility report rates the platform against WCAG 2.1 AA and Section 508. How we tested, what the results show, and where to read the VPAT.

Colleges reviewing software for student-facing work now ask about accessibility early, often before the first demo. Here is CampusCredit's answer in one place: what we tested, what the results show, and where to read the full report.
What we published
CampusCredit has an Accessibility Conformance Report (ACR), written on the industry-standard VPAT 2.4 template from the Information Technology Industry Council. It evaluates the platform against WCAG 2.1 Level A and Level AA, and against Section 508 of the Rehabilitation Act. The report is dated April 12, 2026, and you can open it here or from the VPAT link at the bottom of any page on this site.
New to the format? Our earlier post explains what a VPAT is and why institutions ask for one, and the W3C's WCAG overview covers the standard itself.
Why WCAG 2.1 AA matters for public colleges
WCAG 2.1 AA is no longer only a best practice. The U.S. Department of Justice's ADA Title II rule on web and mobile accessibility adopts WCAG 2.1 AA as the technical standard for state and local governments, and it names public schools, community colleges and public universities among them. After an April 2026 extension, the compliance dates are April 26, 2027 for public entities serving 50,000 people or more, and April 26, 2028 for smaller ones. The rule covers content a public college provides through vendors too, which is why procurement teams ask for a VPAT.
How we tested
We tested the way people use the platform, not only with automated scanners:
- Keyboard-only navigation, with no mouse
- Hands-on testing in Google Chrome throughout development
- Screen readers: NVDA with Firefox, and VoiceOver with Safari
- Automated checks with Axe DevTools and Google Lighthouse
What the results show
Every criterion in the report is rated Supports or Not Applicable, with two exceptions rated Partially Supports. That includes the Section 508 sections for software, documentation and support services.
We would rather name the two exceptions than round them up:
- 2.1.1 Keyboard. In two administrator forms, Add New Student and Edit Articulation, the submit button can be reached by keyboard, but it takes extra Tab presses to get there.
- 1.3.5 Identify Input Purpose. Articulation ID lookup fields need autocomplete attributes, which tell browsers and assistive technology what a field is for.
The report schedules fixes for both in the third quarter of 2026.
What this means for your institution
Most colleges look for alignment with WCAG 2.1 AA when they review a vendor. With CampusCredit:
- Your review has a standard document to work from. The report follows the VPAT 2.4 format, so your accessibility or procurement team can check it criterion by criterion against WCAG 2.1 AA and Section 508.
- Nothing is hidden. The two partial items are named, with the screens they affect and when the fixes were scheduled.
- It sits alongside the rest of your review. Accessibility is usually one part of a vendor review. Our FERPA page covers student data privacy, and accreditation compliance shows the audit trail reviewers look for.
- Questions go to people. If your reviewers want to talk through a criterion, our support team is a short email away.
Common questions
Does CampusCredit meet WCAG 2.1 AA?
The report rates every WCAG 2.1 A and AA criterion as Supports or Not Applicable, except 2.1.1 Keyboard and 1.3.5 Identify Input Purpose, which are rated Partially Supports. The full report has the detail for each one.
Does the report cover Section 508?
Yes. It includes the Section 508 chapters for software, support documentation and support services.
Who should I contact about the report?
Email support@mycampuscredit.com. If you are evaluating CampusCredit for a community college or district, you can also contact our team.
Read the full report
Open the CampusCredit Accessibility Conformance Report. To see what the platform does, start with the CampusCredit platform.
Access to college credit should open doors, not add barriers. Accessibility is part of how we build that access.



