Web Accessibility Audit Report

University of Arizona Accessibility Website

Executive Summary

Estimated Remediation Effort: Medium (2-3 days)

Key Strengths

• Skip navigation link present
• Clear heading structure with H2-H3 hierarchy
• Contact information readily available
• Semantic HTML elements used appropriately
• Comprehensive content organization

Critical Concerns

• Multiple H1 elements on single page
• Redundant links throughout card components
• Ambiguous link text without sufficient context
• Logo alt text includes visual styling information

Critical Issues

<!-- Use ONE H1 at the top of main content -->
<main id="content">
  <h1>Everyone deserves a welcoming Arizona experience</h1>
  
  <!-- All subsequent major sections should use H2 -->
  <section>
    <h2>News</h2>
    <!-- content -->
  </section>
  
  <section>
    <h2>You can start in two ways</h2>
    <!-- content -->
  </section>
</main>

<!-- Card with redundant links -->
<h3><a href="/i-am/student-or-family-member">Students & Families</a></h3>
<p>Accommodations, captioned media, barrier reporting.</p>
<a href="/i-am/student-or-family-member">Student guide</a>

<!-- Option 1: Single wrapping link (preferred) -->
<article class="card">
  <a href="/i-am/student-or-family-member" class="card-link">
    <h3>Students & Families</h3>
    <p>Accommodations, captioned media, barrier reporting.</p>
    <span class="cta" aria-hidden="true">Student guide →</span>
  </a>
</article>

<!-- Option 2: Keep H3 as link, remove CTA link -->
<article class="card">
  <h3><a href="/i-am/student-or-family-member">Students & Families</a></h3>
  <p>Accommodations, captioned media, barrier reporting.</p>
  <!-- Remove the second link entirely -->
</article>

Major Issues

<!-- Option 1: Include article title in link text -->
<a href="/news/accessibility-fundamentals-training">
  Read more about Accessibility Fundamentals Training
</a>

<!-- Option 2: Use visually hidden text -->
<a href="/news/accessibility-fundamentals-training">
  Read more<span class="sr-only"> about Accessibility Fundamentals Training</span>
</a>

<!-- Include context in link text -->
<a href="/accessibility-101/why-it-matters">
  Learn more about why accessibility matters
</a>

<!-- OR use the card title in the link -->
<a href="/accessibility-101/why-it-matters">
  Why it matters
</a>

<img src="logo.png" alt="The University of Arizona Wordmark Line Logo White">

<!-- Remove color reference -->
<img src="logo.png" alt="The University of Arizona">

<!-- OR if linking to homepage -->
<a href="https://www.arizona.edu/">
  <img src="logo.png" alt="University of Arizona homepage">
</a>

<a href="/tools-checklists/experience-accessibility-simulations">
  Try accessibility simulations
</a>

Moderate Issues

Minor Issues

What Passed

Remediation Roadmap

Phase 1: Critical Fixes (Week 1)

Effort: 8-16 hours | Impact: High

1. Fix H1 duplication (2 hours)
   • Debug template rendering issue
   • Ensure only one H1 per page
   • Test across all page templates
2. Refactor card components (4-6 hours)
   • Update card component template
   • Convert to single wrapping link or remove CTA link
   • Test keyboard navigation
   • Deploy and verify across all pages using cards

Phase 2: Major Fixes (Week 2)

Effort: 8-12 hours | Impact: Medium-High

3. Update all ambiguous link text (4-6 hours)
   • Replace "Read more" with descriptive text
   • Replace "Learn more" with context
   • Update CTA button text
   • Create content guidelines
4. Fix logo alt text (1 hour)
5. Verify and fix "I am a" dropdown (2-3 hours)
6. Add external link warnings (2 hours)

Phase 3: Moderate Fixes (Week 3)

Effort: 4-8 hours | Impact: Medium

• Verify and enhance skip link
• Verify HTML lang and viewport meta
• Test and fix focus indicators
• Verify color contrast
• Make feedback banner dismissible
• Audit search form

Phase 4: Minor Enhancements (Week 4)

Effort: 2-4 hours | Impact: Low

• Minor link text improvements
• External link indicators
• Documentation and guidelines

Recommended Testing Setup

Automated Testing

1. Install axe DevTools browser extension: https://www.deque.com/axe/devtools/
2. Run Lighthouse in Chrome DevTools (Accessibility audit)
3. Set up Lighthouse CI for continuous monitoring

Manual Testing Checklist

• Test keyboard navigation (Tab, Shift+Tab, Enter, Escape)
• Verify skip link visibility on focus
• Test "I am a" dropdown with keyboard only
• Test search form with screen reader
• Navigate entire page using screen reader + keyboard
• Test at 200% browser zoom
• Verify focus indicators on all interactive elements
• Check color contrast ratios
• Test with high contrast mode

Screen Reader Testing

Test Scenarios

• Navigate by headings (H key in NVDA)
• Open links list (Insert+F7 in NVDA)
• Navigate by landmarks (D key in NVDA)
• Use "I am a" dropdown with screen reader only

Next Steps

Additional Resources

WCAG 2.2 Resources

• WCAG 2.2 Quick Reference
• Understanding WCAG 2.2

Testing Tools

• axe DevTools
• WAVE
• Color Contrast Checker

Screen Readers

• NVDA (Windows) - Free
• JAWS (Windows)
• VoiceOver (Mac/iOS) - Built-in (Cmd+F5)

Learning Resources

• WebAIM
• Deque University
• The A11y Project
• W3C WAI Tutorials

End of Report
Generated: March 4, 2026 | Auditor: Web Accessibility Wizard | Version: 1.0