Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 1 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 ✗

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

7 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 7 <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.

A+

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

7 <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

34 headings

PASS

34 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 UC Davis
H1 UC Davis duplicate H1
H2 Congrats, New Aggies!
H2 From Labs to Lives
H2 California's College Town
H2 Main Campus
H2 Bodega Marine Lab
H2 UC Davis Health
H2 Tahoe Environmental Research Center
H2 In the middle of everywhere
H2 A top-tier public university
H2 Ranked 1st in the nation in agriculture and forestry
H2 Ranked 1st in the nation in veterinary medicine
H2 Ranked 2nd public university in the nation for graduate financial success
H2 Ranked 9th nationally among public universities
H2 Unrivaled student experience
H3 Housing
H3 Dining and Food
H3 City of Davis
H3 Athletics
H2 Campus facts
H3 With roughly 55 miles of bike and pedestrian paths, Davis is easy to get around.
H3 Like the invention of the full-body scanner, UC Davis has led the way with innovative discoveries for more than half a century.
H3 700+ students present their research at our annual Undergraduate Research, Scholarship and Creative Activities Conference.
H2 Unique to UC Davis
H3 Learn to brew beer!
H3 Take a study break with a puppy!
H2 Trending now
H2 Follow us
H2 UC Davis
H2 Students
H2 Alumni
H2 Faculty
H2 Staff

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 56 images OK

PASS

All 56 images OK

4 decorative image(s) correctly marked

52 image(s) with good alt text

56 images 52 good alt text 4 decorative

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 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">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#edit-keys	search	Search	for/id
#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

Link & Button Quality

1 issue(s) across 292 links and 42 buttons

PASS

1 issue(s) across 292 links and 42 buttons

1 link(s) with no accessible text

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

Got: a#main-content

291 link(s) with descriptive text

292 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label

333 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

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 404 | UC Davis ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 UC Davis	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 From Labs to Lives	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 California's	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Main Campus	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Bodega Marine Lab	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 UC Davis Health	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tahoe Environmental …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 In the middle of eve…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 A top-tier	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ranked 1st in the na…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ranked 1st in the na…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ranked 2nd public un…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ranked 9th nationall…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Unrivaled	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Follow us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 UC Davis	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Students	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Alumni	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Faculty	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Staff	21.00:1	3.0:1	#000000	#FFFFFF	Pass

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+

Lighthouse Accessibility Audits

Score 96/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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HOUSING `div.o-box--flush > a.marketing-link > div.marketing-link__body > h3.marketing-link__title`
DINING AND FOOD `div.o-box--flush > a.marketing-link > div.marketing-link__body > h3.marketing-link__title`
CITY OF DAVIS `div.o-box--flush > a.marketing-link > div.marketing-link__body > h3.marketing-link__title`
ATHLETICS `div.o-box--flush > a.marketing-link > div.marketing-link__body > h3.marketing-link__title`

These are opportunities to improve the legibility of your content.

○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

●`[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

●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 are distinguishable without relying on color.

●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.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●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

○ARIA IDs are unique

○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

○Form elements have associated labels

○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.

○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.