Skip to content
https://mtu.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
3
PASS
9
INFO
0
Checks
13
9 PASS 3 REVIEW 1 FIX
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
Favicon & Branding
16 icon(s) detected
REVIEW
16 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode Dark Mode Supported
color-scheme meta Not set Dark theme-color #000000 CSS indicators Detected

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Michigan Technological University
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Degrees for What Tomorrow Needs
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Academics
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Request Information
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The Tech Difference
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Come Home to Houghton
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Spring Commencement
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Summer Youth Programs
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Chang K. Park Center for Student Wellnes…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest News and Stories
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Events
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stay Connected
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Admissions
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Study and Live
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Campus Info
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Policies and Safety
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Michigan Technological University
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
title Michigan Technological University
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to page content
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to footer navigation
2.19:1
#000000
on
#374562
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 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 Michigan Technologic…1.00:13.0:1
#000000
#000000
Fail
h2 Degrees for What Tom…1.00:13.0:1
#000000
#000000
Fail
h2 Academics1.00:13.0:1
#000000
#000000
Fail
h2 Request Information1.00:13.0:1
#000000
#000000
Fail
h2 The Tech Difference1.00:13.0:1
#000000
#000000
Fail
h2 Come Home to Houghto…1.00:13.0:1
#000000
#000000
Fail
h2 Spring Commencement1.00:13.0:1
#000000
#000000
Fail
h2 Summer Youth Program…1.00:13.0:1
#000000
#000000
Fail
h2 Chang K. Park Center…1.00:13.0:1
#000000
#000000
Fail
h2 Latest News and Stor…1.00:13.0:1
#000000
#000000
Fail
h2 Featured Events1.00:13.0:1
#000000
#000000
Fail
h2 Stay Connected1.00:13.0:1
#000000
#000000
Fail
h2 Admissions1.00:13.0:1
#000000
#000000
Fail
h2 Study and Live1.00:13.0:1
#000000
#000000
Fail
h2 Campus Info1.00:13.0:1
#000000
#000000
Fail
h2 Policies and Safety1.00:13.0:1
#000000
#000000
Fail
h2 Michigan Technologic…1.00:13.0:1
#000000
#000000
Fail
title Michigan Technologic…1.00:14.5:1
#000000
#000000
Fail
a Skip to page content1.00:14.5:1
#000000
#000000
Fail
a Skip to footer navig…2.19:14.5:1
#000000
#374562
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
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 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
21 headings
PASS
21 headings
Info::
Single H1 present
  • H1 Michigan Technological University
  • H2 Degrees for What Tomorrow Needs
  • H2 Academics
  • H2 Request Information
  • H2 The Tech Difference
  • H2 R1
  • H2 No. 3
  • H2 $82K
  • H2 7,400+
  • H2 Come Home to Houghton
  • H2 Spring Commencement
  • H2 Summer Youth Programs
  • H2 Chang K. Park Center for Student Wellness
  • H2 Latest News and Stories
  • H2 Featured Events
  • H2 Stay Connected
  • H2 Admissions
  • H2 Study and Live
  • H2 Campus Info
  • H2 Policies and Safety
  • H2 Michigan Technological University
A
Alt Text Quality
All 31 images OK
PASS
All 31 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
6 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
31 images 22 good alt text 6 decorative
IssueCount
too long3 image(s)
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#desktop-searchsearchSearchfor/id
#search-optionsselectSearch Categoryfor/id
#mobile-searchsearchSearchfor/id
#mobile-search-optionsselectSearch Categoryfor/id
#combobox_input_9w8djvn19aqtextFind a degree program...none
#emailtextEmailnone
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404 Not Found Custom Styling Navigation Homepage Link Search Form
A
Web Manifest
Valid manifest
PASS
Valid manifest
Info::
Name present: Michigan Technological University
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Michigan Technological University 192×192 icon 512×512 icon Start URL ./ Display Mode browser
Name Michigan Technological University Display Mode browser Theme Color #000000 Background Color #000000 Icons 9 icon(s)
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: //www.mtu.edu/mtu_resources/styles/n/print.css
Print Stylesheet Print Optimized
Print stylesheet //www.mtu.edu/mtu_resources/styles/n/print.css Inline @media print Not detected
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 28 passed
PASS
97

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

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
Previous Image div.mtuslideshow > div.content > div.navigator > a.goto
Image 1 div.mtuslideshow > div.content > div.navigator > a.goto
Image 2 div.mtuslideshow > div.content > div.navigator > a.goto
Image 3 div.mtuslideshow > div.content > div.navigator > a.goto
Image 4 div.mtuslideshow > div.content > div.navigator > a.goto
Image 5 div.mtuslideshow > div.content > div.navigator > a.goto
Image 6 div.mtuslideshow > div.content > div.navigator > a.goto
Image 7 div.mtuslideshow > div.content > div.navigator > a.goto
Image 8 div.mtuslideshow > div.content > div.navigator > a.goto
Next Image div.mtuslideshow > div.content > div.navigator > a.goto

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