Skip to content
https://usf.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Oops, Page Not Found | University of South Florida ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA 9 pass AA only
title Welcome to the University of South Flori…
2.03:1
#000000
on
#044A34
needs 4.5:1 (normal text)
16px · top of page (header area)
span Emergency
2.71:1
#000000
on
#2D5B4B
needs 4.5:1 (normal text)
16px · top of page (header area)
a usf.edu/usfalerts
2.50:1
#000000
on
#38534A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
2.47:1
#000000
on
#484E4D
needs 4.5:1 (normal text)
16px · top of page (header area)
span University of South Florida - 70 Est. 19…
2.29:1
#000000
on
#4A4749
needs 4.5:1 (normal text)
16px · above the fold
span University of South Florida - 70 Est. 19…
2.26:1
#000000
on
#4A4649
needs 4.5:1 (normal text)
16px · above the fold
span Search
2.44:1
#000000
on
#4E4B4D
needs 4.5:1 (normal text)
16px · above the fold
label Search USF:
2.16:1
#000000
on
#484345
needs 4.5:1 (normal text)
16px · above the fold
span About USF
2.39:1
#000000
on
#4D4A4A
needs 4.5:1 (normal text)
16px · above the fold
span About USF
2.40:1
#000000
on
#4D4A4B
needs 4.5:1 (normal text)
16px · above the fold
a Overview
2.40:1
#000000
on
#4D4A4B
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 70 Years of Bold3.14:13.0:1
#000000
#0F6949
Pass
h2 Start your journey:3.14:13.0:1
#000000
#0F6949
Pass
h2 Trending at USF3.14:13.0:1
#000000
#0F6949
Pass
h2 Built for Your Futur…3.14:13.0:1
#000000
#0F6949
Pass
h2 Live the Bulls Life3.14:13.0:1
#000000
#0F6949
Pass
h2 We are One USF3.14:13.0:1
#000000
#0F6949
Pass
h2 Events3.14:13.0:1
#000000
#0F6949
Pass
h2 Featured News3.14:13.0:1
#000000
#0F6949
Pass
h2 Your Moment Starts N…3.14:13.0:1
#000000
#0F6949
Pass
title Welcome to the Unive…2.03:14.5:1
#000000
#044A34
Fail
span Emergency2.71:14.5:1
#000000
#2D5B4B
Fail
a usf.edu/usfalerts2.50:14.5:1
#000000
#38534A
Fail
a Skip to main content2.47:14.5:1
#000000
#484E4D
Fail
span University of South …2.29:14.5:1
#000000
#4A4749
Fail
span University of South …2.26:14.5:1
#000000
#4A4649
Fail
span Search2.44:14.5:1
#000000
#4E4B4D
Fail
label Search USF:2.16:14.5:1
#000000
#484345
Fail
span About USF2.39:14.5:1
#000000
#4D4A4A
Fail
span About USF2.40:14.5:1
#000000
#4D4A4B
Fail
a Overview2.40:14.5:1
#000000
#4D4A4B
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
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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
31 headings
PASS
31 headings
Info::
Single H1 present
  • H2 Emergency -
  • H2 University of South Florida - 70 Est. 1956
  • H2 University of South Florida - 70 Est. 1956
  • H3 About USF
  • H3 Academics
  • H3 Admissions & Aid
  • H3 Campus Life
  • H3 Athletics
  • H3 Research
  • H3 About USF
  • H3 Academics
  • H3 Admissions & Aid
  • H3 Campus Life
  • H3 Athletics
  • H3 Research
  • H1 70 Years of Bold
  • H2 Start your journey:
  • H2 Trending at USF
  • H3 Visit USF
  • H3 The FAFSA is Open
  • H3 Incoming Students: Finish Your Onboarding Checklist
  • H2 Built for Your Future
  • H2 Live the Bulls Life
  • H2 We are One USF
  • H2 Events
  • H2 Featured News
  • H3 Robotic microsurgery offers new hope for patients at USF Health and Tampa General Hospital
  • H3 USF-Jabil partnership advances next-generation medical technology
  • H3 Grandfather’s Vietnam heroism led grandson to USF and an interest in national security
  • H3 U.S. News & World Report ranks more than 40 USF graduate programs among the nation’s best
  • H2 Your Moment Starts Now
A+
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
16 image(s) with good alt text
17 images 16 good alt text
IssueCount
too long1 image(s)
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#mobile-search-inputtextSearch USF:for/id
#search-inputtextSearch USF:for/id
#audience-selectselectStart your journey:for/id
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 27 passed
PASS
100

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.

○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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.
●Select elements have associated label elements.
●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 are distinguishable without relying on color.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[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
○`[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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○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.
○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.

Send Feedback