The challenge
The EDU site is often the first impression for future physicians, scientists, and health professionals, but it wasn’t meeting WCAG 2.1 accessibility standards. Issues like [low color contrast, inconsistent heading structure, missing alt text, and keyboard navigation gaps] made it harder for people using assistive technology. For a public academic medical center, that’s both a compliance risk and a contradiction of the institution’s values.
How research shaped this
I combined automated scans with manual keyboard and screen reader testing to see the site the way assistive-technology users do. Tools flagged 10 (AA) visual design issues, but manual testing revealed problems no scanner catches, such as confusing focus order and unclear text. That shaped what I fixed first.
Process
Audit: I documented every violation with annotated screenshots and grouped them by WCAG criterion.
Prioritize: I ranked issues by severity and how many pages they affected, fixing systemic problems in shared components first.

Design fixes: I updated the color palette for contrast, rebuilt the heading hierarchy, and designed visible focus states and accessible component patterns.

Partner with Engineering and QA: I worked with developers to build the fixes and with QA to verify them against WCAG criteria.

Prevent regressions: I created an accessibility checklist for content editors so new pages stay compliant.
Solution
The redesigned EDU site meets WCAG 2.1 AA while keeping the UT Southwestern look and feel. Fixes were built into shared components, so every page that uses them benefits automatically.
Results
The accessibility score rose from D+ to B, 1,000+ violations were resolved, and over 10,000k pages were remediated.
Results
Accessibility works best as part of the system, not page-by-page cleanup. Fixing components instead of individual pages made compliance easier to sustain, and it changed how the team thinks about accessibility from the start of every project.

You may also like

↑Back to Top