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

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 77 links and 2 buttons

REVIEW

1 issue(s) across 77 links and 2 buttons

1 link(s) with no accessible text

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

Got: a#main-content

2 link(s) open in new tab without warning

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

Got: https://www.youvisit.com/tour/sfsu ; https://www.youvisit.com/tour/ada/sfsu/88825?from=direct …

74 link(s) with descriptive text

77 links

1 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.youvisit.co…	Explore Our Campus Now	new tab	Add '(opens in new tab)' to text
https://www.youvisit.co…	View ADA Accessible Tour	new tab	Add '(opens in new tab)' to text

76 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.youvisit.com/tour/sfsu ; https://www.youvisit.com/tour/ada/sfsu/88825?from=direct …

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Page Not Found | San Francisco State University ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

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

title San Francisco State University

1.32:1

#000000

#231161

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.32:1

#000000

#231161

needs 4.5:1 (normal text)

16px · top of page (header area)

a SAN FRANCISCO STATE UNIVERSITY

1.32:1

#000000

#231161

needs 4.5:1 (normal text)

16px · top of page (header area)

a Apply Now

1.32:1

#000000

#231161

needs 4.5:1 (normal text)

16px · top of page (header area)

a A–Z

1.32:1

#000000

#231161

needs 4.5:1 (normal text)

16px · above the fold

a Calendar

1.32:1

#000000

#231161

needs 4.5:1 (normal text)

16px · above the fold

a Login

1.32:1

#000000

#231161

needs 4.5:1 (normal text)

16px · above the fold

span Toggle navigation

1.60:1

#000000

#34302B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 San Francisco State …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Welcome to San Franc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Learn About SFSU	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Academic Programs	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Athletics	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Gain Real World Expe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SFSU Community	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Make It Possible	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Upcoming Events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title San Francisco State …	1.32:1	4.5:1	#000000	#231161	Fail
a Skip to main content	1.32:1	4.5:1	#000000	#231161	Fail
a SAN FRANCISCO STATE …	1.32:1	4.5:1	#000000	#231161	Fail
a Apply Now	1.32:1	4.5:1	#000000	#231161	Fail
a A–Z	1.32:1	4.5:1	#000000	#231161	Fail
a Calendar	1.32:1	4.5:1	#000000	#231161	Fail
a Login	1.32:1	4.5:1	#000000	#231161	Fail
label Search …	15.72:1	4.5:1	#000000	#FFDC70	Pass
span Search SF State Butt…	15.72:1	4.5:1	#000000	#FFDC70	Pass
span Toggle navigation	1.60:1	4.5:1	#000000	#34302B	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

6 landmarks

PASS

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H1 San Francisco State Home
H2 Accept your admission offer
H2 Welcome to San Francisco State University
H2 Learn About SFSU
H2 Academic Programs
H2 Athletics
H2 Gain Real World Experience
H2 SFSU Community
H2 Explore Our Campus with a Virtual Tour!
H2 Make It Possible
H2 Upcoming Events
H2 Latest News
H2 Take the Next Steps

A+

Alt Text Quality

All 21 images OK

PASS

All 21 images OK

21 image(s) with good alt text

21 images 21 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search	text	Search SF State	for/id

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 24 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.

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
Search SF State Button `form#search-box > div.input-group > div.input-group-btn > button.btn`
Accessibility `div.col-md-3 > ul.list-unstyled > li > a`
Equity and Community Inclusion `div.col-md-3 > ul.list-unstyled > li > a`
Environment and Sustainability `div.col-md-3 > ul.list-unstyled > li > a`
Title IX `div.col-md-3 > ul.list-unstyled > li > a`
Privacy Policy `div.col-md-3 > ul.list-unstyled > li > a`
Annual Fire Safety Report PDF `div.col-md-3 > ul.list-unstyled > li > a`
Annual Safety Report (Clery) `div.col-md-3 > ul.list-unstyled > li > a`
Parenting Students `div.col-md-3 > ul.list-unstyled > li > a`
University Ombuds `div.col-md-3 > ul.list-unstyled > li > a`
Document Reader `div.col-md-3 > ul.list-unstyled > li > a`
WASC Accreditation `div.col-md-3 > ul.list-unstyled > li > a`

These items highlight common accessibility best practices.

○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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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

○Elements with visible text labels have matching accessible names.

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