Outcomes
What students should leave with
- Review interfaces for contrast, semantic structure, and keyboard support.
- Spot fragile patterns in forms, buttons, links, and responsive layouts.
- Create a practical QA checklist for student projects and internal builds.
Reference map
Core topics to cover
Color contrast
Semantic landmarks
Keyboard navigation
Focus states
Form clarity
Error feedback
Responsive QA
Module sequence
ICCT lesson flow
Module 1
Reading an interface critically
Lessons: 2
Teach students to look beyond appearance and assess usability.
Contrast, hierarchy, and readable content
screen comfort, priority, and clarity
Landmarks, headings, and semantic support
screen-reader-friendly structure
Checkpoint lab
Audit a student resource page for contrast, heading flow, and skipped structure issues.
Module 2
Forms and interaction states
Lessons: 2
Focus on where users often get stuck.
Labels, errors, and focus states
clear entry, recovery, and keyboard guidance
Buttons, links, and interactive cues
making actions obvious and dependable
Checkpoint lab
Repair an admissions contact form so it works cleanly with keyboard and screen magnification workflows.
Module 3
Quality review habits
Lessons: 2
Build repeatable checks before release or grading.
Responsive walkthroughs and edge cases
small screens, overflow, and content pressure
Issue logs and remediation handoff
writing actionable feedback for teammates
Checkpoint lab
Produce a pre-launch checklist and issue tracker for a student capstone interface.
Capstone prompts
Projects students can actually ship
Portal Accessibility Audit
Review one internal tool, score its issues, and propose a practical remediation order.
Accessible Form Retrofit
Take an existing form and upgrade labels, errors, focus, and mobile behavior.