Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 3 REVIEW 7 FIX

Link & Button Quality

Action

8 issue(s) across 168 links and 33 buttons

FIX

8 issue(s) across 168 links and 33 buttons

2 link(s) with no accessible text

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

Got: a.o-media__link (#368 on page); a.o-media__link (#473 on page)

2 link(s) open in new tab without warning

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

Got: https://calstate.policystat.com/policy/19831859/latest/#autoid-z2p98; https://www.onetrust.com/products/cookie-consent/

6 button(s) with no accessible text

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

Got: button.vimeo-showcase__playlist--nav-btn (#553 on page); button.vimeo-showcase__playlist--nav-btn (#555 on page); button (#748 on page); button (#764 on page); button (#780 on page); button (#796 on page)

164 link(s) with descriptive text

168 links

2 empty

0 generic text

2 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://calstate.policystat.com/policy/1…	, opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

191 links and buttons have descriptive text

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

a.o-media__link (#368 on page); a.o-media__link (#473 on page)

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://calstate.policystat.com/policy/19831859/latest/#autoid-z2p98; https://www.onetrust.com/products/cookie-consent/

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

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

button.vimeo-showcase__playlist--nav-btn (#553 on page); button.vimeo-showcase__playlist--nav-btn (#555 on page); button (#748 on page); button (#764 on page); button (#780 on page); button (#796 on page)

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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

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

Alt Text Quality

2 of 25 images have issues

REVIEW

2 of 25 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 decorative image(s) correctly marked

22 image(s) with good alt text

25 images 22 good alt text 1 decorative 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 1 pass AA only

title San José State University

2.82:1

#000000

#0055A2

needs 4.5:1 (normal text)

16px · top of page (header area)

a San José State University

2.40:1

#000000

#2D4984

needs 4.5:1 (normal text)

16px · top of page (header area)

span Visit

2.40:1

#000000

#2D4984

needs 4.5:1 (normal text)

16px · top of page (header area)

span Apply

2.14:1

#000000

#264374

needs 4.5:1 (normal text)

16px · above the fold

span Give

2.41:1

#000000

#2E4B7C

needs 4.5:1 (normal text)

16px · above the fold

span Menu

2.45:1

#000000

#0C4C90

needs 4.5:1 (normal text)

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

a Visit

2.82:1

#000000

#0055A2

needs 4.5:1 (normal text)

16px · above the fold

a Map

2.82:1

#000000

#0055A2

needs 4.5:1 (normal text)

16px · above the fold

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 A Transformative Uni…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Imagine Yourself Her…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Upcoming Events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SJSU Live & On Deman…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Privacy Preference C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Colleges	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Contact Us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Manage Consent Prefe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cookie List	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title San José State Univ…	2.82:1	4.5:1	#000000	#0055A2	Fail
a Skip to main content	5.66:1	4.5:1	#000000	#898756	Pass
a San José State Univ…	2.40:1	4.5:1	#000000	#2D4984	Fail
span Visit	2.40:1	4.5:1	#000000	#2D4984	Fail
span Apply	2.14:1	4.5:1	#000000	#264374	Fail
span Give	2.41:1	4.5:1	#000000	#2E4B7C	Fail
span Menu	2.45:1	4.5:1	#000000	#0C4C90	Fail
a Visit	2.82:1	4.5:1	#000000	#0055A2	Fail
a Map	2.82:1	4.5:1	#000000	#0055A2	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.

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 23 passed

REVIEW

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.vimeo-showcase__info-wrap > div.vimeo-showcase__playlist > button.vimeo-showcase__playlist--nav-btn > img `div.vimeo-showcase__info-wrap > div.vimeo-showcase__playlist > button.vimeo-showcase__playlist--nav-btn > img`
div.vimeo-showcase__info-wrap > div.vimeo-showcase__playlist > button.vimeo-showcase__playlist--nav-btn > img `div.vimeo-showcase__info-wrap > div.vimeo-showcase__playlist > button.vimeo-showcase__playlist--nav-btn > img`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.o-media__frame > div.o-media__copy > p.o-media__heading > a.o-media__link `div.o-media__frame > div.o-media__copy > p.o-media__heading > a.o-media__link`
div.o-media__frame > div.o-media__copy > p.o-media__heading > a.o-media__link `div.o-media__frame > div.o-media__copy > p.o-media__heading > a.o-media__link`
div.o-region--footer__quicklinks > ul.vertical > li.o-region--footer__item > a#ot-sdk-link `div.o-region--footer__quicklinks > ul.vertical > li.o-region--footer__item > a#ot-sdk-link`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.o-region--footer__quicklinks > ul.vertical > li.o-region--footer__item > a#ot-sdk-link `div.o-region--footer__quicklinks > ul.vertical > li.o-region--footer__item > a#ot-sdk-link`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SJSU Loves SJ `div.vimeo-showcase__playlist > div.swiper > div#swiper-wrapper-b52c96cc3d376a8a > div.vimeo-showcase__item`
Parking at SJSU `div.vimeo-showcase__playlist > div.swiper > div#swiper-wrapper-b52c96cc3d376a8a > div.vimeo-showcase__item`

○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

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

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

●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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○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

○Form elements have associated labels

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

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

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <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

A+

Heading Hierarchy

16 headings

PASS

16 headings

Single H1 present

H1 About
H2 A Transformative University
H2 Imagine Yourself Here
H2 News
H2 Upcoming Events
H2 SJSU Live & On Demand
H3 Colleges
H3 Resources
H3 Contact Us
H2 Privacy Preference Center
H3 Manage Consent Preferences
H4 Targeting Cookies
H4 Performance Cookies
H4 Functional Cookies
H4 Strictly Necessary Cookies
H3 Cookie List

A+

Form Accessibility

All 10 controls labeled

PASS

All 10 controls labeled

10 control(s) properly labeled

10 controls

10 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#gsc-i-id1	text	search	aria-label
#gsc-i-id2	text	search	aria-label
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id

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