Skip to content
https://case.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Warning::
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.
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer

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

B
Heading Hierarchy
12 headings
REVIEW
12 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Expand Your Education
  • H2 The CWRU Difference
  • H2 Research and Innovation
  • H3 Humanizing art
  • H2 Find Yourself in Cleveland
  • H2 More to Explore
  • H3 The Arts
  • H3 Collaborative Research
  • H3 Athletics
  • H2 Student Spotlight
  • H2 News and Updates
  • H2 Upcoming Events

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found | Case Western Reserve University ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA 1 pass AA only
title Case Western Reserve University: One of …
1.17:1
#000000
on
#09143A
needs 4.5:1 (normal text)
16px · top of page (header area)
button MENU
1.17:1
#000000
on
#09143A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Celebrating 200 years
1.17:1
#000000
on
#09143A
needs 4.5:1 (normal text)
16px · top of page (header area)
p At Case Western Reserve University, we t…
1.17:1
#000000
on
#09143A
needs 4.5:1 (normal text)
16px · top of page (header area)
p But we don't just think—we do.
1.17:1
#000000
on
#09143A
needs 4.5:1 (normal text)
16px · above the fold
p In labs and classrooms, we spend each da…
4.06:1
#000000
on
#696E6E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p to solve the biggest issues of today and…
2.44:1
#000000
on
#4A4C4F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p With hundreds of programs in a variety o…
3.51:1
#000000
on
#60636E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Undergraduate Programs
3.36:1
#000000
on
#5C6070
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Graduate & Professional Programs
4.01:1
#000000
on
#696B7F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Online Programs
2.33:1
#000000
on
#27497C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span The CWRU Difference
1.66:1
#000000
on
#003071
needs 4.5:1 (normal text)
16px · above the fold
span Research and Innovation
1.66:1
#000000
on
#003071
needs 4.5:1 (normal text)
16px · mid-page

6 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)
ElementRatioRequiredFGBGResult
h3 Humanizing art9.07:13.0:1
#000000
#99ACC6
Pass
h3 The Arts21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Collaborative Resear…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Athletics21.00:13.0:1
#000000
#FFFFFF
Pass
title Case Western Reserve…1.17:14.5:1
#000000
#09143A
Fail
button MENU1.17:14.5:1
#000000
#09143A
Fail
span Celebrating 200 year…1.17:14.5:1
#000000
#09143A
Fail
p At Case Western Rese…1.17:14.5:1
#000000
#09143A
Fail
p But we don't just th…1.17:14.5:1
#000000
#09143A
Fail
p In labs and classroo…4.06:14.5:1
#000000
#696E6E
Fail
p to solve the biggest…2.44:14.5:1
#000000
#4A4C4F
Fail
span Expand Your Educatio…4.92:14.5:1
#000000
#7A7B76
Pass
p With hundreds of pro…3.51:14.5:1
#000000
#60636E
Fail
span Undergraduate Progra…3.36:14.5:1
#000000
#5C6070
Fail
span Graduate & Professio…4.01:14.5:1
#000000
#696B7F
Fail
span Online Programs2.33:14.5:1
#000000
#27497C
Fail
span The CWRU Difference1.66:14.5:1
#000000
#003071
Fail
span Research and Innovat…1.66:14.5:1
#000000
#003071
Fail
p A distinguished scho…21.00:14.5:1
#000000
#FFFFFF
Pass
div aerial agents ©21.00:14.5:1
#000000
#FFFFFF
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+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
12 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
23 images 10 good alt text 12 decorative
IssueCount
too long1 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#quotesliderrangeQuote Sliderfor/id
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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Send Feedback