Skip to content
https://miami.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 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.

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.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

B
Alt Text Quality
2 of 48 images have issues
REVIEW
2 of 48 images have issues
Warning::
2 image(s) with filename as alt text
Info::
3 image(s) with alt text over 125 characters
Info::
10 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
48 images 33 good alt text 10 decorative 2 generic
IssueCount
filename2 image(s)
too long3 image(s)
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 University of Miami ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 71/100 — 11 failing, 21 passed
REVIEW
71

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accessibility Options: Skip to Content Skip to Search Skip to footer Office o… div.accessibility-toolbar > div.row > div.small-12 > ul.supernav
Display: Default High Contrast div.accessibility-toolbar > div.row > div.small-12 > ul#color-toggle

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Better Forecasts Save Lives Take a look inside the world's only Category 5 hur… div.sliderMain > div.slick-list > div.slick-track > div#heroCarouselContentAndImg_1
Lakeside Village Opened to students in Fall 2020, Lakeside Village is a 12-acre… div.row > div.slick-list > div.slick-track > div.large-3
Harold Long Jr. and H.T. Smith Student Services Building Students walk past the… div.row > div.slick-list > div.slick-track > div.large-3
Donna E. Shalala Student Center The 120,000-square-foot Donna E. Shalala Studen… div.row > div.slick-list > div.slick-track > div.large-3
Canopy within palm trees Canopies float among the palm trees on the Coral Gable… div.row > div.slick-list > div.slick-track > div.large-3
Sebastian the Ibis A bronze statue of our mascot Sebastian the Ibis welcomes cu… div.row > div.slick-list > div.slick-track > div.large-3
F.G. Walton Smith research vessel The F.G. Walton Smith research vessel sits on… div.row > div.slick-list > div.slick-track > div.large-3
‘Fate’ Accompli “Hey, Mom. Want to build a bridge?” student Hannah Weese asked,… div.row > div.slick-list > div.slick-track > div.large-3
Relax on a Rocker Lush landscapes abound on the University's Coral Gables campu… div.row > div.slick-list > div.slick-track > div.large-3
The Billy Goat Designed and built by 13 UM architecture students during the fal… div.row > div.slick-list > div.slick-track > div.large-3
Endless Shades of Summer Colorful foliage from more than 500 species of flora k… div.row > div.slick-list > div.slick-track > div.large-3
The Rathskeller Sink the 8 ball or savor the mac 'n' cheese bites at The Rathsk… div.row > div.slick-list > div.slick-track > div.large-3
Alfred C. Glassell, Jr. SUSTAIN Building The Alfred C. Glassell, Jr. SUSTAIN Bu… div.row > div.slick-list > div.slick-track > div.large-3
Getting Fit The Patti and Allan Herbert Wellness Center, one of the nation’s la… div.row > div.slick-list > div.slick-track > div.large-3

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Turning campus involvement into career skills Cane Commitment helps undergradu… div.medium-12 > div#um_blog_mobile_carousel_student > div.slick-list > div.slick-track
From business student to thriller writer Alumnus Bryan Michael Richards recent… div.row > div#um_blog_mobile_carousel > div.slick-list > div.slick-track
Lakeside Village Pavilion The Lakeside Village Pavilion is one of the event ven… section#experienceumiami > div.row > div.slick-list > div.slick-track

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEWS div.hero-wrapper > section#home_news_container > div.row > h2.column

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to Content div.small-12 > ul.supernav > li.show-for-sr > a

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
Students get a boost to expand their businesses div.slick-track > div.um-blog-column-mo > div.um-blog-tn-mo > h4
University of Miami div.large-3 > div > div > h5.stagsansmedium

These are opportunities to improve keyboard navigation in your application.

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.hero-wrapper > div.contain-to-grid > div.navbar-header > a.navbar-home-link div.hero-wrapper > div.contain-to-grid > div.navbar-header > a.navbar-home-link

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.

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
Accessibility Options: div.row > div.small-12 > ul.supernav > li
305-284-2374 div.row > div.small-12 > ul.supernav > li
Display: div.row > div.small-12 > ul#color-toggle > li

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
Your emails might be saying more than they have to div.row > div.large-12 > center > a.stagsanssemibold
By University of Miami div.row > div.large-12 > center > a
It’s all sunshine and rainbows at the U div.row > div.large-12 > center > a.stagsanssemibold
By University of Miami div.row > div.large-12 > center > a
Hurricane Sports div.large-3 > ul.no-bullet > li > a.white
University Hotline div.large-3 > ul.no-bullet > li > a.white
UOnline Programs div.large-3 > ul.no-bullet > li > a.white
CaneLink div.large-3 > ul.no-bullet > li > a.white
Blackboard div.large-3 > ul.no-bullet > li > a.white
Workday div.large-3 > ul.no-bullet > li > a.white
Careers div.large-3 > ul.no-bullet > li > a.white

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.js html.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
Pause Slideshow body.home > div.hero-wrapper > section#homepage_hero_slider > button.slick-pause-button
○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]`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
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●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>`).
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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 `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
○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
○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
○`<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.
○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
Heading Hierarchy
63 headings, 1 skip(s)
PASS
63 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 University of Miami
  • H2 Featured Stories
  • H3 Redefining Dementia Research
  • H4 Related Links
  • H3 Better Forecasts Save Lives
  • H4 Related Links
  • H2 NEWS
  • H2 NEWS
  • H3 Lessons from sports leaders
  • H3 El Niño is coming
  • H3 A potential discovery from the dawn of time
  • H3 Lessons from sports leaders
  • H3 El Niño is coming
  • H3 A potential discovery from the dawn of time
  • H2 STUDENT STORIES
  • H3 Students get a boost to expand their businesses
  • H3 Turning campus involvement into career skills
  • H3 Students get a boost to expand their businesses
  • H3 Turning campus involvement into career skills
  • H4 Turning campus involvement into career skills
  • H4 Students get a boost to expand their businesses
  • H4 Turning campus involvement into career skills
  • H4 Students get a boost to expand their businesses
  • H2 U MIAMI ON:
  • H3 T
  • H3 F
  • H3 Y
  • H3 Y
  • H3 T
  • H3 F
  • H3 Y
  • H3 Y
  • H2 ALUMNI STORIES
  • H3 Uplifting generations
  • H3 Championship lessons
  • H3 An artist behind the scenes
  • H3 From business student to thriller writer
  • H3 From business student to thriller writer
  • H3 Uplifting generations
  • H3 Championship lessons
  • H3 An artist behind the scenes
  • H3 From business student to thriller writer
  • H3 Uplifting generations
  • H2 EXPERIENCE U MIAMI
  • H3 Lakeside Village Pavilion
  • H3 Lakeside Village
  • H3 Harold Long Jr. and H.T. Smith Student Services Building
  • H3 Donna E. Shalala Student Center
  • H3 Canopy within palm trees
  • H3 Sebastian the Ibis
  • H3 F.G. Walton Smith research vessel
  • H3 ‘Fate’ Accompli
  • H3 Relax on a Rocker
  • H3 The Billy Goat
  • H3 Endless Shades of Summer
  • H3 The Rathskeller
  • H3 Alfred C. Glassell, Jr. SUSTAIN Building
  • H3 Getting Fit
  • H5 University of Miami skipped
  • H5 UM Network
  • H5 Tools and Resources
  • H5 Visit
  • H5 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

A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#sliverRightSearchtextSearchfor/id
#sliverSearchSmalltextSearch UM (Mobile)for/id
#mobileNavSearchtextSearchfor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: //cdn.miami.edu/_assets-common/css/print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet //cdn.miami.edu/_assets-common/css/print.css ✓Inline @media print Not detected ✗
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 University of Miami19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Featured Stories19.43:13.0:1
#000000
#F6F6F6
Pass
h2 NEWS19.43:13.0:1
#000000
#F6F6F6
Pass
h2 NEWS19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Lessons from sports …19.43:13.0:1
#000000
#F6F6F6
Pass
h3 El Niño is coming19.43:13.0:1
#000000
#F6F6F6
Pass
h3 A potential discover…19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Lessons from sports …19.43:13.0:1
#000000
#F6F6F6
Pass
h3 El Niño is coming19.43:13.0:1
#000000
#F6F6F6
Pass
h3 A potential discover…19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Lakeside Village Pav…19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Lakeside Village19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Harold Long Jr. and …19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Donna E. Shalala Stu…19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Canopy within palm t…19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Sebastian the Ibis19.43:13.0:1
#000000
#F6F6F6
Pass
h3 F.G. Walton Smith re…19.43:13.0:1
#000000
#F6F6F6
Pass
h3 ‘Fate’ Accompli19.43:13.0:1
#000000
#F6F6F6
Pass
h3 Relax on a Rocker19.43:13.0:1
#000000
#F6F6F6
Pass
h3 The Billy Goat19.43:13.0:1
#000000
#F6F6F6
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.

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

Send Feedback