Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://uwm.edu/wp-content/themes/uwmwebid2/manifest.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://uwm.edu/wp-content/themes/uwmwebid2/manifest.webmanifest

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

2 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100001">

1 control(s) properly labeled

3 controls

1 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#search-field	search	Search for:	none
#g-recaptcha-response-100000	textarea	(none)	none
#g-recaptcha-response-100001	textarea	(none)	none

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

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA 1 pass AA only

h1 UW-Milwaukee

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 What can we help you find?

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Make New Waves

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The UWM Experience

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Leading in Research

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 UWM by the Numbers

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hear From Our Panthers

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Student Life

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Spotlight Stories

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Next Steps

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Sidonie

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Brenden

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Yazmin

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

span University of Wisconsin-Milwaukee

1.56:1

#000000

#2D2F30

needs 4.5:1 (normal text)

16px · top of page (header area)

span University of Wisconsin-Milwaukee

3.09:1

#000000

#5A5B5E

needs 4.5:1 (normal text)

16px · above the fold · 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)

Element	Ratio	Required	FG	BG	Result
h1 UW-Milwaukee	1.00:1	3.0:1	#000000	#000000	Fail
h2 What can we help you…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Make New Waves	1.00:1	3.0:1	#000000	#000000	Fail
h2 The UWM Experience	1.00:1	3.0:1	#000000	#000000	Fail
h2 Leading in Research	1.00:1	3.0:1	#000000	#000000	Fail
h2 UWM by the Numbers	1.00:1	3.0:1	#000000	#000000	Fail
h2 Hear From Our Panthe…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Student Life	1.00:1	3.0:1	#000000	#000000	Fail
h2 Spotlight Stories	1.00:1	3.0:1	#000000	#000000	Fail
h2 Next Steps	1.00:1	3.0:1	#000000	#000000	Fail
h3 Sidonie	1.00:1	3.0:1	#000000	#000000	Fail
h3 Brenden	1.00:1	3.0:1	#000000	#000000	Fail
h3 Yazmin	1.00:1	3.0:1	#000000	#000000	Fail
title UW-Milwaukee - Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to footer	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span University of Wiscon…	1.56:1	4.5:1	#000000	#2D2F30	Fail
span University of Wiscon…	3.09:1	4.5:1	#000000	#5A5B5E	Fail
span Site Menu	11.85:1	4.5:1	#000000	#CFC0B4	Pass
button Academics	6.63:1	4.5:1	#000000	#8E9194	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+

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

22 headings

PASS

22 headings

Single H1 present

H2 What can we help you find?
H1 UW-Milwaukee
H2 Make New Waves
H2 The UWM Experience
H2 Leading in Research
H2 UWM by the Numbers
H2 Hear From Our Panthers
H3 Sidonie
H3 Brenden
H3 Yazmin
H2 Student Life
H3 Housing
H3 Athletics
H3 Student Support Services
H3 Health & Wellness
H2 Spotlight Stories
H3 How math and impatient driving inspired student’s award-winning startup
H3 UWM creates strategies for artificial intelligence in the classroom
H3 Using artificial intelligence to tease out answers to health care disparities
H3 Lazarus Project to shine a new light on oldest map in UWM collection
H3 UWM welcomes largest freshman class since 2009
H2 Next Steps

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

2 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

13 image(s) with good alt text

16 images 13 good alt text 1 decorative

Issue	Count
too long	2 image(s)

A+

Link & Button Quality

118 links, 16 buttons — all OK

PASS

118 links, 16 buttons — all OK

118 link(s) with descriptive text

118 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

134 links and buttons have descriptive text

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - UW-Milwaukee ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 25 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

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

●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

●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

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

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

○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

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

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