Skip to content
https://missouri.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
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::
2 navigation landmark(s) detected
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
12 headings
REVIEW
12 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Search
  • H2 ACADEMIC EXCELLENCE SINCE 1839
  • H2 We Know You’ve Got What It Takes
  • H2 Academics at Mizzou
  • H3 With more than 300 degree programs, Mizzou is the place to build your future — your way.
  • H2 A Tiger’s-Eye View
  • H2 Mizzou Living
  • H3 Explore your future home.
  • H2 Why Mizzou?
  • H2 M-I-Z!   Z-O-U!
  • H2 Earn Your Stripes
  • H3 Become part of a legacy of excellence.

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 instagram icon Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA 1 pass AA only
title Homepage | Mizzou
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Request Info
1.07:1
#000000
on
#0D0B0C
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Search21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ACADEMIC EXCELLENCE…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We Know You’ve Got…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Academics at Mizzou21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A Tiger’s-Eye View21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mizzou Living21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why Mizzou?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 M-I-Z!   Z-O-U!21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Earn Your Stripes21.00:13.0:1
#000000
#FFFFFF
Pass
h3 With more than 300 d…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Explore your future …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Become part of a leg…21.00:13.0:1
#000000
#FFFFFF
Pass
title Homepage | Mizzou1.00:14.5:1
#000000
#000000
Fail
a Skip to main content1.00:14.5:1
#000000
#000000
Fail
a Request Info1.07:14.5:1
#000000
#0D0B0C
Fail
a Apply4.51:14.5:1
#000000
#72728E
Pass
a Visit9.98:14.5:1
#000000
#B1AFD7
Pass
a Give10.89:14.5:1
#000000
#BEB6DA
Pass
button Info For11.13:14.5:1
#000000
#C1B8D9
Pass
a Current Students12.45:14.5:1
#000000
#CEC3DB
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 23 passed
REVIEW
89

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.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Address City, State, Zip Code City Columbia State MO Zip Code 65211 Telephone n… div.miz-card > div.miz-card__body > div.miz-link-container > dl.miz-contact-point

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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.mizzou-header-content > div.mizzou-header__masthead > p.miz-masthead__title > a.miz-masthead__title-link div.mizzou-header-content > div.mizzou-header__masthead > p.miz-masthead__title > a.miz-masthead__title-link
div.miz-social-media > ul.miz-social-media-list > li.miz-social-media-list__item > a.miz-social-media-list__link div.miz-social-media > ul.miz-social-media-list > li.miz-social-media-list__item > a.miz-social-media-list__link
div.miz-social-media > ul.miz-social-media-list > li.miz-social-media-list__item > a.miz-social-media-list__link div.miz-social-media > ul.miz-social-media-list > li.miz-social-media-list__item > a.miz-social-media-list__link
div.miz-social-media > ul.miz-social-media-list > li.miz-social-media-list__item > a.miz-social-media-list__link div.miz-social-media > ul.miz-social-media-list > li.miz-social-media-list__item > a.miz-social-media-list__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.

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
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a
div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a div.miz-card__body > ul.miz-link-list > li.miz-link-list__item > a

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
`[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
Definition list items are wrapped in `<dl>` elements
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
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 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
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.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
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.
A
Landmark Structure
6 landmarks
PASS
6 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+
Alt Text Quality
All 15 images OK
PASS
All 15 images OK
Info::
15 image(s) with good alt text
15 images 15 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-inputtextSearchfor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_5cEmsVzJybnGCmsHLIKOY0CElTjb9XUMnLOE772mMsg.css?delta=4&language=en&theme=miz_missouri_edu_subtheme&include=eJyVkutuhCAQhV9I5W_fhgww2ukCYxjY1n36gpr0Eo27iUHQby6cOeBcZoiLgn0zjIlj7gzYm85cn1n92muyHDvLCZXlMHPEmGUI9NA_x763kNw1VMuAzf3MVOtd0Q4rAZmeqD7SVBJeY8wZ0yX2juCewDzFW13k-iYBJLekl2AiY06uG0iESyKNrmgppiYM2HpN3L9zwBmmYwFOAgM6gj6wA_9S2KsBwpbAb-Veist19JLJbkEulRn8AB_w1XlYuGTtSCzfMS2qZrPsu7WGYgwG3TByCpDbuP-KrNpxy3Dw58FFOxSaopZFMgZtEkS3ku5Nr71pA4LH8FgNLs_C4ikcsJIXj1uSQ2nU7uJzYPJs6pDOgd3gm1JVjMfiGVwbTKju-_dZN6mKQbW_u6191Zrt7oSfotZ1qNYoHr8BK126bQ
Print Stylesheet Print Optimized
Print stylesheet /sites/default/files/css/css_5cEmsVzJybnGCmsHLIKOY0CElTjb9XUMnLOE772mMsg.css?delta=4&language=en&theme=miz_missouri_edu_subtheme&include=eJyVkutuhCAQhV9I5W_fhgww2ukCYxjY1n36gpr0Eo27iUHQby6cOeBcZoiLgn0zjIlj7gzYm85cn1n92muyHDvLCZXlMHPEmGUI9NA_x763kNw1VMuAzf3MVOtd0Q4rAZmeqD7SVBJeY8wZ0yX2juCewDzFW13k-iYBJLekl2AiY06uG0iESyKNrmgppiYM2HpN3L9zwBmmYwFOAgM6gj6wA_9S2KsBwpbAb-Veist19JLJbkEulRn8AB_w1XlYuGTtSCzfMS2qZrPsu7WGYgwG3TByCpDbuP-KrNpxy3Dw58FFOxSaopZFMgZtEkS3ku5Nr71pA4LH8FgNLs_C4ikcsJIXj1uSQ2nU7uJzYPJs6pDOgd3gm1JVjMfiGVwbTKju-_dZN6mKQbW_u6191Zrt7oSfotZ1qNYoHr8BK126bQ Inline @media print Not detected
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback