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

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

title Home | University of Kentucky

1.98:1

#000000

#0033A0

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main

1.98:1

#000000

#0033A0

needs 4.5:1 (normal text)

16px · top of page (header area)

a University of Kentucky

1.98:1

#000000

#0033A0

needs 4.5:1 (normal text)

16px · top of page (header area)

div University-wide Navigation

1.01:1

#000000

#020207

needs 4.5:1 (normal text)

16px · top of page (header area)

a Resources

1.09:1

#000000

#0E0D19

needs 4.5:1 (normal text)

16px · above the fold

a Alumni

1.38:1

#000000

#351E32

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Apply

1.18:1

#000000

#10162E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a BBNvolved

1.27:1

#000000

#231C2C

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Calendar

1.58:1

#000000

#1F2C5E

needs 4.5:1 (normal text)

16px · above the fold

a Canvas

1.58:1

#000000

#1E2C60

needs 4.5:1 (normal text)

16px · above the fold

a Directory

1.59:1

#000000

#1D2C61

needs 4.5:1 (normal text)

16px · above the fold

a Faculty & Staff

1.59:1

#000000

#1D2C62

needs 4.5:1 (normal text)

16px · above the fold

a Give

1.59:1

#000000

#1C2C63

needs 4.5:1 (normal text)

16px · above the fold

a Graphic Standards

1.59:1

#000000

#1C2C64

needs 4.5:1 (normal text)

16px · mid-page

a Jobs

1.61:1

#000000

#1B2D66

needs 4.5:1 (normal text)

16px · mid-page

a Libraries

1.62:1

#000000

#1A2D67

needs 4.5:1 (normal text)

16px · mid-page

a linkblue

1.62:1

#000000

#1A2D68

needs 4.5:1 (normal text)

16px · mid-page

a Registrar

1.62:1

#000000

#192D69

needs 4.5:1 (normal text)

16px · mid-page

a Severe Weather Procedures

1.62:1

#000000

#192D6A

needs 4.5:1 (normal text)

16px · mid-page

a Site Index

1.63:1

#000000

#182D6C

needs 4.5:1 (normal text)

16px · mid-page

3 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
title Home \| University of…	1.98:1	4.5:1	#000000	#0033A0	Fail
a Skip to main	1.98:1	4.5:1	#000000	#0033A0	Fail
a University of Kentuc…	1.98:1	4.5:1	#000000	#0033A0	Fail
div University-wide Navi…	1.01:1	4.5:1	#000000	#020207	Fail
a Resources	1.09:1	4.5:1	#000000	#0E0D19	Fail
a Alumni	1.38:1	4.5:1	#000000	#351E32	Fail
a Apply	1.18:1	4.5:1	#000000	#10162E	Fail
a BBNvolved	1.27:1	4.5:1	#000000	#231C2C	Fail
a Calendar	1.58:1	4.5:1	#000000	#1F2C5E	Fail
a Canvas	1.58:1	4.5:1	#000000	#1E2C60	Fail
a Directory	1.59:1	4.5:1	#000000	#1D2C61	Fail
a Faculty & Staff	1.59:1	4.5:1	#000000	#1D2C62	Fail
a Give	1.59:1	4.5:1	#000000	#1C2C63	Fail
a Graphic Standards	1.59:1	4.5:1	#000000	#1C2C64	Fail
a Jobs	1.61:1	4.5:1	#000000	#1B2D66	Fail
a Libraries	1.62:1	4.5:1	#000000	#1A2D67	Fail
a linkblue	1.62:1	4.5:1	#000000	#1A2D68	Fail
a Registrar	1.62:1	4.5:1	#000000	#192D69	Fail
a Severe Weather Proce…	1.62:1	4.5:1	#000000	#192D6A	Fail
a Site Index	1.63:1	4.5:1	#000000	#182D6C	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.

A+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

21 headings

PASS

21 headings

Multiple H1 headings (9 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H2 Megamenu
H1 About UK
H1 Academics duplicate H1
H1 Admissions duplicate H1
H1 Athletics duplicate H1
H1 Current Students duplicate H1
H1 Research duplicate H1
H1 UK HealthCare duplicate H1
H1 DanceBlue: A TRADITION THAT MOVES US duplicate H1
H1 Discovery Advancing the Commonwealth duplicate H1
H2 IN THE NEWS
H3 University of Kentucky Leads the Way in Responsible AI with Microsoft Partnership
H3 Finding Passion and Purpose
H3 Working Together to Advance Kentucky
H2 PROSPECTIVE STUDENTS
H2 EXPLORE YOUR WILDEST AMBITIONS
H2 By The Numbers
H3 $7.6 Billion
H3 1 of 8
H3 3.68
H2 Follow us on social media

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

2 decorative image(s) correctly marked

3 image(s) with good alt text

5 images 3 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-keywords-69e7e1d94c1de	text	Search our Site	for/id
#search-keywords-69e7e1d9f1cfa	text	Search our Site	for/id

A+

Link & Button Quality

265 links, 5 buttons — all OK

PASS

265 links, 5 buttons — all OK

265 link(s) with descriptive text

265 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

270 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○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

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

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