Skip to content
https://duke.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::
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
Landmark Structure
Action
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Heading Hierarchy
53 headings
REVIEW
53 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H1 (empty)
  • H2 News
  • H2 Search
  • H3 Default Search Links
  • H3 Autocompleted Search Links
  • H2 Main menu
  • H1 United in Spirit duplicate H1
  • H2 Our spirit is in the roar of crowds, in breakthrough moments in the lab, and in standing side by side with the local community.
  • H2 What Spirit Means to Us
  • H2 Our Passions
  • H2 Stitched with Spirit
  • H2 It Takes a Team
  • H2 Belief
  • H2 Past And Present
  • H2 Our Passions
  • H3 Student-Athletes Rise to the Challenge
  • H3 For This Space Club, It’s Rocket Science
  • H3 Divinity Alumni Connect with Durham
  • H3 The Excitement Behind A Major
  • H3 King’s Singers Inspire Kids to Give It a Go
  • H3 Engineering Students Become Car Junkies
  • H3 What Sparks New Ventures?
  • H3 A First-Hand Look into Energy Transition
  • H2 Spirit Is Stitched to Our Attire
  • H3 The Threads that Tie Us Together
  • H3 Med Students Hope Their School Swipes Right
  • H3 ROTC Spirit
  • H3 The Flashy Suits of the ALS Champion
  • H3 Different Uniforms,Same Tenacity
  • H2 It Takes a Team
  • H3 Students Tackle Plastic Pollution
  • H3 Showing Spirit for Sports and Sustainability
  • H3 Tracing the Past to Shape the Future
  • H2 How We Prevail
  • H3 We Never, Ever, Ever Give Up
  • H3 As the Drone Flies, It Can Save Lives
  • H3 A Breathing Therapy for the Sickest of Patients
  • H2 Belief
  • H3 From Court to Chapel: Coach K Reflects on Values That Last
  • H3 Indigenous Superheroes Get a Voice
  • H3 Amid Conflict, Findingthe Humanity in Medicine
  • H3 How Duke Helps Students with Wellness from Day One
  • H2 Connecting Past and Present
  • H3 How Teams Work in Surgery and on the Court
  • H3 How Service Becomes a Calling
  • H3 A Partnership to Save Lives
  • H3 A 50-Year Friendship
  • H2 Previous Features
  • H2 Across Our State
  • H2 Accessibility
  • H2 Get in Touch
  • H2 Compliance

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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 Page not found - Duke University ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h1 United in Spirit
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Search
2.90:1
#000000
on
#734C56
needs 3.0:1 (large text)
24px · mid-page
h2 Main menu
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our spirit is in the roar of crowds, in …
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Spirit Means to Us
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Our Passions
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Stitched with Spirit
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 It Takes a Team
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Belief
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Past And Present
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Our Passions
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Spirit Is Stitched to Our Attire
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 It Takes a Team
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How We Prevail
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Belief
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting Past and Present
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Previous Features
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Accessibility
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get in Touch
1.42:1
#000000
on
#012169
needs 3.0:1 (large text)
24px · bottom of viewport

6 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
h1 United in Spirit1.42:13.0:1
#000000
#012169
Fail
h2 News14.73:13.0:1
#000000
#CAD9F3
Pass
h2 Search2.90:13.0:1
#000000
#734C56
Fail
h2 Main menu1.42:13.0:1
#000000
#012169
Fail
h2 Our spirit is in the…1.42:13.0:1
#000000
#012169
Fail
h2 What Spirit Means to…1.42:13.0:1
#000000
#012169
Fail
h2 Our Passions1.42:13.0:1
#000000
#012169
Fail
h2 Stitched with Spirit1.42:13.0:1
#000000
#012169
Fail
h2 It Takes a Team1.42:13.0:1
#000000
#012169
Fail
h2 Belief1.42:13.0:1
#000000
#012169
Fail
h2 Past And Present1.42:13.0:1
#000000
#012169
Fail
h2 Our Passions1.42:13.0:1
#000000
#012169
Fail
h2 Spirit Is Stitched t…1.42:13.0:1
#000000
#012169
Fail
h2 It Takes a Team1.42:13.0:1
#000000
#012169
Fail
h2 How We Prevail1.42:13.0:1
#000000
#012169
Fail
h2 Belief1.42:13.0:1
#000000
#012169
Fail
h2 Connecting Past and …1.42:13.0:1
#000000
#012169
Fail
h2 Previous Features1.42:13.0:1
#000000
#012169
Fail
h2 Accessibility1.42:13.0:1
#000000
#012169
Fail
h2 Get in Touch1.42:13.0:1
#000000
#012169
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
Alt Text Quality
All 28 images OK
PASS
All 28 images OK
Info::
18 image(s) with alt text over 125 characters
Info::
10 image(s) with good alt text
28 images 10 good alt text
IssueCount
too long18 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Lighthouse Accessibility Audits
Score 99/100 — 1 failing, 28 passed
PASS
99

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●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
●`[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
●`[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
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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 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.
○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
○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.

Send Feedback