Skip to content
https://swarthmore.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
2
REVIEW
5
PASS
6
INFO
0
Checks
13
6 PASS 5 REVIEW 2 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title TikTok ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
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 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Swarthmore Home21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Homepage Ambient Vid…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Additional Site Navi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Search the website21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Main Horizontal Navi…3.43:13.0:1
#000000
#B43135
Pass
h2 Homepage Alumni Voic…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 To Zero By Thirty-Fi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Neutrality21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What's Distinctive A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News from Swarthmore21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Black Excellence and…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 To Zero By Thirty-Fi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Swarthmore Forward21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Homepage Link List21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Homepage Double Call…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Living @ Swarthmore21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Opportunities in Phi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Site Footer21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Social Media Links21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Additional Navigatio…21.00:13.0: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
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary Site Navigation" SEARCH MAIN CONTENTINFO footer

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

A
Heading Hierarchy
43 headings
PASS
43 headings
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Main Horizontal Navigation
  • H1 Swarthmore Home
  • H1 Homepage Ambient Video duplicate H1
  • H2 Homepage Alumni Voices and Sustainability
  • H2 To Zero By Thirty-Five: Inside Swarthmore’s Path to CarbonNeutrality
  • H3 Watch
  • H2 What's Distinctive About Swarthmore?
  • H3 Why Swarthmore
  • H2 News from Swarthmore
  • H3 Steven Mukum ’26 to Explore Human Displacement Across Five Countries as Watson Fellow
  • H3 Innovation of Upgraded X-Ray Tool to Enhance Research Experience for Physics, Chemistry, and Engineering Students
  • H3 Swarthmore to Award Honorary Degrees to Leaders in Higher Education, Arts, Justice, and Sustainability at 154th Commencement
  • H2 Events
  • H3 Swarthmore College Chorus and Garnet Singers
  • H3 “What’s in a (Building’s) Name?”
  • H3 Robert Putnam ’63, H’90 on Community in America, on Campus
  • H2 Black Excellence and President's Fund for Racial Justice
  • H2 To Zero By Thirty-Five
  • H2 Swarthmore Forward
  • H2 Homepage Link List
  • H2 Homepage Double Callout
  • H2 Living @ Swarthmore
  • H2 Opportunities in Philadelphia
  • H2 Site Footer
  • H3 Contact Information
  • H3 Social Links
  • H3 Site Feedback and Accessibility
  • H3 Legal Links
  • H3 Helpful Links - Left Column
  • H3 Helpful Links - Right Column
  • H3 Social Links
  • H3 Site Feedback and Accessibility
  • H3 Legal Links
  • H1 Additional Site Navigation duplicate H1
  • H2 Social Media Links
  • H2 Additional Navigation Links
  • H2 Social Media Links
  • H2 Helpful Information
  • H3 Dining Hall Hours
  • H3 Next Trains to Philadelphia
  • H2 guides
  • H1 Search the website duplicate H1
  • H2 Helpful Links

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 13 images OK
PASS
All 13 images OK
Info::
1 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
13 images 12 good alt text 1 decorative
All images have appropriate alt text.
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
#flyout__search-inputtextWhat are you looking for?for/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_Yys2aOANk9V82JjcMU8j6fSPwzLYwn6GbBdAWliWykI.css?delta=2&language=en&theme=swarthmore&include=eJxFy0sKwCAMRdENia7pWYNaYg2J9rP70kLp5A4O3KUrhaRTwB4rTidQZIUU-_gXPzeZkasVSs4O6Cjt-TP3CHZ22aAWIozcXumw8Na3nibTDafxKYU
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/default/files/css/css_Yys2aOANk9V82JjcMU8j6fSPwzLYwn6GbBdAWliWykI.css?delta=2&language=en&theme=swarthmore&include=eJxFy0sKwCAMRdENia7pWYNaYg2J9rP70kLp5A4O3KUrhaRTwB4rTidQZIUU-_gXPzeZkasVSs4O6Cjt-TP3CHZ22aAWIozcXumw8Na3nibTDafxKYU ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
What's Distinctive About Swarthmore? It ultimately doesn’t matter what course… div.container-fluid > ul.row > li#whats-distinctive-about-swarthmore > a.feature-stories__column-inner
○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
●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
●`[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 are distinguishable without relying on color.
●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
○`[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 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
○Form elements have associated labels
○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.
○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.

Send Feedback