UC Web Accessibility Report

This month at a glance

§ 01

Every number below reflects required issues only — axe-core rules tagged WCAG 2.0 or 2.1 Level A/AA, the baseline under ADA Title II and Section 508. Reach-goal issues (WCAG 2.1 AAA and WCAG 2.2) are tracked separately in the campus table. The Mobile column shows issues found only at mobile viewport width.

Why it matters

§ 02

Results by campus

§ 03

Every UC site that matches the current filter is listed below, grouped by campus when the view includes schools and colleges. Desktop is the WCAG 2.0/2.1 A/AA violation count at desktop width (1440px). Mobile is the same at mobile width (375px). Reach covers WCAG 2.1 AAA and all of WCAG 2.2 — aspirational, not yet legally required in the US. Select any row to see the specific rules and what they mean in plain language.

Table listing each UC site matching the current filter, with columns for site name, desktop violations, mobile violations, reach-goal violations, impact mix, element count, month-over-month change, and an expandable details button.
Site	Desktop	Mobile	Reach	Impact mix	Elements	Change	Details

Critical Serious Moderate Minor Unknown

Errors over time

§ 04

Lower lines are better. A flat line means that grouping held steady between months. A drop means someone fixed something. The chart's granularity follows the filter — campus-aggregated by default, per-site when you drill into a single campus or discipline.

Most common issues

§ 05

The 10 required-level axe-core rules (WCAG 2.0/2.1 Level A/AA) flagged most often this month across the filtered UC sites, stacked by impact severity. Reach-goal rules are tracked separately in each site's details row. Working through the top of this list tends to have the biggest impact for the most people.