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 2 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

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

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 ✗

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title University of Kansas logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h1 TOWERING TOWARD THE BLUE

2.82:1

#000000

#555556

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Join the Commencement celebration

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 KU statistics

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Second brag section

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Serving Kansas and beyond

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Fourth brag banner

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Jayhawks making headlines

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Third brag banner

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The space to create. The resources to in…

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 From great heights, Rock Chalk echoes fo…

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 KU pursuits boost Kansas and the Midwest…

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Onward: Toward Infinite Possibility

2.82:1

#000000

#555556

needs 3.0:1 (large text)

24px · bottom of viewport

title Explore the home of the Jayhawks | The U…

2.89:1

#000000

#0051BA

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

2.19:1

#000000

#01477B

needs 4.5:1 (normal text)

16px · top of page (header area)

span The University

2.69:1

#000000

#005688

needs 4.5:1 (normal text)

16px · above the fold

span Kansas

3.55:1

#000000

#2D6993

needs 4.5:1 (normal text)

16px · above the fold

span MENU

1.94:1

#000000

#373D4F

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 TOWERING TOWARD THE …	2.82:1	3.0:1	#000000	#555556	Fail
h2 Join the Commencemen…	2.82:1	3.0:1	#000000	#555556	Fail
h2 KU statistics	2.82:1	3.0:1	#000000	#555556	Fail
h2 Second brag section	2.82:1	3.0:1	#000000	#555556	Fail
h2 Serving Kansas and b…	2.82:1	3.0:1	#000000	#555556	Fail
h2 Fourth brag banner	2.82:1	3.0:1	#000000	#555556	Fail
h2 Jayhawks making head…	2.82:1	3.0:1	#000000	#555556	Fail
h2 Third brag banner	2.82:1	3.0:1	#000000	#555556	Fail
h2 The space to create.…	2.82:1	3.0:1	#000000	#555556	Fail
h2 From great heights, …	2.82:1	3.0:1	#000000	#555556	Fail
h2 KU pursuits boost Ka…	2.82:1	3.0:1	#000000	#555556	Fail
h2 Onward: Toward Infin…	2.82:1	3.0:1	#000000	#555556	Fail
title Explore the home of …	2.89:1	4.5:1	#000000	#0051BA	Fail
p This website uses co…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	9.53:1	4.5:1	#000000	#99B2C5	Pass
a Skip to main content	2.19:1	4.5:1	#000000	#01477B	Fail
span The University	2.69:1	4.5:1	#000000	#005688	Fail
span Kansas	3.55:1	4.5:1	#000000	#2D6993	Fail
span MENU	1.94:1	4.5:1	#000000	#373D4F	Fail
span THE UNIVERSITY	8.44:1	4.5:1	#000000	#A2A4AC	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

12 headings

PASS

12 headings

Single H1 present

H1 TOWERING TOWARD THE BLUE
H2 Join the Commencement celebration
H2 KU statistics
H2 Second brag section
H2 Serving Kansas and beyond
H2 Fourth brag banner
H2 Jayhawks making headlines
H2 Third brag banner
H2 The space to create. The resources to inspire.
H2 From great heights, Rock Chalk echoes for all to hear.
H2 KU pursuits boost Kansas and the Midwest.
H2 Onward: Toward Infinite Possibility

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

7 image(s) with alt text over 125 characters

5 image(s) with good alt text

12 images 5 good alt text

Issue	Count
too long	7 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#kute-search-form-block--2--input	text	Search this unit	for/id

Link & Button Quality

1 issue(s) across 82 links and 7 buttons

PASS

1 issue(s) across 82 links and 7 buttons

1 link(s) with no accessible text

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

Got: a#main-content

81 link(s) with descriptive text

82 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label

88 links and buttons have descriptive text

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

a#main-content

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

A+

Lighthouse Accessibility Audits

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

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

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

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

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