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

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 ✗

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

4 <nav> landmark(s) found

1 of 4 <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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

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 magnifying glass ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 20 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 University of Cincin…	4.20:1	3.0:1	#000000	#E00122	Pass
h2 What are you interes…	4.20:1	3.0:1	#000000	#E00122	Pass
h2 There’s before you…	4.20:1	3.0:1	#000000	#E00122	Pass
h2 Lifelong Return on I…	4.20:1	3.0:1	#000000	#E00122	Pass
h2 Your	4.20:1	3.0:1	#000000	#E00122	Pass
h2 Career	4.20:1	3.0:1	#000000	#E00122	Pass
h2 Starts	4.20:1	3.0:1	#000000	#E00122	Pass
h2 Here.	4.20:1	3.0:1	#000000	#E00122	Pass
h2 Next	4.20:1	3.0:1	#000000	#E00122	Pass
h2 lives	4.20:1	3.0:1	#000000	#E00122	Pass
h2 here.	4.20:1	3.0:1	#000000	#E00122	Pass
h2 Our home.	4.20:1	3.0:1	#000000	#E00122	Pass
h2 Our city.	4.20:1	3.0:1	#000000	#E00122	Pass
h2 University of Cincin…	4.20:1	3.0:1	#000000	#E00122	Pass
h2 UC Tools	4.20:1	3.0:1	#000000	#E00122	Pass
h2 About Us	4.20:1	3.0:1	#000000	#E00122	Pass
h3 No programs to show.…	4.20:1	3.0:1	#000000	#E00122	Pass
h3 An Affordable Path t…	4.20:1	3.0:1	#000000	#E00122	Pass
h3 The Leader in Cooper…	4.20:1	3.0:1	#000000	#E00122	Pass
h3 Bearcats for Life	4.20:1	3.0:1	#000000	#E00122	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+

Heading Hierarchy

18 headings

PASS

18 headings

Single H1 present

H1 University of Cincinnati: Founder of Co-op, Leader in Co-op
H2 What are you interested in?
H3 No programs to show. Try Broadening Your Search
H2 There’s before you become a Bearcat, and there’s after.
H2 Lifelong Return on Investment
H3 An Affordable Path to Achievement
H3 The Leader in Cooperative Education
H3 Bearcats for Life
H2 YourCareerStartsHere.
H2 Next lives here.
H2 Our home.Our city.
H2 University of Cincinnati News
H3 UC students engineer possibilities at Kaleidoscope
H3 Bringing deadly ‘Sweeney Todd’ to life
H3 Mayor calls these UC students 'history makers'
H3 From spilled milk to super-resolution microscopy
H2 UC Tools
H2 About Us

Alt Text Quality

1 of 11 images have issues

PASS

1 of 11 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

10 image(s) with good alt text

11 images 10 good alt text 1 missing

Issue	Count
missing	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Form Accessibility

1 of 31 controls have issues

PASS

1 of 31 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

30 control(s) properly labeled

31 controls

30 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search	text	Search	aria-label
#program-finder-keyword	text	Keywords	for/id
#degree-associates	checkbox	Associates	for/id
#degree-bachelors	checkbox	Bachelors	for/id
#degree-uc	checkbox	Minors and Certificates	for/id
#degree-masters	checkbox	Masters	for/id
#degree-doctoral	checkbox	Doctoral	for/id
#degree-gc	checkbox	Graduate Certificate	for/id
#ARCH	checkbox	Architecture, Construction and Building Trade	for/id
#BHAV	checkbox	Behavioral & Social Science	for/id
#BUSS	checkbox	Business	for/id
#COMP	checkbox	Computers & Technology	for/id
#CULT	checkbox	Culture & Languages	for/id
#DSGN	checkbox	Design	for/id
#EDUC	checkbox	Education	for/id
#ENGI	checkbox	Engineering	for/id
#HUMA	checkbox	Humanities	for/id
#MEDI	checkbox	Medicine & Health	for/id
#NATU	checkbox	Natural Science & Math	for/id
#PERF	checkbox	Performing Arts & Music	for/id
#PLAN	checkbox	Planning	for/id
#POLI	checkbox	Politics, Law & Social Justice	for/id
#SOCS	checkbox	Social Science	for/id
#ARTS	checkbox	Arts	for/id
#COOP	checkbox	Co-Op	for/id
#UC Blue Ash	checkbox	UC Blue Ash	for/id
#UC Clermont	checkbox	UC Clermont	for/id
#West Campus	checkbox	West Campus	for/id
#East Campus	checkbox	East Campus	for/id
#Online	checkbox	Online	for/id
input	submit	(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

Link & Button Quality

1392 links, 345 buttons — all OK

PASS

1392 links, 345 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://www.facebook.com/uofcincinnati; http://twitter.com/uofcincy; https://www.instagram.com/uofcincy; https://www.youtube.com/user/uofcincinnati; https://www.linkedin.com/edu/school?id=19141; https://www.tiktok.com/@uofcincy

1386 link(s) with descriptive text

1392 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/uofcincinnati	Facebook	new tab	Add '(opens in new tab)' to text
http://twitter.com/uofcincy	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/uofcincy	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/uofcincinna…	Youtube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/edu/school?id=1…	linkedIn	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@uofcincy	tik tok	new tab	Add '(opens in new tab)' to text

1731 links and buttons have descriptive text

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

https://www.facebook.com/uofcincinnati; http://twitter.com/uofcincy; https://www.instagram.com/uofcincy; https://www.youtube.com/user/uofcincinnati; https://www.linkedin.com/edu/school?id=19141; https://www.tiktok.com/@uofcincy

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

●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

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

●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

●Uses ARIA roles only on compatible elements

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

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

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

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