🔍 Accessibility Audit Report

axe-core performs automated checks against the Web Content Accessibility Guidelines (WCAG) and other accessibility standards. The tests check for:

• Semantic HTML: Proper use of HTML elements, ARIA attributes, and landmarks
• Keyboard Navigation: All interactive elements must be keyboard accessible
• Color Contrast: Text must meet WCAG contrast ratio requirements (4.5:1 for normal text, 3:1 for large text)
• Focus Management: Visible focus indicators and logical tab order
• Form Labels: All form inputs must have associated labels
• Image Alt Text: Images must have appropriate alternative text
• Heading Structure: Proper heading hierarchy (h1 → h2 → h3, etc.)
• Landmark Regions: Proper use of ARIA landmarks (banner, main, navigation, contentinfo)
• Interactive Elements: Buttons, links, and controls must have accessible names
• Language Attributes: HTML lang attribute must be set

Skip links are hidden links that appear at the top of a page when a keyboard user tabs into them. They allow users to bypass repetitive content (like navigation menus) and jump directly to the main content.

Why Are Skip Links Important?

• Essential for keyboard-only users who can't use a mouse
• Required by WCAG 2.1 Success Criterion 2.4.1 (Bypass Blocks)
• Improve navigation efficiency for screen reader users
• Help users with motor impairments who find repeated tabbing difficult

Skip Link Implementation Requirements

• Must be the first focusable element on the page
• Must become visible when focused
• Must link to a valid target (e.g., #main-content)
• Target element must exist and be focusable

Current Skip Link Status

• Skip links found: 24/24 pages
• Skip links working: 24/24 pages

The accessibility tests performed by axe-core are designed to ensure compliance with the following standards:

IITAA Accessibility Standards for Illinois

The Illinois Information Technology Accessibility (IITAA) standards require that all state websites and digital services be accessible to individuals with disabilities. These standards align with WCAG 2.1 Level AA and Section 508 requirements.

• IITAA Standards Documentation

WCAG 2.1 Level AA Guidelines

The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA are internationally recognized standards for web accessibility. These guidelines provide a comprehensive framework for making web content accessible to people with disabilities.

• WCAG 2.1 Quick Reference

Section 508 Standards

Section 508 of the Rehabilitation Act requires federal agencies and organizations receiving federal funding to make their electronic and information technology accessible to people with disabilities.

• Section 508 Standards

ADA Title II Requirements

Title II of the Americans with Disabilities Act requires state and local governments to provide equal access to their services, programs, and activities, including websites and digital content.

• ADA.gov - Web Accessibility

Development vs. Production Testing

This audit was run against the Development environment (http://localhost:3000).

• Development: Tests against your local development server. Results may differ from production due to missing assets, different configurations, or debug features.
• Production: Tests against your live website. This provides the most accurate results for what users actually experience.

Recommendation: Run audits in both environments and fix issues found in either.

Nuxt + Vuetify Specific Considerations

This audit is configured for Nuxt 4 + Vuetify 3 applications with the following considerations:

• Region rule disabled: Vue/Nuxt's component structure can cause false positives with the 'region' rule
• Nuxt root excluded: The #__nuxt container is excluded from testing
• Dynamic content: The audit waits for Vue to fully render before running tests
• Vuetify components: ARIA roles on Vuetify components are verified