Skip to content
https://www.yale.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Yale University
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name Yale University ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name Yale University Icons 6 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 ✗
B
Favicon & Branding
23 icon(s) detected
REVIEW
23 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
3 navigation pattern(s)
REVIEW
3 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
11 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 11 <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.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h2 Secondary Navigation
2.16:1
#000000
on
#6C2A66
needs 3.0:1 (large text)
24px · 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)
ElementRatioRequiredFGBGResult
h1 Yale University5.87:13.0:1
#000000
#AE6FC4
Pass
h1 Yale University21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secondary Navigation2.16:13.0:1
#000000
#6C2A66
Fail
h2 Main Navigation21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Striking a chord21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Creating instruments…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A partnership betwee…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 An American Songbook21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The latest from Yale…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Yale’s impact on A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Parts That Make …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Helpful Links21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Visiting Yale21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Social Links21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Main Navigation21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secondary Navigation21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gateway Navigation21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HEALTH & MEDICINE21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ENGINEERING21.00:13.0:1
#000000
#FFFFFF
Pass
h3 PUBLIC HEALTH21.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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 25 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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All News Alumni Arts & Humanities Business Campus & Community Environment Healt… div.news_explore_row > div.news_explore_supporting > form.news_explore_form > div.fs-dropdown
Info for Visiting Yale Campus Tours Maps & Directions Yale Visitor Center Museu… div.footer_nav_section > div.region > form.visitor_form > div.fs-dropdown

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Yale School of Art EXPLORE THE SCHOOL Benjamin Franklin College EXPLORE THE … div.fs-carousel-wrapper > div.fs-carousel-container > div.fs-carousel-canister > div.explore_carousel_item
The Yale Stradivari EXPLORE THE COLLECTION Brewing history LEARN MORE div.fs-carousel-wrapper > div.fs-carousel-container > div.fs-carousel-canister > div.explore_carousel_item

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.explore_grid_wrapper > div#fs-carousel__1 > div.fs-carousel-pagination > button.fs-carousel-page
2 div.explore_grid_wrapper > div#fs-carousel__1 > div.fs-carousel-pagination > button.fs-carousel-page
3 div.explore_grid_wrapper > div#fs-carousel__1 > div.fs-carousel-pagination > button.fs-carousel-page

These items highlight common accessibility best practices.

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
Dwight Hall at Yale LEARN MORE div.fs-carousel-canister > div.explore_carousel_item > article.explore_story > a.explore_story_link
Afro-American Cultural Center EXPLORE THE CENTER div.fs-carousel-canister > div.explore_carousel_item > article.explore_story > a.explore_story_link
○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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●ARIA input fields have accessible names
●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
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●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 `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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
22 landmarks
PASS
22 landmarks
Info::
<main> landmark present
Info::
11 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "skip_to_content" SEARCH MAIN ASIDE CONTENTINFO footer
A
Heading Hierarchy
38 headings
PASS
38 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Yale University
  • H2 Secondary Navigation
  • H2 Main Navigation
  • H2 Striking a chord
  • H3 HEALTH & MEDICINE
  • H2 Creating instruments anyone can play
  • H3 ENGINEERING
  • H2 A partnership between YSPH, NYC Health + Hospitals, and Juilliard Extension is now exploring music’s potential to relieve medical staff burnout.
  • H3 PUBLIC HEALTH
  • H2 An American Songbook
  • H3 SACRED MUSIC
  • H2 The latest from Yale News
  • H3 Suffer from seasonal allergies? These tips will help you find relief
  • H3 ‘Cultivating Conversation’: Instilling skills that carry dialogue forward
  • H3 Yale names Derek Chang and Philippe Costeletos as successor trustees
  • H3 Social media and youth mental health: Does more use always mean more harm?
  • H3 Five Yale affiliates named AAAS fellows
  • H2 Yale’s impact on America
  • H3 FOR THE GREATER GOOD
  • H2 The Parts That Make Yale Whole
  • H3 A closer look for the curious
  • H4 Dwight Hall at Yale
  • H4 Afro-American Cultural Center
  • H4 Yale School of Art
  • H4 Yale School of Art
  • H4 Benjamin Franklin College
  • H4 The Yale Stradivari
  • H4 Brewing history
  • H4 Wright Lab
  • H4 Bulldog Days
  • H4 Asian American Cultural Center
  • H2 Helpful Links
  • H2 Visiting Yale
  • H2 Social Links
  • H1 Yale University duplicate H1
  • H2 Main Navigation
  • H2 Secondary Navigation
  • H2 Gateway Navigation

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 15 images OK
PASS
All 15 images OK
Info::
9 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
15 images 6 good alt text 9 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
querytextsearcharia-label
inputsubmit(none)none

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

<input type="submit">

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

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found | Yale University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback