Colleges and universities · Section 508 testing
Registration that works for every student, from the first day.
A public university campus was replacing its class registration system. Its accessibility office asked us to test the new system before the first registration window opened, so every student could sign up for classes on time.
- Client
- A public university campus
- Type
- Section 508 testing
- Scope
- 4 student tasks, 22 screens
- Result
- 19 barriers fixed before registration
Context and goals
Students use the system to search for classes, build a schedule, join a waitlist, and pay fees. Many of them do it on a phone.
The campus buys software to Section 508 and WCAG 2.2 AA, and needed results it could hand to the vendor.
What success looks like
- A student can register for classes with a keyboard, a screen reader, or zoom, on a phone or a computer.
- Search results and schedule changes are announced as they happen.
- The vendor gets a clear list of what to fix.
What we measured
A DHS Certified Trusted Tester tested 4 student tasks across 22 screens by hand, on a computer and a phone, with a keyboard, two screen readers, and zoom.
Barriers found in each task
- Build a schedule8
- Join a waitlist5
- Search for classes3
- Pay fees3
All 19 were fixed and retested before registration opened.
| Barrier | Task | Severity | Status |
|---|---|---|---|
| Schedule changes not announced | Build a schedule | High | Fixed |
| Weekly grid unreadable by screen readers | Build a schedule | High | Fixed |
| Small waitlist buttons on phones | Join a waitlist | Medium | Fixed |
| Overlapping text at 200% zoom | Pay fees | Medium | Fixed |
| Filter buttons with no names | Search for classes | Medium | Fixed |
What we found
- The good news: class search and payment worked well with a keyboard and a screen reader.
- Adding a class changed the schedule without telling screen reader users that anything had changed.
- The weekly schedule grid could not be read with a screen reader.
- Waitlist buttons on a phone were too small to tap reliably.
- Text overlapped at 200% zoom on the fee summary.
Hear the difference
A student who uses a screen reader adds a class to their schedule.
Before
What a screen reader says
- “Add, button.”
- Nothing else. The class is added, but the student can’t tell that it worked.
After
What a screen reader says
- “Add, button.”
- “Biology 101 added. Your schedule has 4 classes and 13 units.”
The path to good
- We gave the campus and the vendor 19 issues, each with the requirement, the screen, the severity, and how to fix it.
- We suggested a list view of the weekly schedule, which helps every student on a phone.
- We retested each fix as the vendor released it.
Follow-up
All 19 barriers were fixed before the first registration window opened. The campus kept the report with its purchase records, and asks for a retest with every major update.
All case studies are samples. Each is based on our past work or on our audits of publicly available websites, documents, and social media. Names and details have been changed to protect privacy.
Before you buy
We start with a free light audit.
We prepare it for you and send you what we find.
- We check your homepageKeyboard, screen reader, contrast, and zoom.
- We review one public documentTags, headings, image descriptions, and language.
- We fix one public document freeYou get it back fixed, with a before and after.
- We send you what we findA short written summary you can share with your team.