Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Link & Button Quality

Action

5 issue(s) across 79 links and 8 buttons

FIX

5 issue(s) across 79 links and 8 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.umkc.edu/; https://www.umkc.edu/

13 link(s) open in new tab without warning

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

Got: https://www.umkcfoundation.org/; https://www.facebook.com/UMKC; https://www.twitter.com/UMKC; https://www.instagram.com/umkcinkansascity/; https://www.youtube.com/user/UMKC; https://www.linkedin.com/school/umkc/; https://www.tiktok.com/@umkc_roos; https://umkc.umsystem.edu/; https://umsystem.instructure.com/; https://umkc.starfishsolutions.com/starfish-ops/support/login.html (+3 more)

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.o-btn (#214 on page); button.aa-SubmitButton (#396 on page); button.aa-ClearButton (#406 on page)

64 link(s) with descriptive text

79 links

2 empty

0 generic text

13 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.umkc.edu/	(empty)	empty	Add link text or aria-label
https://www.umkcfoundation.org/	Dare to Be Bold link opens in…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/UMKC	U.M.K.C. on Facebook. <span cl…	new tab	Add '(opens in new tab)' to text
https://www.twitter.com/UMKC	U.M.K.C. on Twitter. <span cla…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/umkcinkansasci…	U.M.K.C. on Instagram. <span c…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/UMKC	U.M.K.C. on YouTube. <span cla…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/umkc/	U.M.K.C. on Linked In. <span c…	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@umkc_roos	U.M.K.C. on TikTok. <span clas…	new tab	Add '(opens in new tab)' to text
https://www.umkc.edu/	(empty)	empty	Add link text or aria-label
https://umkc.umsystem.edu/	Pathway link opens in a new t…	new tab	Add '(opens in new tab)' to text
https://umsystem.instructure.com/	Canvas link opens in a new ta…	new tab	Add '(opens in new tab)' to text
https://umkc.starfishsolutions.com/starf…	UMKC Connect link opens in a …	new tab	Add '(opens in new tab)' to text
https://www.umsystem.edu	© 2026 Curators of the Unive…	new tab	Add '(opens in new tab)' to text
https://www.umsystem.edu/ums/copyright/	DMCA Policy link opens in a n…	new tab	Add '(opens in new tab)' to text
https://www.umsystem.edu/ums/hr/eeo	equal opportunity employer	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

69 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.umkc.edu/; https://www.umkc.edu/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.umkcfoundation.org/; https://www.facebook.com/UMKC; https://www.twitter.com/UMKC; https://www.instagram.com/umkcinkansascity/; https://www.youtube.com/user/UMKC; https://www.linkedin.com/school/umkc/; https://www.tiktok.com/@umkc_roos; https://umkc.umsystem.edu/; https://umsystem.instructure.com/; https://umkc.starfishsolutions.com/starfish-ops/support/login.html (+3 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.o-btn (#214 on page); button.aa-SubmitButton (#396 on page); button.aa-ClearButton (#406 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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: strategic marketing and communications | university of missouri kansas city

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 ✗

Heading Hierarchy

25 headings

REVIEW

25 headings

No H1 heading found

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

H2 Choose Blue. Choose Bold.
H3 Release the Potential in Every Roo
H3 Transform Discovery for the Challenges of the Future
H3 Create Servant Leadership for a Better World
H2 Wall Street Journal Ranks UMKC in Top Spots — Again
H2 No. 1
H3 Student Experience
H2 No. 1
H3 Social Mobility
H2 No. 2
H3 Best Value
H2 Blaze New Trails
H2 Kansas City’s Only R1 University
H3 Research awards
H3 Research and development spending
H3 Community impact
H3 Jobs supported
H2 A Place to Connect
H2 14 Years of Top Rankings for UMKC Online Graduate Nursing Program
H3 Wyatt Boyd, urban planning and design student
H2 All Aboard, Roos!
H2 Featured Events
H2 Hungry for More?
H2 University of Missouri-Kansas City
H2 Helpful Links

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

Alt Text Quality

2 of 9 images have issues

REVIEW

2 of 9 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 decorative image(s) correctly marked

9 images 7 decorative 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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 U.M.K.C. on TikTok. <span class="sr-only"> link opens in a new tab</span> ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

A+

Landmark Structure

15 landmarks

PASS

15 landmarks

<main> landmark present

11 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" id="autocomplete-0-input">

1 control(s) properly labeled

2 controls

1 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#q	input	Search UMKC.edu:	for/id
#autocomplete-0-input	search	(Find your program)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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)

Element	Ratio	Required	FG	BG	Result
h2 Choose Blue. Choose …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Wall Street Journal …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 No. 1	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 No. 1	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 No. 2	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Blaze New Trails	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Kansas City’s Only…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 A Place to Connect	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 14 Years of Top Rank…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 All Aboard, Roos!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Featured Events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Hungry for More?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 University of Missou…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Helpful Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Release the Potentia…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Transform Discovery …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Create Servant Leade…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Student Experience	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Social Mobility	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Best Value	21.00:1	3.0:1	#000000	#FFFFFF	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 29 passed

PASS

100

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.

○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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

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

○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

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

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

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