Skip to content
https://odu.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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.

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.
B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="edit-submit">; <input type="submit" name="op" id="edit-submit">
Info::
3 control(s) properly labeled
5 controls
3 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
selectselectLabelaria-label
#edit-stextSite search formaria-label
#edit-stextSite search formaria-label
#edit-submitsubmit(none)none
#edit-submitsubmit(none)none

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

<input type="submit" name="op" id="edit-submit">; <input type="submit" name="op" id="edit-submit">

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

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 Page Not Found | Old Dominion University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
a Apply
3.19:1
#000000
on
#256383
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Visit
1.56:1
#000000
on
#003057
needs 4.5:1 (normal text)
16px · above the fold
a Give
1.56:1
#000000
on
#003057
needs 4.5:1 (normal text)
16px · above the fold
a myODU
1.93:1
#000000
on
#324216
needs 4.5:1 (normal text)
16px · above the fold
span Menu
1.64:1
#000000
on
#323415
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 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 Homepage17.82:13.0:1
#000000
#E9EDEF
Pass
h2 Life at ODU21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A Video Message from…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 From Firsts to Forwa…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Faces of ODU21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Take The Next Step21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Legal21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Visit21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Main Navigation21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mega Menu21.00:13.0:1
#000000
#FFFFFF
Pass
title ODU - Old Dominion U…8.39:14.5:1
#000000
#5DAFC4
Pass
a Skip to main content8.39:14.5:1
#000000
#5DAFC4
Pass
div We are forever Monar…8.39:14.5:1
#000000
#5DAFC4
Pass
a Alert Details8.39:14.5:1
#000000
#5DAFC4
Pass
a Apply3.19:14.5:1
#000000
#256383
Fail
a Visit1.56:14.5:1
#000000
#003057
Fail
a Give1.56:14.5:1
#000000
#003057
Fail
a myODU1.93:14.5:1
#000000
#324216
Fail
span Menu1.64:14.5:1
#000000
#323415
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
10 landmarks
PASS
10 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 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
14 headings
PASS
14 headings
Info::
Single H1 present
  • H1 Homepage
  • H2 Life at ODU
  • H2 A Video Message from President Hemphill
  • H2 From Firsts to Forward-Focused
  • H2 Faces of ODU
  • H2 Remembering Lt. Col. Brandon A. Shah ’07, Who Defined Leadership, Service and Heroism at ODU
  • H2 ODU’s Ellmer School of Nursing Welcomes Four-Legged Chief Compassion Officer
  • H2 How Much Is Nature Worth? ODU Researcher Has the Answer
  • H2 Take The Next Step
  • H2 Resources
  • H2 Legal
  • H2 Visit
  • H2 Main Navigation
  • H2 Mega Menu
A+
Alt Text Quality
All 38 images OK
PASS
All 38 images OK
Info::
9 decorative image(s) correctly marked
Info::
29 image(s) with good alt text
38 images 29 good alt text 9 decorative
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 28 passed
PASS
94

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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mega-menu-toggle > ul.menu > li.menu-item > a.menu-toggle div.mega-menu-toggle > ul.menu > li.menu-item > a.menu-toggle
div.mega-menu-toggle > ul.menu > li.menu-item > a.sr-text div.mega-menu-toggle > ul.menu > li.menu-item > a.sr-text

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of 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
Pause div.col-md-3 > div.icon-blocks > div.custom-dots-navigation > button#play-pause
Go to slide 1 div.custom-dots-navigation > ul.slick-dots > li > button
Go to slide 2 div.custom-dots-navigation > ul.slick-dots > li.slick-active > button
Go to slide 3 div.custom-dots-navigation > ul.slick-dots > li > 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
●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.
●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.
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Elements with visible text labels have matching accessible names.
○`[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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○`<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
○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