Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-77wcw4

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://scu.edu/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://scu.edu/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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

2 issue(s) across 71 links and 5 buttons

REVIEW

2 issue(s) across 71 links and 5 buttons

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#button-left; button#button-right

71 link(s) with descriptive text

71 links

0 empty

0 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

74 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

button#button-left; button#button-right

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

14 icon(s) detected

REVIEW

14 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

a Alumni

3.00:1

#000000

#B30738

needs 4.5:1 (normal text)

16px · above the fold

span Santa Clara University Homepage

1.73:1

#000000

#621D28

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Progress	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h1 Needs	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h1 Located in the globa…	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h1 Discover SCU	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h1 Hear from SCU’s Th…	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h1 Find Your Future at …	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h1 Find Your Future at …	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h2 Where is Accountabil…	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h2 ‘A man of peace’…	17.63:1	3.0:1	#000000	#EDEBE6	Pass
h2 Amazon adds fuel sur…	17.63:1	3.0:1	#000000	#EDEBE6	Pass
title Home - Santa Clara U…	19.92:1	4.5:1	#000000	#F8F9FA	Pass
a Skip to main content	19.92:1	4.5:1	#000000	#F8F9FA	Pass
a Students	19.92:1	4.5:1	#000000	#F8F9FA	Pass
a Faculty & Staff	19.92:1	4.5:1	#000000	#F8F9FA	Pass
a Families	9.13:1	4.5:1	#000000	#DC98AC	Pass
a Alumni	3.00:1	4.5:1	#000000	#B30738	Fail
a Visitors	8.77:1	4.5:1	#000000	#DA94A6	Pass
a Offices & Services	17.63:1	4.5:1	#000000	#EDEBE6	Pass
a Schools & Centers	17.63:1	4.5:1	#000000	#EDEBE6	Pass
span Santa Clara Universi…	1.73:1	4.5:1	#000000	#621D28	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Heading Hierarchy

15 headings

PASS

15 headings

Multiple H1 headings (7 found)

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

H1 Progress Needs People
H1 Located in the global capital of innovation, sunny Silicon Valley is the ideal place to forge a brighter future duplicate H1
H2 Make More Than a Living. Make a Difference.
H1 Discover SCU duplicate H1
H2 Santa Clara University establishes the Cunningham Shoquist Center for Applied AI and Human Potential
H2 How one business professor is reimagining what microfinance can do for the unhoused
H2 Tell Me Something New: A Life of Musical Discovery
H2 Math major and Putnam standout wants to change the way you think about math
H1 Hear from SCU’s Thought Leaders duplicate H1
H2 Where is Accountability When Governments Deploy AI?
H2 ‘A man of peace’: Pope Leo embarks on a marathon visit to Africa
H2 Amazon adds fuel surcharge for sellers. But will you have to pay more?
H1 Featured Events duplicate H1
H1 Find Your Future at SCU duplicate H1
H1 Find Your Future at SCU duplicate H1

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

1 of 16 images have issues

PASS

1 of 16 images have issues

1 image(s) with generic alt text

1 decorative image(s) correctly marked

14 image(s) with good alt text

16 images 14 good alt text 1 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search	Search	aria-label
q	search	Search	aria-label

A+

Lighthouse Accessibility Audits

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.carousel-container > div.carousel > div#window > button#button-left `div.carousel-container > div.carousel > div#window > button#button-left`
div.carousel-container > div.carousel > div#window > button#button-right `div.carousel-container > div.carousel > div#window > button#button-right`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●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

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

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

○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

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