Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Link & Button Quality

1 issue(s) across 107 links and 16 buttons

REVIEW

1 issue(s) across 107 links and 16 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.universityofcalifornia.edu/news/uc-davis-releases-5-strawberry-va…; https://www.universityofcalifornia.edu/news/uc-cooperative-extension-advisors…; https://www.universityofcalifornia.edu/news/your-bird-flu-questions-answered

103 link(s) with descriptive text

107 links

1 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.universityofcalifornia.edu/n…	From lab to field to plate	new tab	Add '(opens in new tab)' to text
https://www.universityofcalifornia.edu/n…	Science at the speed of agricu…	new tab	Add '(opens in new tab)' to text
https://www.universityofcalifornia.edu/n…	Staying ahead of avian flu	new tab	Add '(opens in new tab)' to text

119 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.universityofcalifornia.edu/news/uc-davis-releases-5-strawberry-va…; https://www.universityofcalifornia.edu/news/uc-cooperative-extension-advisors…; https://www.universityofcalifornia.edu/news/your-bird-flu-questions-answered

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

6 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 6 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

8 pass 12 fail WCAG AA

a Take action: Stand up for

2.62:1

#000000

#005581

needs 4.5:1 (normal text)

16px · top of page (header area)

button menu

2.62:1

#000000

#005581

needs 4.5:1 (normal text)

16px · top of page (header area)

span mobile menu open

2.62:1

#000000

#005581

needs 4.5:1 (normal text)

16px · above the fold

div Main Navigation

2.34:1

#000000

#534834

needs 4.5:1 (normal text)

16px · above the fold

a Campuses & locations

2.27:1

#000000

#4E4734

needs 4.5:1 (normal text)

16px · above the fold

span Toggle subnavigation for Campuses & loca…

2.24:1

#000000

#4D4634

needs 4.5:1 (normal text)

16px · above the fold

a Find your place at UC

1.94:1

#000000

#31403F

needs 4.5:1 (normal text)

16px · above the fold

a Student success

1.30:1

#000000

#1B2225

needs 4.5:1 (normal text)

16px · above the fold

span Toggle subnavigation for Student success

1.15:1

#000000

#0E1620

needs 4.5:1 (normal text)

16px · above the fold

a FirstGen

2.21:1

#000000

#254868

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Graduate students

1.22:1

#000000

#0D1B34

needs 4.5:1 (normal text)

16px · above the fold

a Transfer students

1.55:1

#000000

#1B2F4A

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Feeding the nation	6.32:1	3.0:1	#000000	#1295D8	Pass
h2 Campuses	6.32:1	3.0:1	#000000	#1295D8	Pass
h3 UC breaks a Nobel re…	6.32:1	3.0:1	#000000	#1295D8	Pass
h3 Innovating to keep A…	6.32:1	3.0:1	#000000	#1295D8	Pass
h3 Revolutionizing care…	6.32:1	3.0:1	#000000	#1295D8	Pass
h3 Stand with UC	6.32:1	3.0:1	#000000	#1295D8	Pass
title Home \| University of…	16.58:1	4.5:1	#000000	#FFE552	Pass
a Skip to main content	16.58:1	4.5:1	#000000	#FFE552	Pass
a Take action: Stand u…	2.62:1	4.5:1	#000000	#005581	Fail
button menu	2.62:1	4.5:1	#000000	#005581	Fail
span mobile menu open	2.62:1	4.5:1	#000000	#005581	Fail
div Main Navigation	2.34:1	4.5:1	#000000	#534834	Fail
a Campuses & locations	2.27:1	4.5:1	#000000	#4E4734	Fail
span Toggle subnavigation…	2.24:1	4.5:1	#000000	#4D4634	Fail
a Find your place at U…	1.94:1	4.5:1	#000000	#31403F	Fail
a Student success	1.30:1	4.5:1	#000000	#1B2225	Fail
span Toggle subnavigation…	1.15:1	4.5:1	#000000	#0E1620	Fail
a FirstGen	2.21:1	4.5:1	#000000	#254868	Fail
a Graduate students	1.22:1	4.5:1	#000000	#0D1B34	Fail
a Transfer students	1.55:1	4.5:1	#000000	#1B2F4A	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

6 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

Heading Hierarchy

22 headings, 1 skip(s)

PASS

22 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Our mission: Improving lives
H3 UC breaks a Nobel record skipped
H3 Innovating to keep America in the lead
H4 Fixing glitches in the code of life
H4 When seconds count
H4 Putting powerful tech to work for American security
H3 Revolutionizing care for families
H4 Life-saving care in California’s Central Valley
H4 A pro skater rides again
H4 Federal funding drives progress in the fight against cancer
H2 Feeding the nation
H3 From lab to field to plate
H3 Science at the speed of agriculture
H3 Staying ahead of avian flu
H3 Stand with UC
H2 Campuses
H3 Academic health centers
H3 National laboratories
H3 Agriculture and Natural Resources
H3 Education outreach
H3 Academic publishing and broadcasting
H3 Other locations

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Alt Text Quality

All 9 images OK

PASS

All 9 images OK

9 image(s) with good alt text

9 images 9 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit" id="edit-submit">

2 control(s) properly labeled

3 controls

2 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#edit-keys	search	Search	for/id
#edit-email	text	Your email address	aria-label
#edit-submit	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title University of California ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 27 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
UC breaks a Nobel record `div.flex--2col > div.paragraph > div.clearfix > h3`

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.