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

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Search Icon ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

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

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, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA 1 pass AA only

a Visit

1.46:1

#000000

#491D0C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Apply

1.67:1

#000000

#592313

needs 4.5:1 (normal text)

16px · above the fold

a Give

2.10:1

#000000

#732C11

needs 4.5:1 (normal text)

16px · above the fold

div Search

1.29:1

#000000

#2E1C14

needs 4.5:1 (normal text)

16px · above the fold

div Close

3.55:1

#000000

#676177

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 WELCOME TO ROCKY TOP	8.45:1	3.0:1	#000000	#FF8200	Pass
h2 Programs you’re lo…	8.45:1	3.0:1	#000000	#FF8200	Pass
h2 Welcome home	8.45:1	3.0:1	#000000	#FF8200	Pass
h2 Come see us	8.45:1	3.0:1	#000000	#FF8200	Pass
h2 Invest in your succe…	8.45:1	3.0:1	#000000	#FF8200	Pass
h2 The Volunteer spirit	8.45:1	3.0:1	#000000	#FF8200	Pass
h2 Become a Volunteer	8.45:1	3.0:1	#000000	#FF8200	Pass
h3 A selfless act	8.45:1	3.0:1	#000000	#FF8200	Pass
h3 A role model	8.45:1	3.0:1	#000000	#FF8200	Pass
h3 Tools	8.45:1	3.0:1	#000000	#FF8200	Pass
h3 Campus Links	8.45:1	3.0:1	#000000	#FF8200	Pass
title University of Tennes…	14.44:1	4.5:1	#000000	#FFCD99	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Request Info	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Visit	1.46:1	4.5:1	#000000	#491D0C	Fail
a Apply	1.67:1	4.5:1	#000000	#592313	Fail
a Give	2.10:1	4.5:1	#000000	#732C11	Fail
div Search	1.29:1	4.5:1	#000000	#2E1C14	Fail
div Close	3.55:1	4.5:1	#000000	#676177	Fail
label Search	6.70:1	4.5:1	#000000	#C8805C	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

3 landmarks

PASS

3 landmarks

<main> landmark present

No <nav> landmark found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H1 WELCOME TO ROCKY TOP
H2 Programs you’re looking for
H2 Welcome home
H2 Come see us
H2 Invest in your success
H2 The Volunteer spirit
H3 A selfless act
H3 A role model
H2 Become a Volunteer
H3 Tools
H3 Campus Links

Alt Text Quality

All 19 images OK

PASS

All 19 images OK

7 image(s) with alt text over 125 characters

2 decorative image(s) correctly marked

10 image(s) with good alt text

19 images 10 good alt text 2 decorative

Issue	Count
too long	7 image(s)

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
#site-search-field-slider	search	Search this site	aria-label
#site-search-field-slider	search	Search this site	aria-label

Link & Button Quality

81 links, 11 buttons — all OK

PASS

81 links, 11 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://tennessee.edu/; https://www.tntransferpathway.org/

79 link(s) with descriptive text

81 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://tennessee.edu/	University of Tennessee System	new tab	Add '(opens in new tab)' to text
https://www.tntransferpathway.org/	Tennessee Transfer Pathway	new tab	Add '(opens in new tab)' to text

90 links and buttons have descriptive text

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

https://tennessee.edu/; https://www.tntransferpathway.org/

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

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

●`<frame>` or `<iframe>` elements have a title

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

●ARIA IDs are unique

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

○No form fields have multiple labels

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

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