Skip to content
https://fordham.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
a Information For
3.07:1
#000000
on
#5C5A5B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Current Students
2.86:1
#000000
on
#565656
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Faculty and Staff
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · above the fold
a Families
2.19:1
#000000
on
#454545
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Alumni
1.93:1
#000000
on
#3D3D3B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Find a Degree
1.65:1
#000000
on
#323330
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Find People
2.18:1
#000000
on
#454542
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Apply
2.15:1
#000000
on
#444442
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Visit
1.94:1
#000000
on
#433C39
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Give
4.32:1
#000000
on
#757168
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

9 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)
ElementRatioRequiredFGBGResult
h2 WE STAND FOR WHAT MA…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Doing Good That Beco…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We Are Leaders, Drea…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We’re Drawn to Whe…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fordham Privacy Pref…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage Consent Prefe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title Fordham University21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to Main Content21.00:14.5:1
#000000
#FFFFFF
Pass
a Log in21.00:14.5:1
#000000
#FFFFFF
Pass
a Information For3.07:14.5:1
#000000
#5C5A5B
Fail
a Current Students2.86:14.5:1
#000000
#565656
Fail
a Faculty and Staff1.93:14.5:1
#000000
#3D3D3D
Fail
a Families2.19:14.5:1
#000000
#454545
Fail
a Alumni1.93:14.5:1
#000000
#3D3D3B
Fail
a Find a Degree1.65:14.5:1
#000000
#323330
Fail
a Find People2.18:14.5:1
#000000
#454542
Fail
a Apply2.15:14.5:1
#000000
#444442
Fail
a Visit1.94:14.5:1
#000000
#433C39
Fail
a Give4.32:14.5:1
#000000
#757168
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
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <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 "Accessible Links" MAIN ASIDE "Notice" 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
27 headings
PASS
27 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Fordham University - Homepage
  • H1 Fordham University - Homepage duplicate H1
  • H2 WE STAND FOR WHAT MATTERS MOST
  • H2 Doing Good That Becomes Greater As The Jesuit University of New York
  • H2 We Are Leaders, Dreamers, Achievers, And Doers
  • H2 Stephanie Lane, Video Producer Intern at iHeartMedia
  • H2 Theo Vandenberg, Rotational Associate Intern at New York Life
  • H2 Carley Walker, Performance Marketing Associate Intern at Hearst
  • H2 John Garza, Sacristan Assistant Intern at Trinity Church
  • H2 Julia Sosa, Montefiore Health Opportunities Program Intern
  • H2 From Winding Elms to Bustling City Blocks
  • H2 AI for the Greater Good
  • H2 We’re Drawn to Where We’re Needed Most
  • H2 Hoda Kotb to Deliver Commencement Address
  • H3 Record-High Applications: A Look at Fordham’s Admitted Class of 2030
  • H3 How Addy Found Her People at Fordham
  • H3 Class of 2025 Lands Strong Job Outcomes Despite Tough Market
  • H3 19 Reasons to Love Fordham Right Now
  • H3 Fordham Students Help New Yorkers Navigate Tax Season
  • H3 New College Guide Names Fordham a Dream School
  • H2 Fordham Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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 84 images have issues
PASS
1 of 84 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
19 decorative image(s) correctly marked
Info::
64 image(s) with good alt text
84 images 64 good alt text 19 decorative 1 missing
IssueCount
missing1 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

A+
Form Accessibility
All 9 controls labeled
PASS
All 9 controls labeled
Info::
9 control(s) properly labeled
9 controls
9 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#site-search-inputtextSearch the sitefor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /media/home/admin-use-only/css/print.css
Print Stylesheet Print Optimized
Print stylesheet /media/home/admin-use-only/css/print.css Inline @media print Not detected
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 27 passed
PASS
97

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Helpful Links University Directory Careers at Fordham Nondiscrimination Policy … div.row > div.footer__col > div.footer__link-widget > ul.footer__link-widget__col
Visit Campus Tours Maps and Directions Virtual Tour div.row > div.footer__col > div.footer__link-widget > ul.footer__link-widget__col

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Menu div.header-nav__bottom > div.header-nav__bottom__container > div.header-nav__bottom__nav-toggler > button.header-nav__bottom__nav-toggler__button
Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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 are distinguishable without relying on color.
Links have a discernible name
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
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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.
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.
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