Skip to content
https://georgetown.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
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 1 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.

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::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 8 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Georgetown University ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
title Georgetown University in Washington DC
1.08:1
#000000
on
#0A0D0C
needs 4.5:1 (normal text)
16px · top of page (header area)
button Open Search Form
1.17:1
#000000
on
#151717
needs 4.5:1 (normal text)
16px · top of page (header area)
a Who We Are
1.79:1
#000000
on
#343938
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a The Whole Person
2.16:1
#000000
on
#47443A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Our Catholic & Jesuit Heritage
1.99:1
#000000
on
#443E38
needs 4.5:1 (normal text)
16px · above the fold
a Local & Global Impact
1.93:1
#000000
on
#463B32
needs 4.5:1 (normal text)
16px · above the fold
a Our History
1.82:1
#000000
on
#403829
needs 4.5:1 (normal text)
16px · above the fold
a Student Stories
1.80:1
#000000
on
#413728
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Faculty Stories
1.90:1
#000000
on
#433B2E
needs 4.5:1 (normal text)
16px · above the fold
a Alumni Stories
1.25:1
#000000
on
#241C10
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

4 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
h1 Georgetown Universit…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Build a Future Here21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Georgetown Campuses21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Upcoming Events21.00:13.0:1
#000000
#FFFFFF
Pass
h2 @GeorgetownUniversit…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 An Education That Ma…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Impact for the Commo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 DC at Your Doorstep21.00:13.0:1
#000000
#FFFFFF
Pass
title Georgetown Universit…1.08:14.5:1
#000000
#0A0D0C
Fail
button Open Search Form1.17:14.5:1
#000000
#151717
Fail
a Who We Are1.79:14.5:1
#000000
#343938
Fail
a The Whole Person2.16:14.5:1
#000000
#47443A
Fail
a Our Catholic & Jesui…1.99:14.5:1
#000000
#443E38
Fail
a Local & Global Impac…1.93:14.5:1
#000000
#463B32
Fail
a Our History1.82:14.5:1
#000000
#403829
Fail
a Student Stories1.80:14.5:1
#000000
#413728
Fail
a Faculty Stories1.90:14.5:1
#000000
#433B2E
Fail
a Alumni Stories1.25:14.5:1
#000000
#241C10
Fail
a Student Life21.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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 27 passed
REVIEW
88

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Close the Search Dialog body.home > div.lc--layout-container > div.l--layout > div#search-form

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
An Education That Matters div.c--component > div.text-container > div.f--field > h3

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Georgetown University @Georgetown X (Twitter) Logo USILA National Team of the W… section.cc--component-container > div.c--component > div.currator-feed > ul.juicer-feed

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Georgetown University @Georgetown X (Twitter) Logo USILA National Team of the W… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo 2025-26 Women's Team The Ge… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item
Georgetown University @Georgetown X (Twitter) Logo Photo from Georgetown on Twi… div.j-stacker-wrapper > div.j-stacker > div#j-column-0 > li.feed-item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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.
●`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
●`<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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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
○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.
○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.
A
Landmark Structure
21 landmarks
PASS
21 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 NAV "primary" 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

A
Heading Hierarchy
16 headings, 1 skip(s)
PASS
16 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Georgetown University
  • H3 An Education That Matters skipped
  • H2 Build a Future Here
  • H3 Impact for the Common Good
  • H2 News
  • H3 4 Alumni with Majors That Led Them in Unexpected Directions
  • H3 Honoring a Professor Whose Breakthroughs in Breast Cancer Research Saved Lives
  • H3 How 5 Students Found Their Faith at Georgetown
  • H3 English Professor Awarded the 2026 Guggenheim Fellowship
  • H2 Georgetown Campuses
  • H3 DC at Your Doorstep
  • H2 Upcoming Events
  • H3 The Oedipus Project
  • H3 An Evening with…Mo Amer and Ayman Mohyeldin
  • H3 Spring 2026- Senior Convocation
  • H2 @GeorgetownUniversity

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Alt Text Quality
All 33 images OK
PASS
All 33 images OK
Info::
17 decorative image(s) correctly marked
Info::
16 image(s) with good alt text
33 images 16 good alt text 17 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
#searchsearchSearch Georgetownfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback