Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 8 REVIEW 3 FIX

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

Action

26 headings, 2 skip(s)

REVIEW

26 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

2 empty heading(s)

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

H1 Become a Blue Hen
H2 Laura Carlson inaugurated as UD’s 29th president
H2 Top marks for UD graduate programs
H4 (empty)
H4 The University of Delaware has been ranked among the 2026 Best Graduate Schools by U.S. News & World Report.
H4 Read More
H2 YOU ARE THE HEART OF UD.
H4 Together, our UD community is bound by Blue Hen pride and a shared drive to better the world around us. Because of this community, breakthroughs in healthcare happen. Championships are won. Award-winn skipped
H4 On I Heart UD Giving Day, give back to to the causes you love.
H3 Give From The Heart >
H2 The Green Superheroes of UD
H2 (empty)
H3 Blue Hens are tackling environmental foes in the ultimate fight for planet Earth
H3 Meet the Heroes >
H3 Undergraduate Programs
H3 Graduate Programs
H3 Online Programs
H2 The latest news from the University of Delaware
H2 Today's Stories
H3 UD's commitment to an equitable and inclusive environment
H4 The University of Delaware does not discriminate against any person on the basis of race, color, national origin, sex, gender identity or expression, sexual orientation, genetic information, marital s
H4 Office of Civil Rights and Title IX Compliance
H3 EXPLORE
H3 ACADEMICS
H3 SERVICES
H3 CONNECT

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Link & Button Quality

1 issue(s) across 190 links and 5 buttons

REVIEW

1 issue(s) across 190 links and 5 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /udaily/2026/april/us-news-world-report-grad-school-rankings/ ("Read More")

7 link(s) open in new tab without warning

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

Got: /content/udel/en/apply/undergraduate-admissions/admitted-students; /udaily/2026/april/laura-carlson-inauguration-investiture-29th-president/; https://givingday.udel.edu/?utm_source=ocm-homepage&utm_medium=link&utm_conte…; /content/udel/en/udaily/2026/april/laura-carlson-going-the-distance-magazine-…; /content/udel/en/udaily/2026/april/laura-carlson-going-the-distance-magazine-…; https://events.udel.edu/; https://sites.udel.edu/oei/

182 link(s) with descriptive text

190 links

0 empty

1 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/content/udel/en/apply/undergraduate-adm…	Next Steps for Admitted Studen…	new tab	Add '(opens in new tab)' to text
/udaily/2026/april/laura-carlson-inaugur…	View the Event Recap	new tab	Add '(opens in new tab)' to text
/udaily/2026/april/us-news-world-report-…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Us News World Report Grad School Rankings
https://givingday.udel.edu/?utm_source=o…	Give From The Heart	new tab	Add '(opens in new tab)' to text
/content/udel/en/udaily/2026/april/laura…	As UD’s 29th president, Laur…	new tab	Add '(opens in new tab)' to text
/content/udel/en/udaily/2026/april/laura…	Keep Reading	new tab	Add '(opens in new tab)' to text
https://events.udel.edu/	Events Calendar	new tab	Add '(opens in new tab)' to text
https://sites.udel.edu/oei/	Office of Civil Rights and Tit…	new tab	Add '(opens in new tab)' to text

187 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/udaily/2026/april/us-news-world-report-grad-school-rankings/ ("Read More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

/content/udel/en/apply/undergraduate-admissions/admitted-students; /udaily/2026/april/laura-carlson-inauguration-investiture-29th-president/; https://givingday.udel.edu/?utm_source=ocm-homepage&utm_medium=link&utm_conte…; /content/udel/en/udaily/2026/april/laura-carlson-going-the-distance-magazine-…; /content/udel/en/udaily/2026/april/laura-carlson-going-the-distance-magazine-…; https://events.udel.edu/; https://sites.udel.edu/oei/

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title University of Delaware | Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

9 icon(s) detected

REVIEW

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

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 Become a Blue Hen

2.74:1

#000000

#00539F

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The Green Superheroes of UD

2.74:1

#000000

#00539F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Today's Stories

1.00:1

#00539F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Blue Hens are tackling environmental foe…

2.74:1

#000000

#00539F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 UD's commitment to an equitable and incl…

2.74:1

#000000

#00539F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 EXPLORE

2.74:1

#000000

#00539F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ACADEMICS

2.74:1

#000000

#00539F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 SERVICES

2.74:1

#000000

#00539F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 CONNECT

2.74:1

#000000

#00539F

needs 3.0:1 (large text)

19px · bottom of viewport

title University of Delaware

2.74:1

#000000

#00539F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to site content

2.74:1

#000000

#00539F

needs 4.5:1 (normal text)

16px · top of page (header area)

label Quick Links

3.53:1

#000000

#57647F

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a MyUD

3.99:1

#000000

#846465

needs 4.5:1 (normal text)

16px · top of page (header area)

a Maps

2.90:1

#000000

#6E5048

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a People Directory

3.02:1

#000000

#6E5351

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Email

3.63:1

#000000

#6F6360

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Careers

1.53:1

#000000

#312C2B

needs 4.5:1 (normal text)

16px · above the fold

a Library

1.96:1

#000000

#3F3D42

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a A-Z Index

2.74:1

#000000

#00539F

needs 4.5:1 (normal text)

16px · above the fold

5 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)

Element	Ratio	Required	FG	BG	Result
h1 Become a Blue Hen	2.74:1	3.0:1	#000000	#00539F	Fail
h2 The Green Superheroe…	2.74:1	3.0:1	#000000	#00539F	Fail
h2 The latest news from…	7.67:1	3.0:1	#FFFFFF	#00539F	Pass
h2 Today's Stories	1.00:1	3.0:1	#00539F	#00539F	Fail
h3 Blue Hens are tackli…	2.74:1	3.0:1	#000000	#00539F	Fail
h3 UD's commitment to a…	2.74:1	3.0:1	#000000	#00539F	Fail
h3 EXPLORE	2.74:1	3.0:1	#000000	#00539F	Fail
h3 ACADEMICS	2.74:1	3.0:1	#000000	#00539F	Fail
h3 SERVICES	2.74:1	3.0:1	#000000	#00539F	Fail
h3 CONNECT	2.74:1	3.0:1	#000000	#00539F	Fail
title University of Delawa…	2.74:1	4.5:1	#000000	#00539F	Fail
a Skip to site content	2.74:1	4.5:1	#000000	#00539F	Fail
label Quick Links	3.53:1	4.5:1	#000000	#57647F	Fail
a MyUD	3.99:1	4.5:1	#000000	#846465	Fail
a Maps	2.90:1	4.5:1	#000000	#6E5048	Fail
a People Directory	3.02:1	4.5:1	#000000	#6E5351	Fail
a Email	3.63:1	4.5:1	#000000	#6F6360	Fail
a Careers	1.53:1	4.5:1	#000000	#312C2B	Fail
a Library	1.96:1	4.5:1	#000000	#3F3D42	Fail
a A-Z Index	2.74:1	4.5:1	#000000	#00539F	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.

Lighthouse Accessibility Audits

Score 85/100 — 5 failing, 18 passed

REVIEW

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open Main Navigation `div.pageheader > header > div.header-container > div#sidebar-toggle`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
`div.callpanel954811 > div.container > div.textComponent > h4`
Together, our UD community is bound by Blue Hen pride and a shared drive to b… `div.callpanel445747 > div.container > div.textComponent > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`
div.row > div.col-md-8 > div.calloutTextImageEditor > meta `div.row > div.col-md-8 > div.calloutTextImageEditor > meta`

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.no_js `html.no_js`

These items highlight common accessibility best practices.

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
MEET THE HEROES > `div.col-md-4 > div.callToActionComponent > h3 > a`
Reserve Your Place SCHEDULE A TOUR `div.columnGenerator > div.row > div.col-md-4 > a`
Get More Information MEET YOUR COUNSELOR `div.columnGenerator > div.row > div.col-md-4 > a`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

●Skip links are focusable.

●All heading elements contain content.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

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

○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

○Buttons have an accessible name

○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

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

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

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

A+

Alt Text Quality

All 32 images OK

PASS

All 32 images OK

1 image(s) with alt text over 125 characters

31 image(s) with good alt text

32 images 31 good alt text

Issue	Count
too long	1 image(s)

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit" name="sa">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#q-2	text	Search	aria-label
#q	text	Search	aria-label
sa	submit	Submit Search	aria-label
sa	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.