Skip to content
https://depaul.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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
Heading Hierarchy
20 headings, 2 skip(s)
REVIEW
20 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Home
  • H2 At DePaul, Education is Hands-on, Heart-first and Mission-led
  • H2 Our University Revolves Around You
  • H2 Lead with Head, Hands and Heart
  • H6 Find a Major That
 Moves You skipped
  • H5 Take our questionnaire
  • H5 Discover DePaul’s Colleges and Schools
  • H5 Experience the DePaul Difference
  • H2 Invest in What Matters
  • H5 Hear About DePaul From Our Students skipped
  • H4 Join ourBlue Demon Family
  • H4 Find the answers you need.
  • H5 Tuition and Fees
  • H5 Apply
  • H5 Visit
  • H3 DePaul University
  • H2 Information for
  • H2 Academic Resources
  • H2 Campus Resources
  • H2 University Resources

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Alt Text Quality
Action
15 of 20 images have issues
REVIEW
15 of 20 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
12 image(s) with filename as alt text
Warning::
1 image(s) with generic alt text
Info::
3 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
20 images 2 good alt text 3 decorative 13 generic 2 missing
IssueCount
missing2 image(s)
filename12 image(s)
generic1 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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Error Page | DePaul University - Chicago, IL ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA 4 pass AA only
title Home | DePaul University - Chicago, IL
1.85:1
#000000
on
#3A3A3A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
2.86:1
#000000
on
#565656
needs 4.5:1 (normal text)
16px · top of page (header area)
div Welcome to
3.77:1
#000000
on
#686868
needs 4.5:1 (normal text)
16px · top of page (header area)
em DePaul
3.83:1
#000000
on
#696969
needs 4.5:1 (normal text)
16px · above the fold
p Guided by immersive learning, real-world…
4.00:1
#000000
on
#6C6C6C
needs 4.5:1 (normal text)
16px · above the fold
a View Undergraduate Majors
4.06:1
#000000
on
#6D6D6D
needs 4.5:1 (normal text)
16px · above the fold
a View Graduate Programs
4.06:1
#000000
on
#6D6D6D
needs 4.5:1 (normal text)
16px · above the fold
p Experience smaller classes, bigger oppor…
4.00:1
#000000
on
#6C6C6C
needs 4.5:1 (normal text)
16px · above the fold
div student-to-faculty ratio, creating a mor…
3.94:1
#000000
on
#6B6B6B
needs 4.5:1 (normal text)
16px · above the fold
span 210
3.83:1
#000000
on
#696969
needs 4.5:1 (normal text)
16px · mid-page
div students enrolled across 10 colleges and…
3.77:1
#000000
on
#686868
needs 4.5:1 (normal text)
16px · mid-page
div of recent graduates report positive care…
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page
div of classes are led by faculty, not by T…
3.55:1
#000000
on
#646464
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Home3.60:13.0:1
#000000
#656565
Pass
h2 At DePaul, Education…3.94:13.0:1
#000000
#6B6B6B
Pass
h2 Our University Revol…4.00:13.0:1
#000000
#6C6C6C
Pass
h2 Lead with Head, Hand…3.39:13.0:1
#000000
#616161
Pass
h2 Invest in What Matte…17.66:13.0:1
#000000
#E5ECF6
Pass
h3 DePaul University17.66:13.0:1
#000000
#E5ECF6
Pass
title Home | DePaul Univer…1.85:14.5:1
#000000
#3A3A3A
Fail
a Skip to main content2.86:14.5:1
#000000
#565656
Fail
div Welcome to3.77:14.5:1
#000000
#686868
Fail
em DePaul3.83:14.5:1
#000000
#696969
Fail
p Guided by immersive …4.00:14.5:1
#000000
#6C6C6C
Fail
a View Undergraduate M…4.06:14.5:1
#000000
#6D6D6D
Fail
a View Graduate Progra…4.06:14.5:1
#000000
#6D6D6D
Fail
p Experience smaller c…4.00:14.5:1
#000000
#6C6C6C
Fail
div student-to-faculty r…3.94:14.5:1
#000000
#6B6B6B
Fail
span 2103.83:14.5:1
#000000
#696969
Fail
div students enrolled ac…3.77:14.5:1
#000000
#686868
Fail
div of recent graduates …3.66:14.5:1
#000000
#666666
Fail
div of classes are led b…3.55:14.5:1
#000000
#646464
Fail
p DePaul’s unique La…17.66:14.5:1
#000000
#E5ECF6
Pass

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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtextSearch DePaularia-label
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 26 passed
PASS
92

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Find a Major That
 Moves You div.row > div#32c42a3b-79ea-403c-baf6-a93858f5bbad > div.card-banner__hero > h6.card-banner__title
Hear About DePaul From Our Students div.row > div#9215e160-a886-45f4-b3d6-7fbe3e593dbd > div.card-listing__header > h5

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Collapsed Information for accordion Information for div#row-1 > div#f71b176d-2d8f-49c2-848d-5dfc816718fa > div#f71b176d-2d8f-49c2-848d-5dfc816718fa-column-2 > li#9eef020e-2725-453b-b9e4-61c0c1b2d09d
Collapsed Academic Resources accordion Academic Resources div#row-1 > div#f71b176d-2d8f-49c2-848d-5dfc816718fa > div#f71b176d-2d8f-49c2-848d-5dfc816718fa-column-3 > li#420b6a6f-c2e2-468e-bfe8-e6824bbdd211
Collapsed Campus Resources accordion Campus Resources div#row-1 > div#f71b176d-2d8f-49c2-848d-5dfc816718fa > div#f71b176d-2d8f-49c2-848d-5dfc816718fa-column-4 > li#dc458ccb-31c9-4172-bf09-3cdd22ecfed3
Collapsed University Resources accordion University Resources div#row-1 > div#f71b176d-2d8f-49c2-848d-5dfc816718fa > div#f71b176d-2d8f-49c2-848d-5dfc816718fa-column-5 > li#f54b5940-1c1f-45d8-99c2-205183f05992

These are opportunities to improve the experience of reading tabular or list data using 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
Search div.search-widget-faq--search-with-carousel__search-container > div.component > div.faq-search__input-wrapper > button.faq-search__button

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.
●`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
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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
○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