Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Link & Button Quality

Action

9 issue(s) across 116 links and 22 buttons

FIX

9 issue(s) across 116 links and 22 buttons

6 link(s) with no accessible text

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

Got: https://www.facebook.com/illinois.edu; https://www.instagram.com/illinois1867; https://x.com/uofillinois; http://linkedin.com/edu/school?id=18321; http://youtube.com/user/Illinois1867; https://www.tiktok.com/@uofillinois

1 link(s) open in new tab without warning

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

Got: https://airtable.com/appPOMTGwK7Lmsk3d/pag419Wp9uGnLW1Vn/form

3 button(s) with no accessible text

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

Got: button#search-button; button.slider__previous-button (#473 on page); button.slider__next-button (#477 on page)

109 link(s) with descriptive text

116 links

6 empty

0 generic text

1 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/illinois.edu	(empty)	empty	Add link text or aria-label
https://www.instagram.com/illinois1867	(empty)	empty	Add link text or aria-label
https://x.com/uofillinois	(empty)	empty	Add link text or aria-label
http://linkedin.com/edu/school?id=18321	(empty)	empty	Add link text or aria-label
http://youtube.com/user/Illinois1867	(empty)	empty	Add link text or aria-label
https://www.tiktok.com/@uofillinois	(empty)	empty	Add link text or aria-label
https://airtable.com/appPOMTGwK7Lmsk3d/p…	Website Feedback	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

128 links and buttons have descriptive text

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

https://www.facebook.com/illinois.edu; https://www.instagram.com/illinois1867; https://x.com/uofillinois; http://linkedin.com/edu/school?id=18321; http://youtube.com/user/Illinois1867; https://www.tiktok.com/@uofillinois

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://airtable.com/appPOMTGwK7Lmsk3d/pag419Wp9uGnLW1Vn/form

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#search-button; button.slider__previous-button (#473 on page); button.slider__next-button (#477 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

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 ✗

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Search functionality detected

Got: role-search

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Form Accessibility

3 of 3 controls have issues

REVIEW

3 of 3 controls have issues

3 control(s) rely on placeholder only

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

Got: <input type="search" name="s">; <input type="search" name="s">; <input type="search" name="s">

3 controls

0 labeled

3 placeholder only

0 unlabeled

Control	Type	Label	Method
s	search	(Search this site)	placeholder only
s	search	(Search this site)	placeholder only
s	search	(Search this site)	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

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA 2 pass AA only

h1 University of Illinois Urbana-Champaign …

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Leading the Future

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Learn about Illinois

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Discover Illinois News

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Experience Our Community

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Need help finding something?

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Champaign-Urbana

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Krannert Art Museum

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Spurlock Museum

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Krannert Center for the Performing Arts

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

h3 University Library

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cultural Centers

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Explore Campus

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Connect with Illinois

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Access University Resources

1.36:1

#000000

#1C2534

needs 3.0:1 (large text)

19px · bottom of viewport

title Illinois

3.84:1

#000000

#7E6455

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Apply

1.82:1

#000000

#3D3A20

needs 4.5:1 (normal text)

16px · top of page (header area)

a Give

2.48:1

#000000

#544D2F

needs 4.5:1 (normal text)

16px · above the fold

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 University of Illino…	1.36:1	3.0:1	#000000	#1C2534	Fail
h2 Leading the Future	1.36:1	3.0:1	#000000	#1C2534	Fail
h2 Learn about Illinois	1.36:1	3.0:1	#000000	#1C2534	Fail
h2 Discover Illinois Ne…	1.36:1	3.0:1	#000000	#1C2534	Fail
h2 Experience Our Commu…	1.36:1	3.0:1	#000000	#1C2534	Fail
h2 Need help finding so…	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 Champaign-Urbana	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 Krannert Art Museum	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 Spurlock Museum	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 Krannert Center for …	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 University Library	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 Cultural Centers	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 Explore Campus	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 Connect with Illinoi…	1.36:1	3.0:1	#000000	#1C2534	Fail
h3 Access University Re…	1.36:1	3.0:1	#000000	#1C2534	Fail
title Illinois	3.84:1	4.5:1	#000000	#7E6455	Fail
span University of Illino…	5.17:1	4.5:1	#000000	#7E7E7E	Pass
a Visit	5.17:1	4.5:1	#000000	#7E7E7E	Pass
a Apply	1.82:1	4.5:1	#000000	#3D3A20	Fail
a Give	2.48:1	4.5:1	#000000	#544D2F	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.

Landmark Structure

16 landmarks

PASS

16 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Search landmark present

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 University of Illinois Urbana-Champaign Home
H2 Leading the Future
H2 Start your
H2 Cancer Center at Illinois earns prestigious National Cancer Institute designation
H2 Illini Success report highlights increase in employment, starting salaries for recent Illinois grads
H2 Illinois recognized for excellence in global engagement
H2 Learn about Illinois
H2 Resources
H2 Discover Illinois News
H2 Experience Our Community
H3 Champaign-Urbana
H3 Krannert Art Museum
H3 Spurlock Museum
H3 Krannert Center for the Performing Arts
H3 University Library
H3 Cultural Centers
H2 Need help finding something?
H3 Explore Campus
H3 Connect with Illinois
H3 Access University Resources

Alt Text Quality

All 58 images OK

PASS

All 58 images OK

3 image(s) with alt text over 125 characters

42 decorative image(s) correctly marked

13 image(s) with good alt text

58 images 13 good alt text 42 decorative

Issue	Count
too long	3 image(s)

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 Illinois Logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 28 passed

PASS

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.

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
header.header > div.header__top > div.header-menu__wrapper > a.header__home-link `header.header > div.header__top > div.header-menu__wrapper > a.header__home-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.

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

●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

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

●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

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